Can you send a stack of firefox-bin while it is in this state, and
maybe a couple of seconds of truss output?
Comments inline:
Lars Tunkrans wrote:
I hope this is enough to convince you that the Xsun process for the
user has been killed off
by Xautolock/kill and that some processes remain.
Yes. Very strange.
So enough of firefox.
I know what gconfd is .
but what is the function of /opt/SUNWapleg/bin/desktopApps
Its being started by a Xsession startup script.
Do I need this SUNWardsa-misc package ?
Sorry I have no insight into these packages. They're not
related to Sun Ray Software, that's all I know about them.
You'd probably have to ask on [EMAIL PROTECTED]
By the way, it has recently been determined that you should
be able to write an xautolock kill script that uses gnome-session-save
to exit the session. Perhaps this will work more cleanly. Here are the
notes from CR 6485550:
I believe the desired functionality is available with the existing
gnome-session-save utility.
You can call it with the following options
--silent : This is the argument that you need. It causes the dialog asking if
the user wants to exit the session to not be displayed
--kill : This is the other argument that you need. It causes the session to
actually die.
I'm still doing some research to find out whether you can optionally decide
whether to save the session or not.
*** (#4 of 5): 2007-11-05 19:51:19 GMT+00:00 [EMAIL PROTECTED]
Some more information:
The --gui option only affects this message that gnome-session-save might display
if it cannot connect to the session manager.
display_error (_("Could not connect to the session manager"));
So, the --gui option does not affect the logout dialog or the dialog that tells
you 'These windows do not support "save current setup" and will have to be restarted
manually next time you log in'. These messages actually are coming from metacity,
not gnome-session-save.
If you specify the --silent option, then the logout dialog and the 'These windows do
not support "save current setup" and will have to be restarted manually next time you log in" dialogs are not shown.
If you specify the --silent option *without* the --kill option, then it saves
the
user's session and does not prompt the user for any input.
If you specify the --silent and --kill options together, then it will exit the
session and will *not* save the user session. The one exception is if the user has
their auto_save_session GConf setting set to true (not the normal default), then it
will save the user session when you specify --silent and --kill together. The full
GConf key is:
/apps/gnome-session/options/auto_save_session
So, if you actually do want to save the user's session and you also want to kill
the session silently, you would need to run gnome-session-save twice. The first
time to save the session, the second time to kill the session. Even if the
user has auto_save_session set to true, this wouldn't cause a problem - it
would just waste a bit of time saving the information twice.
gnome-session-save --silent
gnome-session-save --silent --kill
Note that not all programs in JDS or GNOME support the SM session save feature
(provided by the Xserver libSM library). So saving the user's session won't mean that all programs will necessarily be restarted.
-Bob
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
