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 680348 - Timed login is broken
Timed login is broken
Status: RESOLVED FIXED
Product: gdm
Classification: Core
Component: general
unspecified
Other All
: High normal
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2012-07-21 00:20 UTC by Ray Strode [halfline]
Modified: 2014-06-05 21:20 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
daemon: hack around timed login not working (5.47 KB, patch)
2012-07-21 00:20 UTC, Ray Strode [halfline]
needs-work Details | Review
daemon: hack around timed login not working (6.39 KB, patch)
2012-07-21 05:51 UTC, Ray Strode [halfline]
committed Details | Review
manager: fix timed login (2.85 KB, patch)
2014-03-21 16:56 UTC, Ray Strode [halfline]
committed Details | Review
manager: close up timed login race (25.19 KB, patch)
2014-06-05 21:16 UTC, Ray Strode [halfline]
committed Details | Review

Description Ray Strode [halfline] 2012-07-21 00:20:27 UTC
We now start the session conversation just-in-time upon clicking a username in the user list.  This means we can't use the ConversationStarted signal anymore as a convenient way to know when the greeter is ready to hear the TimedLoginRequested signal.

We're going to need to emit it at some other time, or drop it and have the client just read the config themselves.

This patch was a quick hack and it didn't work.  Need to figure out why.
Comment 1 Ray Strode [halfline] 2012-07-21 00:20:28 UTC
Created attachment 219359 [details] [review]
daemon: hack around timed login not working
Comment 2 Ray Strode [halfline] 2012-07-21 05:51:04 UTC
Created attachment 219369 [details] [review]
daemon: hack around timed login not working

The greeter waits for the TimedLoginRequested signal to know
when to initiated the timed login process.

The slave used to send this signal shortly after the greeter
called StartConversation.  Now the greeter doesn't need to
call StartConversation, since conversations are started
implicitly.  This means the slave doesn't have a good place
to know when to emit the TimedLoginRequested signal.

For now, emit the signal a couple of seconds after the greeter
connects. This is a racy stop-gap. We're going to need to redo
how timed login is orchestrated.
Comment 3 Ray Strode [halfline] 2012-07-21 05:52:18 UTC
I pushed attachment 216369 [details] as a temporary stopgap
Comment 4 Vadim Rutkovsky 2014-03-21 10:06:37 UTC
TimedLogin still broken on https://git.gnome.org/browse/gdm/commit/?id=9f0402c0 (3.11.92.1) - Gnome Continuous tests can't login
Comment 5 Ray Strode [halfline] 2014-03-21 16:56:43 UTC
Created attachment 272579 [details] [review]
manager: fix timed login

There was some confusion over multiple competing enabled variables.

This commit eliminates the confusion.
Comment 6 Ray Strode [halfline] 2014-03-24 13:19:55 UTC
Attachment 272579 [details] pushed as 9f7a617 - manager: fix timed login
Comment 7 Ray Strode [halfline] 2014-06-05 21:16:52 UTC
Created attachment 277974 [details] [review]
manager: close up timed login race

Previously we would emit the timed-login-requested signal after the
client connects, which might be before it was listening for the
signal.

Now we only emit the signal in direct response to a GetTimedLoginDetails
call, which we make implicitly when the appropiate proxy interface is
set up.
Comment 8 Ray Strode [halfline] 2014-06-05 21:17:33 UTC
people are still seeing timed login not working sporadically. I haven't been able to reproduce, but this commit should close up the race.
Comment 9 Ray Strode [halfline] 2014-06-05 21:20:07 UTC
Comment on attachment 277974 [details] [review]
manager: close up timed login race

Attachment 277974 [details] pushed as e24484f - manager: close up timed login race