User-Agent: Mozilla/5.0 (X11; U; Linux i686; ru; rv:1.8.1.6) Gecko/20070730 SUSE/2.0.0.6-1.1 Firefox/2.0.0.6 Build Identifier: Then Xfce session closing, all applications with unsaved data closed without prompting. Reproducible: Always Steps to Reproduce: 1.Open any application like gedit, mousepad 2.Write something without saving 3.Logout from xfce Actual Results: All data is lost! Expected Results: Every application (which can this) must be informed about session end, and session wouldn't close early than last informed application will be closed.
Well, xfce4-session is a session manager (hence the name). That is all session aware applications are asked to save their state, and this state is resumed on next login. This is done via the XSM Protocol. If xfce4-session wouldn't do this, applications like the xfce4-panel, the window manager, the desktop manager or the file manager wouldn't be restarted in the proper state on login. So, if that doesn't work for application XYZ, then it's most probably a bug (or a missing feature) in this very application. For example, gvim, firefox and thunderbird are known to be broken wrt session management.
(In reply to comment #0) > User-Agent: Mozilla/5.0 (X11; U; Linux i686; ru; rv:1.8.1.6) > Gecko/20070730 SUSE/2.0.0.6-1.1 Firefox/2.0.0.6 > Build Identifier: > > Then Xfce session closing, all applications with unsaved data closed without > prompting. > > Reproducible: Always > > Steps to Reproduce: > 1.Open any application like gedit, mousepad > 2.Write something without saving > 3.Logout from xfce > > Actual Results: > All data is lost! > > Expected Results: > Every application (which can this) must be informed about session end, and > session wouldn't close early than last informed application will be closed. > (In reply to comment #1) > Well, xfce4-session is a session manager (hence the name). That is all session > aware applications are asked to save their state, and this state is resumed on > next login. This is done via the XSM Protocol. If xfce4-session wouldn't do > this, applications like the xfce4-panel, the window manager, the desktop > manager or the file manager wouldn't be restarted in the proper state on login. > > So, if that doesn't work for application XYZ, then it's most probably a bug (or > a missing feature) in this very application. For example, gvim, firefox and > thunderbird are known to be broken wrt session management. > You don't understand problem. All applications which support sessions, correctly saved their state and load next login, but during logout, programs with unsaved date lost it. For example, then logging out in gnome, gedit with unsaved text prompt user to save text, and then xfce logging out gedit silently closed and all data lost.
Read what I said: xfce4-session implements the XSM specification. When a client asks the session manager to logout, it can specify whether the applications should get a chance to interact. If this is requested, the session manager then tells each client to save its state and allows each client, one at a time to interact with the user. So, xfce4-session itself does not decide whether to let applications interact. It's the client that requests the logout, which tells the session manager what to do (this is to support "fast logouts", i.e. on power loss). xfce4-session-logout, which is used by the panel, sets the interact_style to SmInteractStyleAny, hence every client is allowed to interact. This is one of the few points, where the session management spec is 100% clear. Believe or not, but xfce4-session is the most XSM compliant implementation. gnome-session is btw. the worst, what in turn means, that whether something works with gnome-session is irrelevant for Xfce. Anyway, the basics do work the same in both xfce4-session and gnome-session, so back to topic... And to make things clear: gedit works properly with xfce4-session (see http://www.foo-projects.org/~benny/tmp/session-interact.png). So this bug is indeed INVALID (would be WORKSFORME under normal conditions, but in this case it is clear that it is not a bug of this kind in xfce4-session). Ok, now to your problem, which is indeed a question for the mailinglist, because there is no proof for a bug in xfce here... Let's start guessing: 1. Do you save session on logout? (i.e. auto-save in settings or save check box in logout dialog). 2. Did you build gedit (actually libgnomeui) with SM support? 3. Do you use a broken version of gedit/libgnomeui? (possible, tho unlikely... and no, gnome-session is not a reference here) 4. Does xfce4-session crash for some reason before the logout is complete? (tho in this case the session wouldn't be saved either) 5. etc, etc You might have noticed that I'm a bit picky about this issue, but let me explain: From the initial report, it was obvious that you didn't take the time to understand what's going on here exactly, which is ok, since not everyone needs to know anything. But you kept stating that xfce4-session is broken, which is - also obviously, as explained - not the case. And this way you won't get your problem solved, because you're no longer looking for a solution (or a way to understand the problem), but you're simply repeating a false argument.
Hm, ok, that was kinda too verbose... In short: xfce4-session works, gedit works, and check the list of possible problems included in the previous comment. If that doesn't fix the problem, move the discussion to the xfce mailinglist. Thanks.
Re-reading your comment... you didn't insist on a bug in xfce4-session. So, sorry for that stupidity on my side. But try to avoid simply reopening bugs in the future.