Bug 303934 - Shutdown/logout dialogue drop-down options have no background.
Summary: Shutdown/logout dialogue drop-down options have no background.
Status: RESOLVED UNMAINTAINED
Alias: None
Product: plasma4
Classification: Plasma
Component: visuals (show other bugs)
Version: 4.10.60
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-22 21:18 UTC by Ian Stanistreet
Modified: 2018-06-08 19:02 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot showing the problem (19.34 KB, image/jpeg)
2012-07-22 21:19 UTC, Ian Stanistreet
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ian Stanistreet 2012-07-22 21:18:43 UTC
The drop-down options in the shutdown dialogue show the desktop or other windows through them -- as if there is a hole in the dialogue.  See the screenshot.

Reproducible: Always
Comment 1 Ian Stanistreet 2012-07-22 21:19:39 UTC
Created attachment 72685 [details]
Screenshot showing the problem
Comment 2 Lamarque V. Souza 2012-08-14 01:24:33 UTC
The background is transparent like all backgrounds in plasmoids (battery plasmoid, Plasma NM, etc) and tooltips in Plasma. You would have to disable transparency to prevent that from happening.
Comment 3 Ian Stanistreet 2012-08-14 09:09:04 UTC
The background is not simply transparent.  The dialogue background should be in front of the desktop but the drop-down simply shows the desktop through it instead of the dialogue background.
In the screenshot, the background of the drop-down should appear grey (like the dialogue) but it appears blue (like the desktop).

The stacking order should be:
1. Drop-down list
2. Shutdown dialogue
3. Desktop

But instead it appears to be like this:
1. Drop-down list
2. Desktop
Comment 4 Lamarque V. Souza 2012-08-14 15:18:08 UTC
Well, the stacking order is done by kwin as far as I know. Anyway, even when I remove all transparent/translucent flags used in ksmserver (the process what shows the dialog) it still shows a transparent background. So I do not know how to change that.
Comment 5 Ian Stanistreet 2012-08-15 10:19:10 UTC
Maybe this is a radeon issue.  My work computer (intel) isn't affected by it.  I can't think of any other difference.
Comment 6 Lamarque V. Souza 2012-08-17 16:19:51 UTC
Well, my notebook's gpu is an ATI hd4570 and I use the proprietary drivers.  Maybe Intel's driver does not support transparency in menus or you are not using kwin's opengl backend (if I recall correctly transparency does not in other kwin's backends).
Comment 7 David Edmundson 2013-06-06 19:46:23 UTC
Is this still the case for 4.10? I can't reproduce it here.
Comment 8 Lamarque V. Souza 2013-06-06 19:56:55 UTC
It seems fixed here too with 4.10.3.
Comment 9 Ian Stanistreet 2013-06-08 17:57:05 UTC
Not fixed for me, with 4.10.4.
Comment 10 Hrvoje Senjan 2013-06-09 00:22:01 UTC
I can also reproduce with git master...
Comment 11 rockonthemoonfm 2013-07-03 16:23:06 UTC
fixed to me in 4.10 beta 2. archlinux, intel snb.
Comment 12 rockonthemoonfm 2013-07-03 16:27:09 UTC
sorry1 4.11 beta 2. i really miss the comment [edit] feature in bugtracker.

apart that, drop-down dialogue is almost undiscoverable, i'm opening another bug on this regard.
Comment 13 Nate Graham 2018-06-08 19:02:27 UTC
Hello!

This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug is already resolved in Plasma 5.

Accordingly, we hope you understand why we must close this bug report. If the issue described  here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham