[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5
From:       Gianni <bugzilla_noreply () kde ! org>
Date:       2018-08-09 13:33:20
Message-ID: bug-347772-17878-TFKfZSlNlQ () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=347772

--- Comment #36 from Gianni <gianni_2295@hotmail.it> ---
(In reply to David Edmundson from comment #35)

> Compositor settings affect only the window manager. GL clients will still use GL.
> This setting affects only the clients (plasmashell / systemsettings / whatever)
> There are reasons to mix and match those two.

Thanks for explaining me.

> In the meantime, you can export 
> QT_QUICK_BACKEND=software globally and confirm if that fixes it.

I confirm that setting this env variable fixes the kscreenlocker_greet cpu
issue for me!

> > Unfortunately this setting breaks something because I can't see the themes \
> > preview anymore in system settings -> workspace themes.
> 
> That was reported and fixed this week.

Nice to hear! I hope to see this in the next bugfix update.

In conclusion if I got this correctly the cpu issue was related to qt quick
having bad performance issues (during screen lock) with outdated hardware not
providing or providing an inefficient opengl backend. This is solved with
setting the "plasma renderer" to "software", but this (until there's the patch
you mentioned) doesnt comprehend kscreenlocker (or qtQuick?) so as a temporary
workaround I also have to set QT_QUICK_BACKEND=software globally.

-- 
You are receiving this mail because:
You are watching all bug changes.=


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic