Ticket #278 (closed defect: fixed)

Opened 12 years ago

Last modified 12 years ago

"Log Out" button on screensaver takes far too long

Reported by: jdreed Owned by:
Priority: normal Milestone: Summer 2010 (Lucid Deploy)
Component: -- Keywords:
Cc: Fixed in version:
Upstream bug:

Description

Tommy and Joyce (hotline) mentioned that they'd been having some problems logging people out who had abandoned their cluster machines. I told them that Ctrl-L doesn't work anymore, and they have to use the mouse, but they said the "Log Out" button only works about half the time.

I assume this is related to #146, but I wanted to track it separately anyway.

Change History

comment:1 Changed 12 years ago by geofft

I just attempted to log quentin out of mega-man and gave up, only to notice him getting logged out fully ten minutes later. I wonder if the log out button actually didn't work for hotline, or behind the screensaver there are apps waiting for confirmation with a timeout entirely too long.

comment:2 Changed 12 years ago by jdreed

I meant to update this ticket. When I was re-installing 56 two weeks ago, I force-logged out a Debathena machine, and it also took a good 5-10 minutes to log out. So I think it probably does work, just poorly. We should still attempt to make it not suck.

comment:3 Changed 12 years ago by jdreed

  • Summary changed from "Log Out" button on screensaver doesn't always work to "Log Out" button on screensaver takes far too long
  • Milestone changed from Fall Release to IAP 2010

comment:4 Changed 12 years ago by geofft

Not sure how much this will help, but I tried changing --logout to --force-logout in r24267. The docs say that this ends the session "regardless of the inhibition state", which sounds plausibly related to the theory of apps waiting for confirmation and timing out.

comment:5 Changed 12 years ago by jdreed

The change to --force-logout works, but it has the side effect of triggering our reboot code, because it's a bit too unclean. We can decide we don't care.

comment:6 Changed 12 years ago by jdreed

  • Status changed from new to closed
  • Resolution set to fixed

The reboot code is not triggered all the time, and might be triggered only when the user's tokens are no longer valid. We don't care.

Note: See TracTickets for help on using tickets.