Summary: | Screen locker freezes with transparent themes | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Nikita Zlobin <nick87720z> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | hugo.pereira.da.costa, yyc1992 |
Priority: | NOR | ||
Version: | 4.11.3 | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Nikita Zlobin
2013-11-24 18:17:58 UTC
Don't think this is kwin's problem. I've noticed this problem in QtCurve recently but don't know what to do about it yet. Related bug: https://bugs.kde.org/show_bug.cgi?id=312425 https://bugs.kde.org/show_bug.cgi?id=311574 https://bugs.kde.org/show_bug.cgi?id=314663 (probably duplicated) "kscreenlocker" &"kscreenlocker_greet" processes are hardcoded to skip ARGB in bespin. KWin is completely unrelated here - it's between styles and the screensaver (fiddling areound with the window, resp. not catching that) *** This bug has been marked as a duplicate of bug 314663 *** @Nikita Zlobin (I thought said this somewhere else but cannot find it...) In QtCurve you can also blacklist those processes. I haven't tested myself but it should work. @Thomas Do not set to ARGB when a window already exist and when X11BypassWindowManagerHint is set seems to help. And we probably don't want translucency on such a window anyway. |