** Description changed: Binary package hint: gnome-session + gnome-session-save command don't look at the WM your are using but at the desktop > gnome > application > window_manager > current Gcong key which may not be up to date. + In my case the current key was wrongly set to /usr/bin/xfwm4 instead of the standard /usr/bin/metacity therefore the generated session file will use xfwm4 as window manager (which is known to cause sometimes long login time). + Each person trying to change his WM may issue this kind of annoyance with the session file. + + This is either a gnome-session-save issue because it is checking the + Gconf key rather than the WM itself or a Gconf key update issue because + when changing your WM the "current" key is not updated. + + To reproduce this: + 1- Change your "desktop > gnome > application > window_manager > current" Gconf key to something else than your current WM and run the gnome-session-save command. Then check the session file, it should use the WM set in the gconf key and not the one you're using. + or + 1- change your WM and run the gnome-session-save command, then check your session file to see if if it's using your old WM or the current one. + + Old description (outdated now) : After gutsy upgrade, each time i use gnome-session-save it result in a broken session file. With this broken session file impossible to finish the gnome login (waited 2 minutes). To workaround this i had to put back my old feisty session file then it is good again. I can reproduce this as much as i want, if i use gnome-session-save command it brokes the session file each time.
** Description changed: Binary package hint: gnome-session - gnome-session-save command don't look at the WM your are using but at the desktop > gnome > application > window_manager > current Gcong key which may not be up to date. + gnome-session-save command don't look at the WM your are using but at the desktop > gnome > application > window_manager > current Gconf key which may not be up to date. In my case the current key was wrongly set to /usr/bin/xfwm4 instead of the standard /usr/bin/metacity therefore the generated session file will use xfwm4 as window manager (which is known to cause sometimes long login time). Each person trying to change his WM may issue this kind of annoyance with the session file. This is either a gnome-session-save issue because it is checking the Gconf key rather than the WM itself or a Gconf key update issue because when changing your WM the "current" key is not updated. To reproduce this: 1- Change your "desktop > gnome > application > window_manager > current" Gconf key to something else than your current WM and run the gnome-session-save command. Then check the session file, it should use the WM set in the gconf key and not the one you're using. or 1- change your WM and run the gnome-session-save command, then check your session file to see if if it's using your old WM or the current one. Old description (outdated now) : After gutsy upgrade, each time i use gnome-session-save it result in a broken session file. With this broken session file impossible to finish the gnome login (waited 2 minutes). To workaround this i had to put back my old feisty session file then it is good again. I can reproduce this as much as i want, if i use gnome-session-save command it brokes the session file each time. -- gnome-session-save scew up session file https://bugs.launchpad.net/bugs/157780 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
