Bug 382662 - Leave screen dark
Summary: Leave screen dark
Status: RESOLVED DUPLICATE of bug 175642
Alias: None
Product: ksmserver
Classification: Unmaintained
Component: ui (show other bugs)
Version: 5.10.1
Platform: Fedora RPMs Linux
: NOR major
Target Milestone: ---
Assignee: Lubos Lunak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-24 15:42 UTC by SP
Modified: 2020-01-31 18:40 UTC (History)
4 users (show)

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


Attachments
photo of leave screen (77.56 KB, image/jpeg)
2017-07-24 15:42 UTC, SP
Details
dark leave screen (81.09 KB, image/jpeg)
2017-10-15 05:25 UTC, Eric L.
Details

Note You need to log in before you can comment on or make changes to this bug.
Description SP 2017-07-24 15:42:48 UTC
Created attachment 106830 [details]
photo of leave screen

When "Leave" is selected the overlay screen is so dark and lacking in contrast that the menu "Suspend, Shutdown, Logout, etc" cannot be read.  This has only occurred following the recent upgrade to Fedora 26 and KDE Plasma 5.10.1.  It is true for both my machines running identical hardware.  
Video card is:  Advanced Micro Devices, Inc. Tonga PRO Radeon R9 285/380
OS is 64-bit
16 GiB Ram
Comment 1 SP 2017-07-24 15:57:06 UTC
I am guessing this is an SDDM bug - but I cannot see where to file that so I have chosen "general".  The theme in use is "Breeze"
Comment 2 Christoph Feck 2017-08-02 11:03:22 UTC
I am not sure where the ksmserver theme comes from, but on my system, the text/buttons are bright.
Comment 3 Eric L. 2017-10-15 05:25:49 UTC
Created attachment 108358 [details]
dark leave screen

I have the same issue since I upgraded from f25 to f26, it did an update from plasma 5.9.5 to 5.10.5. Additionally I tried to autoremove packages, which I had to roll-back because it removed too many packages. I can provide more information if someone says what is required.

But first would be necessary to understand where the style of this leave screen is defined: I couldn't find any hint on the Internet where it might come from.
Comment 4 Nate Graham 2020-01-31 18:40:52 UTC
*** This bug has been marked as a duplicate of bug 175642 ***