Bug 322612 - Entering the the "Login Screen" menu resets color scheme
Summary: Entering the the "Login Screen" menu resets color scheme
Status: RESOLVED DUPLICATE of bug 254430
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_colors (show other bugs)
Version: 4.10.5
Platform: Other Linux
: NOR minor
Target Milestone: ---
Assignee: Matthew Woehlke
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-20 12:15 UTC by Mircea Kitsune
Modified: 2013-07-21 01:06 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mircea Kitsune 2013-07-20 12:15:44 UTC
If you enter the menu for configuring login screen settings, your color scheme is permanently changed to the default scheme or root's scheme.

Reproducible: Always

Steps to Reproduce:
1. Make sure you're using a custom color scheme under Application Appearance - Colors, which is also separate from that of root.

2. Go to System Settings - System Administration - Login Screen.

3. Leave the Login Screen menu. Either click the 'back' button or close the window.
Actual Results:  
If you open a new program, you will notice the widget has a different color set. If you return to Application Appearance - Colors, you notice a new scheme is selected and applied.

Expected Results:  
The color scheme should not be modified when entering any menu.

Noticed on openSUSE 12.3 64bit, KDE 4.10.5. After the issue occurs, its effect can be fixed by applying your desired color scheme again. The error is persistent, so if you re-log without setting your scheme back, the color scheme applied by the bug will be worn by the desktop.

A possible cause could be that the Login Screen section requires root authentication. So perhaps it copies the color scheme from root to apply visually, but forgets to set it back so it becomes applied to the user.
Comment 1 Christoph Feck 2013-07-21 01:06:05 UTC

*** This bug has been marked as a duplicate of bug 254430 ***