After upgrading my Ubuntu 12.10 machines from 4.9.x to 4.10 RC2 on both shadows were not drawn correctly most of the time. There were small white or big white borders instead. Here is a nice screenshot showing all kinds of shadow (mis)behavor (small border, ok, big border): http://dl.dropbox.com/u/28750014/air_shadows.png This also changed the way my panel looks: http://dl.dropbox.com/u/28750014/air_transparency.png After reading the post about the new Air theme at notmart.org I guess that's the intended look. Additional HW info although I do not think that it is a driver issue: * machine 1: Radeon HD4670, radeon driver * GeForce 8800 GTS 640MB, nouveau driver) Reproducible: Always Steps to Reproduce: 1. Use the default Air theme 2. Upgrade to KDE 4.10 RC2 with the reworked theme 3. Restart KDE Actual Results: Shadows effect drew additional lines, panel transparency 100% Expected Results: Shadows effect only drawing the shadows, panel transparency as shown over at notmart.org Additional gfx hw / driver info: * binaries from kubuntu-ppa/beta * machine 1: Radeon HD4670, radeon driver (stock) * machine 2: GeForce 8800 GTS 640MB, nouveau driver (stock)
The first screenshot shows folderview plasmoids on the desktop, right? That's not related to kwin, plasma-desktop internal stuff. Either the theme or the theme pixmap rendering is broken. On the second shot, the shadows (of the right panel) actually seem to be ok, just the theme is completely garbled. Please open konsole, run kquitapp plasma-desktop # (your desktop is gone) rm /var/tmp/kdecache-`whoami`/plasma_theme_* # delete cached theme plasma-desktop # desktop back and see what happens.
Right, the first screenshot shows the folderview plasmoid placed on the desktop. Sorry for assigning the wrong product / component, kwin was my best guess as I thought the shadows were the root cause. I'll change it to plasma / general. I ran the commands, the panel still looks as on the right, I didn't get the transparency back. Invalidating caches might have been what happened when I switched the theme to something elese an back, however, I did not reproduce the initial situation before running the commands as that would involve downgrading to pre 4.10 RC1 and upgrading again. Mabe I'll have time to do so over the weekend.
If the only remaining issue is the panel transparency (but the theme doesn't look all weird anymore - assuming that's not the intended look ;-) see http://git.reviewboard.kde.org/r/107983/
I also had problems after updating to 4.10 RC3 with the plasma panel transparency. Comment #1 helped me solving this issue: kquitapp plasma-desktop rm /var/tmp/kdecache-`whoami`/plasma_theme_* plasma-desktop Thanks for the hint !
I've also been able to fix transparency problem of panels by following the suggestion on comment #1, but every time I reboot my panels loose the transparency effects, and I have to fix it again. Am I the only one experiencing this? Using Catalyst legacy driver 13.1 on Mobility HD3470 under ArchLinux. BTW, I have no /var/tmp/kdecache-`whoami` folder, but rather (being "mori" my username) /var/tmp/kdecache-moriUh8IcR. I don't know if this is related to the problem (I guess no...).
KDE 4.10: Nicola Mori, you are not the only one. The same happens to me: I fix transparency problem with comment #1 but I loose the transparency effects at reboot. This happen to me since I installed the Nvidia drivers 310.32 64 bit. With the previous driver version didn't happen! Thank you Luca
Comment #1 will only help you in cleaning up plasmas cache explicitly after an upgrade. The fact that plasma cannot detect the compositing state is vastly discussed here: https://git.reviewboard.kde.org/r/107983/ KWin tabbox is supposed to work around this issue, but the workaround is partially to pretty broken.
Ok, thanks for the quick answer. So, can we go on writing in this thread or we just have to wait the fix?
(In reply to comment #8) > Ok, thanks for the quick answer. > So, can we go on writing in this thread or we just have to wait the fix? I'm not involved in plasma development, but if you want to discuss that KWindowSystem::compositingChanged() does not work: there's a long term bug (see RR) about that and i doubt this one is any related. Just with kwin starting threaded, the old bug seems to be more exposed (because many ppl. notice because plasma does not even get the initial status right)
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