Red Hat Bugzilla – Bug 134169
gnome-session creshes at wm start when session saving is turned on
Last modified: 2007-11-30 17:10:50 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6)
Description of problem:
I did upgrade of whole system today (except kernel which i have
2.6.7-1). From times of Fedora Core 1 I cannot save session, because
after logout and login to gnome, gnome stalls with background color. I
tried to remove some positions from ~/.gnome2/session file (for
example when I have 10 saved programs there are few lines beginning
with 5, so I removed all them, renumbered following lines and
decreased total amount by 1). This also doesn't help. Even when teh
session was saved with only one running program gedit, the gnome
crashes just after login.
Gnome session manager is the worst part of Gnome. Last upgrade
resolves many problems: volume default level is no zero at once,
nautilus doesnt crash when smb:/// browsing, etc. but gnome-session NOT!!!
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Save session when exiting Gnome (turn it on in gconf-editor or in
2.Logout from Gnome
3.Login to Gnome
Actual Results: Gnome blocks/stalls just after logging in it. The
only solution is to restart xserver.
Expected Results: WOrking Gnome with restored state (apps with opened
documents) which was saved befor logging out.
I did the test with strace. The output of strace as good and bad
~/.gnome2/session files are accesible at:
These results are effect of saving session state before logging out of
gnome in FC2.
After logging in I have only spalsh screen but session stops/stalls
forever. I have to remove ~/.gnome2/session to fix this. Editing this
file does not help. I have to have permamently turned off session
FC2 was not clean install but upgrade form FC1, where I had same problem.
FC1 was clean install.
*** Bug 134212 has been marked as a duplicate of this bug. ***
*** Bug 137778 has been marked as a duplicate of this bug. ***
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.
This bug is being closed because it has been in the NEEDINFO state for a long
time now. Feel free to reopen the bug report if the problem still happens for
you and you can provide any information that was requested.