It really does seem to be related to gnome-session (or whatever is responsible for reading the homefolder config files and load the window manager).
From the reports of several users, in Bug #572617 :
- The problem never happens with user accounts that are created after Karmic-Lucid upgrade and only used under a Lucid boot.
- It seem that the problem always disappears after removing ~/.config/gnome-session
If this is correct, it would be lack of backward compatibility in reading the home directory.
This renders the desktop session unusable for at least
(i) upgrades from Karmic
(ii) fresh Lucid installs keeping the Karmic home directory
(iii) home directory used with two releases on the same machine
(iv) two releases on the same network of machines in, say, an office
In some cases there is no healthy solution: saving the session, changing dektop effects etc etc... For many users nothing but the ugly "rm -rf ~/.config/gnome-session" worked.
Hi Chris,
It really does seem to be related to gnome-session (or whatever is responsible for reading the homefolder config files and load the window manager).
From the reports of several users, in Bug #572617 : gnome-session
- The problem never happens with user accounts that are created after Karmic-Lucid upgrade and only used under a Lucid boot.
- It seem that the problem always disappears after removing ~/.config/
If this is correct, it would be lack of backward compatibility in reading the home directory.
This renders the desktop session unusable for at least
(i) upgrades from Karmic
(ii) fresh Lucid installs keeping the Karmic home directory
(iii) home directory used with two releases on the same machine
(iv) two releases on the same network of machines in, say, an office
In some cases there is no healthy solution: saving the session, changing dektop effects etc etc... For many users nothing but the ugly "rm -rf ~/.config/ gnome-session" worked.