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 695154 - Pressing enter is broken in the unlock dialog
Pressing enter is broken in the unlock dialog
Status: RESOLVED FIXED
Product: gnome-shell
Classification: Core
Component: login-screen
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Ray Strode [halfline]
gnome-shell-maint
: 695439 695568 695608 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2013-03-04 21:23 UTC by Giovanni Campagna
Modified: 2013-05-08 00:01 UTC
See Also:
GNOME target: 3.8
GNOME version: ---


Attachments
unlockDialog, loginDialog: Connect to the activate signal on the entry (2.67 KB, patch)
2013-03-05 07:05 UTC, Jasper St. Pierre (not reading bugmail)
committed Details | Review

Description Giovanni Campagna 2013-03-04 21:23:03 UTC
I suspect 7b705dd6703973880472c741ad127c5684b1b036 "modalDialog: Fix auto-completion of prompts immediately upon display", because the press event is on the entry, not the dialog.
I can connect to clutter_text.activate, but it looks wrong to me.
Comment 1 Colin Walters 2013-03-04 21:50:29 UTC
I can confirm this bug: In the current gnome-ostree, enter doesn't work in the GDM login entries either.
Comment 2 Matthias Clasen 2013-03-04 23:28:28 UTC
Thats blocker-worthy
Comment 3 Jasper St. Pierre (not reading bugmail) 2013-03-05 07:05:29 UTC
Created attachment 238089 [details] [review]
unlockDialog, loginDialog: Connect to the activate signal on the entry

This is the recommended way to connect to an entry's activation binding --
event bubbling is not guaranteed by ClutterText.


gdm changes untested -- unlock dialog changes tested, and they work.
Comment 4 Stef Walter 2013-03-05 08:44:04 UTC
(In reply to comment #0)
> I suspect 7b705dd6703973880472c741ad127c5684b1b036 "modalDialog: Fix
> auto-completion of prompts immediately upon display"

For those following along at home, this was bug #692937.
Comment 5 Giovanni Campagna 2013-03-05 14:02:32 UTC
Review of attachment 238089 [details] [review]:

Looks good to me (and works fine)
Comment 6 Atri 2013-03-05 14:42:51 UTC
In 3.6.3, with the rebased patch from bug 692937, i haven't seen the lock screen button affected, but the gdm button stopped registering <Enter> indeed. Does that seem possible? If so (and I am interested in doing the rebase), would it be okay for a rebase of this patch here for version 3.6.3 to just include the gdm fix or we should have both fixes anyway?
Thanks!
Comment 7 Jasper St. Pierre (not reading bugmail) 2013-03-05 20:25:32 UTC
Attachment 238089 [details] pushed as 1566a4e - unlockDialog, loginDialog: Connect to the activate signal on the entry
Comment 8 Colin Walters 2013-03-05 20:43:01 UTC
Confirmed fixed in current gnome-ostree builds.
Comment 9 Florian Müllner 2013-03-08 12:39:49 UTC
*** Bug 695439 has been marked as a duplicate of this bug. ***
Comment 10 Colin Walters 2013-03-10 14:50:51 UTC
*** Bug 695568 has been marked as a duplicate of this bug. ***
Comment 11 Florian Müllner 2013-03-11 07:45:54 UTC
*** Bug 695608 has been marked as a duplicate of this bug. ***
Comment 12 Atri 2013-03-14 00:11:08 UTC
Hi!
Would it be possible to have a patch to fix this for the gnome-shell 3-6 branch, please? As I said in c6, this affects the gdm greeter on gnome-shell 3.6.3, but not the unlock screen (at least with my testing).

Thanks!
Comment 13 Atri 2013-05-03 13:51:22 UTC
Hi!
Very sorry for commenting on a RESOLVED bug, but enter key being broken in the gdm greeter by the patch in bug 692937 prevents a fix for bug 692937 being released for openSUSE 12.3 (which was released with GNOME 3.6 and is supported at least until Nov this year). Would be extremely grateful if somebody takes a look at this problem for 3.6.x as well.

Thanks a lot.
Comment 14 Florian Müllner 2013-05-08 00:01:23 UTC
(In reply to comment #13)
> Would be extremely grateful if somebody takes a look at this problem 
> for 3.6.x as well.

With 3.8 out of the door and 3.10 on its way, attaching a backported patch would be the best approach to getting someone to take a look :-)