[Bug 157780] Re: gnome-session-save scew up session file
good enough, closing the report for now then, it should be re open if someone else is able to reproduce it. thanks. ** Changed in: gnome-session (Ubuntu) Status: Incomplete = Invalid -- 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 Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 157780] Re: gnome-session-save scew up session file
Yes, i guess this impact only users playing with WM so maybe we can safely consider than someone playing with WM is able to fix WM related issues even though it would have been better to autodetect the WM while generating the session file. Anyway we can still re-open the bug latter if some users confirm this as an annoying issue, so lets close the bug report. -- 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 Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 157780] Re: gnome-session-save scew up session file
Still an issue? nobody else has confirmed this since your call for testing, otherwise i'll close this report. thanks. -- 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 Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 157780] Re: gnome-session-save scew up session file
Ok please someone at least confirm this on another computer so we can set this report as confirmed and not incomplete I edited the description explaining how to reproduce the bug, i can reproduce this as much as i want and i located the problem. Updating by hand the Gconf key to /etc/bin/metacity solved my issue. Hope someone will get interest in fixing this before hardy, this sounds really easy to fix. -- 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 Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 157780] Re: gnome-session-save scew up session file
** 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 Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 157780] Re: gnome-session-save scew up session file
Ok here some more informations. I discovered some strange behaviour about gnome-session-save. YOu can see in the gutsy generated session file that xfwm4 is set as default manager with no reason. However for an odd reason the desktop gnome application window_manager current Gcong key was set to /usr/bin/xfwm4 which could explain the error. Anyway this clearly demonstrate that the gnome-session-save command is not looking for the WM your are using but is looking to the Gconf key which like i shown can be wrong. Please try to reproduce this on your computer, set the desktop gnome application window_manager current Gconf key to something else than your current WM and check that gnome-session-save will take in consideration your Gconf key and not your current WM. Then change your WM and check that the Gconf key (like i guess) is not updated. I'm pretty sure to have located the problem now, thanks to anyone who can confirm this. -- 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 Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 157780] Re: gnome-session-save scew up session file
One more thing i would like to add and which is really weird to me is the presence of these lines in my gutsy generated session file (the one who don't work ) : ,Program=xfwm4 13,CurrentDirectory=/home/frodon 13,CloneCommand=/usr/bin/xfwm4 --display :0.0 13,RestartCommand=/usr/bin/xfwm4 --display :0.0 --sm-client-id 117f00010100011934840570061180003 I have xfwm4 installed but am not using it at all so this has really nothing to do in my session file and i wonder how this came into it. I think this point is showing that something is wrong somewhere with gnome-session-save and has reported many time in the following bug report many are issuing long login time so there's might be something ultimatly : https://bugs.launchpad.net/ubuntu/+source/meta-gnome2/+bug/151544 -- 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 Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 157780] Re: gnome-session-save scew up session file
Unfortunatly my old feisty session file is really different than the one created under gutsy so it is hard for me to catch what could be wrong, in addition i tried to delete my session file then start a new session and run the gnome-session-save command with no apps opened and it results also in a broken session file. So for me it a bit surprizing that after deleting the session file and with no apps opened the gnome-session-save command still brake my session file. I think there should be something wrong in the way how gutsy write the session file compared to feisty. I join in this post the my old feisty session file which is working correctly. ** Attachment added: Feisty session file which is working correctly http://launchpadlibrarian.net/10193355/session -- 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 Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 157780] Re: gnome-session-save scew up session file
Could you attach the gutsy new session? Looks like you are the only one to have the issue which makes it likely the issue come from something you are running -- 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 Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 157780] Re: gnome-session-save scew up session file
Sorry i wasn't clear in my previous comment, the file i posted in my previous comment (wrongly called Feisty session file which is working correctly) is the one i'm using now under gutsy. -- 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 Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 157780] Re: gnome-session-save scew up session file
Here is an ubuntuforum thread were users are reporting long login time, so this might be also describing the same issue where the session file is written in a way where the login time is really long. In my case i never waited more than 2 minutes. http://ubuntuforums.org/showthread.php?t=585635 -- 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 Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 157780] Re: gnome-session-save scew up session file
Here is an example of a broken file generated by the gnome-session-save command on my computer. ** Attachment added: Broken session file http://launchpadlibrarian.net/10186561/session_old -- 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 Desktop Bugs, which is a bug contact for gnome-session in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 157780] Re: gnome-session-save scew up session file
Thank you for your bug. That's likely to due to one of the applications stored in your session. What is the difference between the working and broken version of your session? ** Changed in: gnome-session (Ubuntu) Importance: Undecided = Low Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs) Status: New = Incomplete -- 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 Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
