More often than not on login, KDE will successfully start up, but will fail to load any transparency effects. This is repeatable, and can be fixed each time by changing the Qt graphics engine from Raster to Native and back again. This bug is does not apply to the open-source ati video drivers, only fglrx. Reproducible: Always Steps to Reproduce: 1. Reboot system. 2. Observe effects that failed to load. 3. Change Qt graphics engine to fix. Actual Results: The effects are successfully loaded after following the above steps. Zerobin paste with relevant information such as ~/.xsession-errors and the output of lspci. http://sebsauvage.net/paste/?6fc0497eea857830#bLvdqkYmJUvCzL3cvqeMgGiOca39I32KuNqpOobSRwQ=
The xsession error log does not indicate that compositing was suspended or kwin crashed etc. a) Please ensure to enable "1212" in "kdebugdialog" (to print more kwin debug out, "kdebugdialog --fullmode" allows you to redirect that into an extra file) b) please provide the output of "qdbus org.kde.kwin /KWin supportInformation" when compositing "failed" (ie. right after login) c) does pressing Shift+Alt+F12 (once or twice) bring back compositing? d) "kwin --replace &" will likely clear the stage as well (changing the graphicssystem implicitly triggers a restart of the process)
Here is the content of qdbus org.kde.kwin /KWin supportInformation: http://sebsauvage.net/paste/?3991d6b38a7bf235#ZrkHMBGz4SoFZCfP36YhmCngtSnxZMWl3MItElTJ8PE= Pressing Shift+Alt+F12 twice does bring back compositing.
(In reply to comment #2) > Here is the content of qdbus org.kde.kwin /KWin supportInformation: > > http://sebsauvage.net/paste/ > ?3991d6b38a7bf235#ZrkHMBGz4SoFZCfP36YhmCngtSnxZMWl3MItElTJ8PE= Compositing is active. How do you determine it's not? Pot. bug #323065 ?
Created attachment 82396 [details] Lack of transparency example.
The bug is similar, but I'm not entirely sure if we're having the same exact problem. I'm having similar problems with the drawing of corners upon resizing and maximizing. In the poster's attachments, I can see the lack of drawn drop shadow, but the panel looks completely normal. Also, I apologize for my unclear wording. Compositing may be working just fine, and only the transparency effect may be failing to load. However, similar to the bug you linked me to, when these effects are disabled and I attempt to use one of them (e.g. Lava lamp minimization), kwin crashes. I figure this is standard behavior though.
plasma initially not noticing that compositing is active (thus loading the opaque theme) would be bug #320959 (not bug #179042 which was about runtime changes which apparently work and "fix" the problem for you now) I assume you can alter the translucency of windows (or the translucency effect in "kcmshell4 kwincompositing" works when moving/resizing a window)? -------- About crashing when loading an effect: no, that's not standard behavior ;-) The crashes there occured on a broken patch which never went upstream in that state. If you get a backtrace, please file a new bug (in case bugzilla doesn't point you to a dupe anyway)
Yes, on the occasion that I log in and everything is working, translucency when dragging/resizing works as well. Should I find that the crash that occurs when no effects are loaded and are attempted to be ran is repeatable, would it be beneficial to file another bug report?
(In reply to comment #7) > Yes, on the occasion that I log in and everything is working, translucency > when dragging/resizing works as well. That's not what i meant. The question is whether translucency when dragging/resizing works *despite* the plasma-desktop panels/popups are *not* translucent. If so (and also present windows etc. works), this is bug #320959 - otherwise not. > attempted to be ran is repeatable, would it be beneficial to file another > bug report? If you get a backtrace: yes please, report the crash (or attach to the present dupe, if any)
ping?
(In reply to comment #8) > The question is whether translucency when dragging/resizing works *despite* > the plasma-desktop panels/popups are *not* translucent. > If so (and also present windows etc. works), this is bug #320959 - otherwise > not. I think I'm also affected by this bug, and here translucency works when dragging/resizing despite the panel not being translucent.
Just noticed that pressing Shift + Alt + F12 twice does not bring panel-translucency back, but kwin --replace did.
Try waiting longer between the shortcuts. KWin delays releasing the CM selection (ie. informs other clients with a little delay to skip that altogether for very short changes eg. when the compositor just needs to be restarted or so)
Ah, sorry, you're right. So it's bug #320959 ? Seems like there's no action in that bug.
Is very most likely that bug, yes (i CC'd you there) No idea about the progress in that regard and don't know the relevant plasma-desktop code good enough, sorry. @Parker We still lack determination on whether you're facing bug #320959 as well, please see comment #8
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
This issue report is quite old. Can you please confirm, that it still persists with Plasma 5.23?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!