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 655075 - "Exclude" greeter option no longer honoured
"Exclude" greeter option no longer honoured
Status: RESOLVED OBSOLETE
Product: gdm
Classification: Core
Component: general
3.10.x
Other Linux
: Normal normal
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2011-07-21 19:52 UTC by Oliver Henshaw
Modified: 2018-05-24 10:36 UTC
See Also:
GNOME target: ---
GNOME version: 3.9/3.10



Description Oliver Henshaw 2011-07-21 19:52:10 UTC
I configure /etc/gdm/custom.conf to exclude a normal user account from the gdm greeter list, following the instructions at http://library.gnome.org/admin/gdm/stable/configuration.html.en#greetersection

But since upgrading from gdm 2.x to gdm 3.0 (really fedora 13 to fedora 15) this no longer works. It appears that this option was lost during the port to libaccountsservice:

http://git.gnome.org/browse/gdm/commit/gui/simple-greeter/gdm-user-chooser-widget.c?id=ec034f78dcb27baf240658323892ac2a665c6580
Comment 1 Oliver Henshaw 2011-11-13 18:38:28 UTC
No change in gdm-3.2.1.1-8.fc16.x86_64, accountsservice-0.6.14-2.fc16.x86_64.
Comment 2 Tadej Janež 2012-02-06 19:34:48 UTC
I can confirm this bug on F-15 with gdm-3.0.4-1.fc15.x86_64.

Oliver, please update the version number attached to this bug report (since you were able to reproduce the bug with gdm 3.2.x).
Comment 3 Caleb Maclennan 2012-02-11 22:59:32 UTC
I can confirm this but is still present in 3.2.1.1. Neither the gdm.schemas nor custom.conf files have any effect.
Comment 4 eimacdude 2012-12-06 19:03:14 UTC
This is still an issue with Gnome 3.4.2 (running on openSUSE 12.2 x86-64). It's the most annoying Gnome bug I've encountered. It occurs even if I set the user ID to a low number (in the system users range), as long as the user has a valid shell--so the only workaround I've found is to set the shell to /bin/false, which obviously is not suitable for many use cases.
From what I remember, back in 2010 this feature used to work. WTF happened?
Comment 5 eimacdude 2012-12-06 19:04:50 UTC
It's also shameful that this bug is still listed as UNCONFIRMED. Seriously? It's been almost a year and a half since Oliver reported it!
Comment 6 eimacdude 2012-12-06 19:06:35 UTC
BTW how do I change the version to 3.4.x? Or should I file a new bug report for that version?
Comment 7 Oliver Henshaw 2012-12-06 19:21:40 UTC
There's a little more discussion in the linked freedesktop.org bug, but it seemed to have stalled. I'm sure I saw a solution of sorts being implemented but can't find the bug number now, maybe I'm just mis-remembering.
Comment 8 David Raker 2013-01-28 13:39:29 UTC
I think the fix you are refering to is linked to from the freedesktop address below.  It seems to be coming along though, thankfully:  https://bugs.freedesktop.org/show_bug.cgi?id=56729
Comment 9 Kamil Páral 2013-07-08 08:50:25 UTC
Problem confirmed with GNOME 3.8 (Fedora 19).
Comment 10 Ulrich Keller 2013-11-28 12:28:11 UTC
Problem still persists in Gnome 3.10.
Comment 11 Peter Larsen 2014-09-22 18:07:01 UTC
Is it possible to at least get a "confirmed" here? What can we provide to make this confirmed?
Comment 12 Ray Strode [halfline] 2015-02-26 16:59:49 UTC
we don't use UNCONFIRMED differently than NEW or ASSIGNED ...
Comment 13 Ray Strode [halfline] 2015-02-26 17:00:45 UTC
This functionality is going to be provided by accountsservice, but it isn't there yet.
Comment 14 GNOME Infrastructure Team 2018-05-24 10:36:48 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gdm/issues/73.