GNOME Bugzilla – Bug 519982
GDM use wrong icons for suspend and Log in
Last modified: 2010-06-17 02:53:44 UTC
Please describe the problem: Just tried out the new gdm 2.22 in Fedora 9. It seems like the button labeled "Suspend" use the media-pause icon, and that's a bit weird. The button labeled "Log in" seems to use the go-home icon, and I can't see the connection between the action and the icon there either. As the verbs in the buttons speak pretty clearly for themselves, it would perhaps be wisest to skip the icons, as it currently just leads to confusion what the buttons do. Steps to reproduce: Actual results: Expected results: Does this happen every time? Other information:
What specific gdmgreeter theme has the problem you describe? One way to get this value is to run this command: gdmflexiserver --command="GET_CONFIG greeter/GraphicalTheme" Are you seeing this problem with one of the 3 themes that is included with GDM (circles, happygnome, or happygnome-list)? If not, then this problem may be with a theme provided by your distro. If this is the case, then you should file the bug with your distro, not with GDM. GDM only maintains the 3 default themes, not themes added-on by various distros.
I used the ones without themes (?) http://live.gnome.org/GDM/Screenshots?action=AttachFile&do=view&target=simple-greeter-primary-fedora.png
I don't think Brian realized you mentioned 2.22
Oh, sorry. Yes, Ray, you are right.
Created attachment 141672 [details] still happening on 2.27 One way to fix this would be for the dialog to respect the buttons-have-icons gconf setting.
Thanks for taking the time to report this bug. However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use. By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME. Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.