Bug 1541021 - Inconsistent panel color on login screen
Summary: Inconsistent panel color on login screen
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-shell
Version: 7.5
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Florian Müllner
QA Contact: Desktop QE
Jana Heves
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-01 14:34 UTC by Martin Krajnak
Modified: 2018-06-27 13:15 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
Inconsistent panel color on login screen When logging to a *GNOME Classic* session, suspending the laptop and resuming it again, the top panel on login screen is white, instead of black. This problem does not affect *GNOME Classic* functionality.
Clone Of:
Environment:
Last Closed: 2018-06-27 13:13:46 UTC
Target Upstream Version:

Attachments (Terms of Use)
photo of lockscreen (237.29 KB, image/jpeg)
2018-02-01 14:34 UTC, Martin Krajnak 		no flags Details
View All

Description Martin Krajnak 2018-02-01 14:34:48 UTC 
Created attachment 1389539 [details]
photo of lockscreen

Description of problem:
See provided photo.

Version-Release number of selected component (if applicable):
gnome-shell-3.26.2-2.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1.Login to Gnome classics session
2.Suspend the laptop (Search for suspend in gnome-shell)
3.Wake up the computer from sleep

Actual results:
The top panel on lock screen is white

Expected results:
The top panel on lock screen should be black
Comment 4 John Hodrien 2018-05-02 10:59:26 UTC 
I don't think there's any need to suspend.  Login to gnome-classic, lock screen, start to unlock screen, see it's the wrong colour.  I've observed this behaviour with gnome-shell-3.26.2-5.el7.x86_64 on CentOS 7 CR.
Comment 5 Martin Krajnak 2018-06-27 13:13:46 UTC 
I am not able to reproduce with gnome-shell-3.28.2-1.el7.x86_64, so it is fixed by rebase
Note You need to log in before you can comment on or make changes to this bug.