If you upgrade to Mageia 2 and run KDE with an existing user account, that user's panel configuration gets whacked and overwritten automatically. To the greatest extent that it is possible, this should not happen. If the user has a Taskbar applet enabled, it gets removed. Many of the icon launchers the user has on the Panel get removed. A Windows 7 style "Icon Tasks" thing gets added. There is no easy way to restore the user's original configuration. Users and sysadmins should not have to go manually restoring existing user configurations. This is a very big problem and is the same issue that turned a lot of people off (myself included) from Mandriva 2011. It replaced the whole Panel with the ROSA Panel, and even removing that and re-adding a regular Panel did not restore the existing configuration. We are now essentially doing the same thing.
CC: (none) => lmenut
CC: (none) => balcaen.john
CC: (none) => juan.baptiste
CC: (none) => dmorganec
Blocks: (none) => 3342
Source RPM: kdeplasma-addons-4.8.2-1.mga2.src.rpm => mageia-kde4-config-2-0.20120411.3.mga2.src.rpm
This bug is not *really* easy to fix here because upstream decided to not support anymore the global plasmarc files. Due to that change & the fact we still used global plasma rc file in mga1 we were forced to switch to handle .js to create configuration. Without the management of global plasmarc file an user will loose his panel since the user configuration plasmarc file provided only "specific" user changes. Here luc wrote a script to handle it & recreate a panel following our default mageia panel (using plasma-icontasks). He also add the classical panel which you can add by simply delete the "new" panel & right click on the desktop to add the "old" one.
I see. If there's a simple procedure that will restore the user's previous configuration, we could just mention this in the Release Notes. If the user has made no modifications to their plasma configuration, I could see it being OK to update them to the new defaults, given the issues you have explained. Any modifications they have made, like buttons or widgets added to or removed from their Panel or desktop should be in their user plasmarc and should continue to be honored. For instance, I think I had a KWrite button on my Panel in one of the upgrade tests I did and it was removed. This is an unfortunate deal, but thank you for the explanation. The only other thing I can think of, would it be possible to have some thing a user could run under Mageia 1 (before upgrading) which would merge the current system-wide configuration that they are using into their user configuration, so that it will carry over on update?
(In reply to comment #2) [...] As John has previously explained in comment #1, we were forced to move to a new configuration system for plasma. > If the user has made no modifications to their plasma configuration, I could > see it being OK to update them to the new defaults, given the issues you have > explained. > > Any modifications they have made, like buttons or widgets added to or removed > from their Panel or desktop should be in their user plasmarc and should > continue to be honored. The plasma update script tries to respect the user's plasma configuration as far as possible: 1) widgets on the workspace desktop shouldn't be touched. 2) the update script only updates the panel based on our previous default panel (with panel id=2). e.g. if the user has removed our default panel, and uses a fully customized panel, the update script doesn't modify it. 3) if the user has customized our mga1 default panel (panel id=2) e.g. by adding some icons, the added widgets should be added on the new default panel (but sadly, we can't guarantee the same order on the panel). > For instance, I think I had a KWrite button on my > Panel in one of the upgrade tests I did and it was removed. If you have systems where the update has seriously damaged the panel configuration, could you attach the following files from ~/.kde4/share/config : - plasma-desktoprc.Mga1ToMga2 & plasma-desktop-appletsrc.Mga1ToMga2, - plasma-desktoprc and plasma-desktop-appletsrc, - a screenshot of the new panel. > > This is an unfortunate deal, but thank you for the explanation. > > The only other thing I can think of, would it be possible to have some thing a > user could run under Mageia 1 (before upgrading) which would merge the current > system-wide configuration that they are using into their user configuration, so > that it will carry over on update? I don't know tools that can do this merge.
Hardware: i586 => All
any news ?
As said in comment #1 & #2 there's nothing we can do about it. I also dropped a note in the errata for this. Closing as invalid rather then wontfix since the change is done on purpose due to upstream change
Status: NEW => RESOLVEDResolution: (none) => INVALID