After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 115162 - logout ignored
logout ignored
Status: RESOLVED DUPLICATE of bug 95834
Product: gnome-session
Classification: Core
Component: general
2.2.x
Other FreeBSD
: High major
: ---
Assigned To: Session Maintainers
Session Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-06-14 04:07 UTC by myron cheung
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.1/2.2



Description myron cheung 2003-06-14 04:07:30 UTC
When I click on the "logout" button in the "Actions" menu on the top panel,
nothing happens for 10 to 15 minutes before the expected dialog box pops up
and asks for confirmation to logout.
Comment 1 Elijah Newren 2003-06-14 21:12:24 UTC
This looks somewhat like bug 95834, except that the time interval
sounds a lot longer.

myron: Does this always happen, or does it only happen if you try to
log out shortly after logging in.  If the latter, can you trying
logging in and immediately log out and find out exactly how many
minutes and seconds it takes for the logout screen to appear?

Also, what are the contents of your ~/.gnome2/session-manual and
/usr/share/gnome/default.session files?
Comment 2 myron cheung 2003-06-14 21:37:29 UTC
Further experiment shows that this bug occurs in 3 out of 5 sessions.
 If I logout immediately after I started my session, the average time
delay is approximately 5 minutes before the logout event takes effect.

#####################################################3
The content of my ~/gnome2/session-maual:

[Default]
num_clients=1
0,RestartStyleHint=3
0,Priority=50
0,RestartCommand=xrdb -merge .Xresources 

#########################################################
The content of my /usr/X11R6/share/gnome/default.session:

# This is the default session that is launched if the user doesn't
# already have a session.
# The RestartCommand specifies the command to run from the $PATH.
# The Priority determines the order in which the commands are started
# (with Priority = 0 first) and defaults to 50.
# The id provides a name that is unique within this file and passed to the
# app as the client id which it must use to register with gnome-session.
# The clients must be numbered from 0 to the value of num_clients - 1.

[Default]
num_clients=4
0,id=default0
0,Priority=0
0,RestartCommand=gnome-smproxy --sm-client-id default0
1,id=default1
1,Priority=10
1,RestartCommand=gnome-wm --default-wm gnome-wm --sm-client-id default1
2,id=default2
2,Priority=40
2,RestartCommand=gnome-panel --sm-client-id default2
3,id=default3
3,Priority=40
3,RestartCommand=nautilus --no-default-window --sm-client-id default3
4,id=default4
4,Priority=50
4,RestartCommand=gnome-terminal --sm-client-id default4

###########################################################
Comment 3 Elijah Newren 2003-06-14 21:48:02 UTC
5 minutes sounds closer to the appropriate time and the fact that you
have added another command to the startup (session commands) makes
this look more like bug 95834.  

If you log in, wait about five or six minutes and then try to log out,
are you still presented with the long wait?  If so, how long is it?
Comment 4 myron cheung 2003-06-15 00:59:21 UTC
In 2 out of 3 trials in which I tried to logout from a 5 minute old
session, the logout dialog box popped up immediatedly as expected. 
Only once I had to wait for another 2 minutes before the dialog box
popped up.
Comment 5 Elijah Newren 2003-06-15 15:12:46 UTC
Well, I think this is probably a duplicate of bug 95834, but I'm not
sure.  So I'm going to add a comment to that bug about this one.  I'm
also going to reopen this one, set priority & severity to match that
found in bug 95834, and add the bugsquad keyword.  I believe this
should be moved to gnome-session as well, though bugzilla will
probably make me do that in two steps...
Comment 6 Elijah Newren 2003-06-15 15:13:32 UTC
It almost let me do it.  Now I'm selected "Reassign bug to owner of
selected component."
Comment 7 Mark McLoughlin 2004-02-04 09:15:28 UTC

*** This bug has been marked as a duplicate of 95834 ***