GNOME Bugzilla – Bug 485751
[Gutsy Beta] .xsession-errors: 'Failed to read saved session file'
Last modified: 2020-10-30 14:32:26 UTC
The bug has been opened on https://bugs.launchpad.net/bugs/150721 "Hi, Using Gutsy beta the .xsession-errors file consistently reports the following error: Refusing to initialize GTK+. /etc/gdm/Xsession: Beginning session setup... /etc/X11/Xsession.d/40guidance-displayconfig_restore: 11: /usr/bin/displayconfig-restore: not found SESSION_MANAGER=local/ilium:/tmp/.ICE-unix/5180 Window manager warning: Failed to read saved session file /home/andrew/.metacity/sessions/default0.ms: Failed to open file '/home/andrew/.metacity/sessions/default0.ms': No such file or directory ** Message: Not starting remote desktop server No problems with this, although there appears to be a delay in the opening desktop fully loading. Andrew"
As Frank Murphy points out in that Launchpad bug, this is not a Metacity bug: a) The session manager is telling Metacity to load a window setup which doesn't exist. If this is a bug in anything, it's a bug in the session manager. b) The most trouble this could cause is that the windows weren't arranged on startup in the way you wanted (in this session which apparently doesn't exist). If this isn't actually causing you any trouble, it's not really much of a bug. Given a), I'm sending this over to the gentlefolk at gnome-session for their thoughts.
I am still seeing this bug in gnome-session-2.24.1 Window manager warning: Failed to read saved session file /home/test/.config/metacity/sessions/10790aea04b02a3c9f122541151659755300000210510005.ms: Failed to open file '/home/test/.config/metacity/sessions/10790aea04b02a3c9f122541151659755300000210510005.ms': No such file or directory
I believe this is a duplicate of bug 552387
no, if the bug was just not-saving-the-session, then it wouldn't be telling metacity to load in any saved session file. the bug probably involves the reading-the-legacy-saved-session-file code, though I don't know why the old saved session file would have been deleted, since legacy sessions should never get discarded with the current code.
This is still an issue with ubuntu lucid alpha 3, gnome 2.29.91, metacity 2.28.1-0ubuntu4. Any chance this would be fixed as it's been hanging around for some time now?
Assuming that this problem is obsolete nowadays. If you can still reproduce this problem with a recent version (currently: 3.38) of GNOME / gnome-session, then please report this at https://gitlab.gnome.org/GNOME/gdm/-/issues/ and follow https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines - thanks a lot!