.xsession-errors: 'Failed to read saved session file'

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=485751

The /usr/share/gnome/default.session file specifies --sm-client-id default0 for gnome-wm, but metacity doesn't seem to like getting passed a non-existent ID. gnome-session used to automatically save the session, and from a saved session this error doesn't happen.

But it begs the question: what is an application supposed to do with these "default0" session IDs? I think metacity is right to complain, but why does the default.session include these? I can't find any documentation.

Saving the session (from System->Preferences->Sessions->Session Options->Remember current applications) will cause this problem to go away.

Yeah, I think this is a gnome-session thing. Moving over to them upstream.

this bug is still present in Ubuntu 8.10

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

Same here:
Window manager warning: Failed to read saved session file /home/test/.config/metacity/sessions/10aa64f26e40f3b10d123176351730231500000075630010.ms: Failed to open file '/home/test/.config/metacity/sessions/10aa64f26e40f3b10d123176351730231500000075630010.ms': No such file or directory

.config/metacity/session isn't existing.

Unfortunately, it looks like a regression in gnome.

http://bugzilla.gnome.org/show_bug.cgi?id=552387

I have same problem under Jaunty.
After last updates.

kocsis@kocsis-laptop:~$ compiz
Checking for Xgl: not present.
xset q doesn't reveal the location of the log file. Using fallback /var/log/Xorg.0.log
Blacklisted PCIID '8086:2a02' found
aborting and using fallback: /usr/bin/metacity
Window manager warning: Failed to read saved session file „/home/kocsis/.config/metacity/sessions/10487b19c556b32335124004238532476700000112410022.ms” Failed to open file „/home/kocsis/.config/metacity/sessions/10487b19c556b32335124004238532476700000112410022.ms” : No such file or directory
.config/metacity/session isn't existing.

This is still happening in Karmic.

Im having this Problem too with Archlinux.
I've somehow been able to fix it by creating a blank file "~/.config/metacity/sessions/"exact number in the errormsg".ms" but it occured again and again.

also here, happens in karmic, after hard reset.

Seeing this on latest Lucid x86 with metacity

What are the steps to reproduce? There's none in this report.
Some of the related bugs (other distros) don't seem to be related at all. Session management is working in Lucid and IIRC was working o Karmic too, but wasn't working in Jaunty, so what's bug about now?

to reproduce this bug

1. enable metacity window manager
2. log out and lot in again
3. type "grep metacity .xsession-errors" in the terminal

in my case I get the following warning messages:

Window manager warning: Failed to read saved session file /home/username/.config/metacity/sessions/10ae761321d5943f90126825862093768400000019000026.ms: Failed to open file '/home/username/.config/metacity/sessions/10ae761321d5943f90126825862093768400000019000026.ms': No such file or directory

Ok, thanks, I can confirm. Odd thing is can't find a reference for that file anywhere in $HOME or /tmp, and removing the only .ms file there was doesn't get a new one created (after a logout)...

A similar behavior here. I upgrade from Karmic to lucid and after reboot im without a WM i do metacity --replace and i have it again but that's i must do it after every boot. Is nasty Exist a workaround? TIA

i forget that's the output of metacity --replace

harrykar@harrysas:~$ metacity --replace
Window manager warning: Failed to read saved session file /home/harrykar/.config/metacity/sessions/10e53ab50e5f896526127366317039694800000015920003.ms: Failed to open file '/home/harrykar/.config/metacity/sessions/10e53ab50e5f896526127366317039694800000015920003.ms': No such file or directory

Note: The directory ~/.config/metacity does not exist.

ok i have a solution from "gnome should recreate your .config folder with the default config files." from http://ubuntuforums.org/showthread.php?p=9286111#post9286111

Procedure:
From liveCD i do
Code:

sudo nautilus

--without sudo you can't--
i rename .config folder i.e. .config_old and in the next restart at a first sight all seems to be ok

This bug is a Linux Mint Debian Edition ( mint isnt listed in the drop down column )