Comment 8 for bug 249373

First, correction: GNOME is indeed switching to a new D-Bus-based protocol for session management, but the new session manager *should have legacy support for XSMP*. The latest documentation seem to be http://live.gnome.org/SessionManagement/GnomeSession and XSMP is mentioned there prominently. Also on my machine, the session manager is indeed creating the SESSION_MANAGER environment variable needed by XSMP clients, and the variable points to a UNIX domain socket as expected.

Some further observation gives me the impression that, in intrepid, the session is not being saved at all, and that applications aren't being shut down cleanly. Try, for example, starting firefox, loading a page, logging out from the GNOME session, logging in again, and starting firefox again (it won't be restarted automatically, anyway.) Firefox will then report that the previous session was ended forcefully, and ask if its state should be restored. I tried with other applications, such as OpenOffice and Lyx (just open a new document, put some text in it, and log out from GNOME) and this leads to data loss. So I don't think this problem should be considered low priority, it isn't just anoying, it is rather dangerous.

Also, Sebastien, the linked upstream bug doesn't really seem to be related to this problem. As far as I understand it, it has to do with the new session manager not being able to restore old session data, saved by the older session manager.

Can people please check if they can repeat my results with Firefox and OpenOffice?