Description of problem: After applying all F17 updates (including gnome-3.4... packages), the GDM login window presents additionally the mysql server account on the login screen. Version-Release number of selected component (if applicable): gdm-3.4.0.1-1 How reproducible: Always before login/after logout Steps to Reproduce: 1. 2. 3. Actual results: Expected results: MySQL account is not displayed on the gdm login screen Additional info:
I can confirm this bug on Fedora 17 Beta RC2 with full updates installed. If I install mysql-server package and reboot, MySQL user is listed in gdm. The relevant string from /etc/passwd: mysql:x:27:27:MySQL Server:/var/lib/mysql:/bin/bash Since it is /bin/bash, and not the nologin shell, probably the mysql-server bug?
Same here, and I also get the user jetty displayed as well. (user 991) from /etc/passwd: jetty:x:991:985::/usr/share/jetty:/bin/sh mysql:x:27:27:MySQL Server:/var/lib/mysql:/bin/bash Both users show in the login window, but show as disabled.
Aleksandra above may have something. All of my other users are have /sbin/nologin as the shell. The 2 I am getting displayed have /bin/sh and /bin/bash as the login shell. My normal user of course is displayed and has /bin/bash as the login shell. So, is GDM scanning the /etc/passwd file and displaying any user that has a login shell?
Hi, same here, top of mysql it displays "Detachable IRC proxy" dircproxy:x:989:989:Detatchable IRC Proxy:/var/lib/dircproxy:/bin/sh I believe it should be displaying only accounts with id >= 1000.
Actually, it should have some configuration option to allow selecting users if you wish to have a user with a user id < 1000 displayed, and display user ids >= 1000 unless told not to (again in configuration options). At least that is what sounds logical to me.
I fully agree!
I wasn't expecting any response to this bug report. In the past year, only 1 bug report for Gnome related items that I have filed has even been responded to, and that was only after Adam Williamson mentioned that me might add it to the blocker list. Other bug reports get responded to, but Gnome bugs sit out here forever with no response.
you'll get a better reception with gnome bugs if you file them upstream. That's where the development happens, after all. Don't get discouraged, though, if you don't always get replies. Remember bug reports are more for users to help the project as a whole than as a way for users to get support from the developers of the project. It's more of a "give useful information for the common good" type thing. We fixed mysql here: http://cgit.freedesktop.org/accountsservice/commit/?id=abd78a5a184f012aecdb8b3795b91c854e1fbece and we fixed things more generally here: https://bugzilla.gnome.org/show_bug.cgi?id=673784
accountsservice-0.6.18-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/accountsservice-0.6.18-1.fc17
Package accountsservice-0.6.18-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing accountsservice-0.6.18-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-5796/accountsservice-0.6.18-1.fc17 then log in and leave karma (feedback).
This appears to only fix the problem for the mysql user but as was mentioned in the comments the problem also exists for the jetty user. So it looks like the blacklist needs to be extended some more. Should I open a new bug specifically for the jetty issue?
Same here - issue fixed only partially. Mysql user is gone, dirc proxy user still visible.
jetty user still shown.
accountsservice-0.6.18-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.