GNOME Bugzilla – Bug 589539
GDM login theme change when using accessibility features
Last modified: 2011-09-07 13:19:05 UTC
The bug has been opened on https://bugs.launchpad.net/bugs/402017 "gdm: 2.27.4-0ubuntu2 When login screen first appears, the window/area containing the username to click on is 338px wide (measured with "screenruler" app). After enabling and disabling the large-text accessibility feature, the area increases to 455px wide. After enabling and disabling the large-text accessibility feature the accessibility icon/button does not change back to the original size but stays at the larger size set when the large-text feature is on. This is causing part of the icon/button to be hidden below the bottom of the screen and is forcing the date/time text to align on the bottom of the white strip instead of the horizontal-centre as it is initially. After enabling/disabling of the "enhance contrast in colours" feature, the colours don't revert back to brown but stay as blue. Screenshots of before/after are attached. http://launchpadlibrarian.net/29313029/before.png http://launchpadlibrarian.net/29313029/before.png"
http://launchpadlibrarian.net/29313036/after.png
I can confirm the contrast issues on ubuntu karmic beta! when enabling the higher contrast it seems that another theme is used, but when i switch it off i expect it to turn into the black theme as it was before.
*** This bug has been marked as a duplicate of bug 617665 ***
reopening, the theme changing issue is a different one from the other bug and not solved in using the git change
So does the same thing happen in the user's session when this dialog is shown? Enable a11y and "Accessibility features can be toggled with keyboard shortcuts".
the session one seems to be working correctly, only the gdm session has the issue
That's what it did (in GNOME 2.x): if (enabled) { gconf_client_set_string (client, KEY_GTK_THEME, HIGH_CONTRAST_THEME, NULL); gconf_client_set_string (client, KEY_ICON_THEME, HIGH_CONTRAST_THEME, NULL); /* there isn't a high contrast metacity theme afaik */ } else { gconf_client_unset (client, KEY_GTK_THEME, NULL); gconf_client_unset (client, KEY_ICON_THEME, NULL); gconf_client_unset (client, KEY_METACITY_THEME, NULL); } So the only reason why it wouldn't get reset properly is if you had the wrong theme as the default one in GConf (probably even just for gdm). In any case gnome-settings-daemon isn't doing anything wrong here.