1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
|
* run SmDiscardCommand when necessary (e.g. pending clients do not fire up,
or we reach another checkpoint/shutdown)
* add a SaveYourself timeout, so bogus clients do not prevent the desktop
from shutdown [Initial code exists in manager.c SEE BELOW]
* Multiscreen support is missing (e.g. with the logout screen)
* Save to XML instead of this binary format.
* Honor SmRestartStyleHint
* Add APM support (separate SM client)
* Use GScanner to parse splash.theme files?!
* Add an option to disable Autostart by xfce4-session
* Fix "Autostart" with default.session [no problem]
* Add configure options to make packagers life easier regarding the
"shutdown/reboot" thing (see the Mail from Marcel Pol on 20031120)
[partly done]
* Remember last selected "Logout action" and make that the default for
the next session.
* Use full display string as session identifier instead of hostname only.
* Add option to disable binding of a TCP/IP socket with ICE (see Moritz
mail on 20031211). [DONE]
* Fix the problem with xfce4-session not working on Solaris 9! [DONE]
* Move "setenv()" from manager.c to libxfce4util as xfce_setenv() [DONE]
* An error leads to a session close on Linux when running several xterms
as reported by Olivier.
Freezes in Shutdown Screen:
---------------------------
* Select "poweroff" from the option menu, click outside the dialog -> frozen!
* Sole solution for now: get rid of the option menu and use radio buttons or
something else that does not create new toplevel windows.
Solution for the TIMEOUT in SAVEYOURSELF problem:
-------------------------------------------------
* Handle the interacting clients first
* Then wait some period of time (e.g. 5-10 seconds) and if some clients
haven't finished the SAVE YOURSELF phase during that time, display a
window with a the list of "sucking" clients and a button "Terminate".
Pressing terminate will terminate the session regardless of the state
of the given clients. In addition to the window there should be a timer
that counts from 60 to 0 seconds and once 0 is reached the session is
automatically terminated.
IRC Log of Olivier and another Linux user with the xterm problem:
-----------------------------------------------------------------
<thomas_adam> ~/.xsession-errors report failings...
<ofourdan> sorry...
<ofourdan> what errors?
<thomas_adam> Client 0x3735252653653536738 lost connection to ICE_socket
<thomas_adam> that's repeated for the other xterm (there were two in the session I saved)
<thomas_adam> and then I just get flung back to the VT
<ofourdan> I think I had such a problem already and reported to benny
<ofourdan> no core, just the session dies
<thomas_adam> ah right
<thomas_adam> yup
<thomas_adam> so a work in progress then? :)
<ofourdan> dunno, cuz he didn't take it into account
<ofourdan> afaik
<thomas_adam> oh, :)
<ofourdan> he can't reproduce the problem
<ofourdan> do you run linux.
<ofourdan> what xfree ?
<ofourdan> does it fail with xterm?
<thomas_adam> Debain Unstable
<thomas_adam> XFree86 4.2.1.1
<thomas_adam> If I clear ~/.xfce/session
<thomas_adam> and start from scratch...
<ofourdan> what if you run another type of terminal, like gnome-terminal or rxvt instead of xterm?
<thomas_adam> yeah...
<thomas_adam> if I open say rxvt or xterm or both, and save them...
<thomas_adam> log back in, the session is restored fine....
<ofourdan> no, no, no xterm at all
<thomas_adam> I have tried that....
<thomas_adam> I'm getting to my point :)
<ofourdan> well, I'll try to ping benny agin on that, it's definitely a show stopper
<thomas_adam> one save and one restore of that session works fine...
<thomas_adam> any subsequent restores of that session cause it to keel over and die.
|
