Summary: | Plasma theme (Oxygen) / panel lacks transparency since 4.2.1 upgrade | ||
---|---|---|---|
Product: | [Plasma] plasma4 | Reporter: | Thilo-Alexander Ginkel <thilo> |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | andresbajotierra, aseigo, christiandehne, drankinatty, finex, luisromangz, notmart |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
Screenshot
Screenshot of how the panel is supposed to look like |
Description
Thilo-Alexander Ginkel
2009-03-12 08:14:02 UTC
Created attachment 32038 [details]
Screenshot
Can you try with a clean user account too? With a new user account (without a .kde directory) the problem seems to happen with a 100% chance. For my own account I managed to get the old settings back (I assume it is related to changing some Desktop Effect settings; DE were enabled in the new account, BTW), which now looks again like in the attached screenshot. Created attachment 32064 [details]
Screenshot of how the panel is supposed to look like
I have the same problem. It started with KDE 4.2.1 and is still present in 4.2.2 using openSUSE. But for me it occurs only if I log in my KDE session when I am on battery power (powerdevil is configured to disable desktop effects in this case). After having logged in on battery power, I find no way to get a transparent panel, after plugging in my power cable and having desktop effects enabled. When I log in my KDE session while the power cable is plugged in, the panel is transparent. Now switching the desktop effects on and off changes the transparency. yes, KSelectWatcher isn't working reliably :/ *** Bug 203332 has been marked as a duplicate of this bug. *** The problem Aaron pointed (and the one causing this behaviour on panels) is reported at bug 179042, and seems to be worked on. *** This bug has been marked as a duplicate of bug 179042 *** *** Bug 212375 has been marked as a duplicate of this bug. *** |