Knurpht-openSUSE wrote:

Op zaterdag 7 maart 2020 23:39:29 CET schreef Per Jessen:

...

On my newly installed TW system (KDE Plasma), when the screen locks, this process takes up about 100% CPU :

/usr/lib64/libexec/kscreenlocker_greet --graceTime 5000 --ksldfd 34

office25:~ # top top - 13:43:50 up 1:33, 8 users, load average: 3.00, 2.98, 2.85 Tasks: 173 total, 2 running, 171 sleeping, 0 stopped, 0 zombie %Cpu(s): 47.4 us, 0.0 sy, 52.6 ni, 0.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 3633.961 total, 1308.312 free, 1117.316 used, 1208.332 buff/cache MiB Swap: 4095.996 total, 4095.996 free, 0.000 used. 2033.125 avail Mem

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 4196 root 30 10 612232 320472 14760 S 105.0 8.612 88:47.01 mprime 10453 per 20 0 707696 126968 68092 R 94.02 3.412 17:36.51 kscreenlocker_g 1355 root 20 0 299044 78432 61900 S 0.332 2.108 0:12.58 X

(this is maybe 10minutes after it locked).

I look forward to anyone helping me resolve this.

What's the video card in use?

It's a standard built-in Intel Corporation 82Q35 Express Integrated Graphics Controller. Nothing fancy, just an office desktop machine.

I read in the other thread that Plasma crashes on OpenGL, does it do that for a newly created fresh user, with only defaults?

It's a brand new TW installation, it crashed on the very first start-up. I could try creating a new user, but I don't think it'll make any difference. -- Per Jessen, Zürich (5.9°C) -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org

Felix Miata wrote:

Per Jessen composed on 2020-03-08 10:10 (UTC+0100):

...

It's a standard built-in Intel Corporation 82Q35 Express Integrated Graphics Controller. Nothing fancy, just an office desktop machine.

~14 year old technology, the first series of the GMA line of GPUs replacing the earlier Intel Extreme Graphics: https://en.wikipedia.org/wiki/Intel_GMA#Gen3

https://en.wikipedia.org/wiki/List_of_Intel_graphics_processing_units#Third_...

They're so old that they missed getting support from the modesetting DDX that supports AMD and NVidia GPUs as well as Intel's.

I have two motherboards with that generation. I've installed ATI PCIe cards in both, taking their Intel GPUs out of active duty, to greatly improve video performance.

If you're going to keep using it for Plasma I suggest to deselect "Enable compositor on startup" if you haven't done so already.

I think that happened automatically when kwin crashed. Maybe not, I'll check. I don't need performance, this machine is just installed as a "console" in a rack downstairs. It's typically used for running minicom, maintaining our inventory database, looking up specs or manuals, checking various sensors and such. -- Per Jessen, Zürich (9.6°C) -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org

On 08/03/2020 10.16, Per Jessen wrote:

Dave Howorth wrote:

...

On Sat, 07 Mar 2020 23:39:29 +0100 Per Jessen <> wrote:

...

On my newly installed TW system (KDE Plasma), when the screen locks, this process takes up about 100% CPU :

...

...

...

(this is maybe 10minutes after it locked).

I look forward to anyone helping me resolve this.

Best suggestion; ditch KDE and go with XFCE or LXDE/LXQt :)

Hmm, you might be right. I prefer KDE, but for this machine it might not be so important.

Or just disable the screen saver. Go to black or better, energy save. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)

Carlos E.R. wrote:

On 08/03/2020 10.16, Per Jessen wrote:

...

Dave Howorth wrote:

...

On Sat, 07 Mar 2020 23:39:29 +0100 Per Jessen <> wrote:

...

On my newly installed TW system (KDE Plasma), when the screen locks, this process takes up about 100% CPU :

...

...

...

...

(this is maybe 10minutes after it locked).

I look forward to anyone helping me resolve this.

Best suggestion; ditch KDE and go with XFCE or LXDE/LXQt :)

Hmm, you might be right. I prefer KDE, but for this machine it might not be so important.

Or just disable the screen saver. Go to black or better, energy save.

Well, I want to lock the screen, that's the important bit. -- Per Jessen, Zürich (10.3°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org

Dave Howorth wrote:

On Sun, 08 Mar 2020 16:26:19 +0100 Per Jessen wrote:

...

Carlos E.R. wrote:

...

On 08/03/2020 10.16, Per Jessen wrote:

...

Dave Howorth wrote:

...

On Sat, 07 Mar 2020 23:39:29 +0100 Per Jessen <> wrote:

...

On my newly installed TW system (KDE Plasma), when the screen locks, this process takes up about 100% CPU :

...

...

...

...

(this is maybe 10minutes after it locked).

I look forward to anyone helping me resolve this.

Best suggestion; ditch KDE and go with XFCE or LXDE/LXQt :)

Hmm, you might be right. I prefer KDE, but for this machine it might not be so important.

Or just disable the screen saver. Go to black or better, energy save.

Well, I want to lock the screen, that's the important bit.

xlock?

I think someone already suggested that, but it still ends up running kscreenlocker_greet. -- Per Jessen, Zürich (8.5°C) -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org

Dave Howorth wrote:

On Sun, 08 Mar 2020 17:30:02 +0100 Per Jessen wrote:

...

...

...

Well, I want to lock the screen, that's the important bit.

xlock?

I think someone already suggested that, but it still ends up running kscreenlocker_greet.

That sounds bizarre. Regular xlock draws its own displays. It might be worth digging into exactly what 'xlock' is on your system and maybe changing it to use different options.

I might be mixing things up - someone suggested using another lock-thingie.

BTW, have you seen: https://bugs.kde.org/show_bug.cgi?id=316348

Not sure if I've seen that one specifically, but when I googled, I did come across a few similar ones. There is no doubt this is a graphics issue. This machine was happily running 13.2 earlier, and I really had no reason to upgrade. Just a spur-of-the-moment decision to try out TW. I guess I'm a little annoyed with myself - I didn't want to end up tinkering. -- Per Jessen, Zürich (7.0°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org

Op zondag 8 maart 2020 17:56:34 CET schreef Knurpht-openSUSE:

Op zondag 8 maart 2020 17:30:02 CET schreef Per Jessen:

...

Dave Howorth wrote:

...

On Sun, 08 Mar 2020 16:26:19 +0100

Per Jessen wrote:

...

Carlos E.R. wrote:

...

On 08/03/2020 10.16, Per Jessen wrote:

...

Dave Howorth wrote: > On Sat, 07 Mar 2020 23:39:29 +0100 Per Jessen <> wrote: >> On my newly installed TW system (KDE Plasma), when the screen

...

>> locks, this process takes up about 100% CPU : ...

...

>> (this is maybe 10minutes after it locked). >> >> I look forward to anyone helping me resolve this. > > Best suggestion; ditch KDE and go with XFCE or LXDE/LXQt :)

Hmm, you might be right. I prefer KDE, but for this machine it might not be so important.

Or just disable the screen saver. Go to black or better, energy save.

Well, I want to lock the screen, that's the important bit.

xlock?

I think someone already suggested that, but it still ends up running kscreenlocker_greet.

I guess that's still being triggered from Plasma's powermanagement. Then again 'xlock' returns nothing on a zypper search or locate. FWIW it's in Workspace Behaviour - Screenlocker

I installed xlockmore, it has an awful lot of options and should somehow be loaded in the powersaving options of Plasma if you disable kscreenlocker -- Gertjan Lettink a.k.a. Knurpht openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org

Op zondag 8 maart 2020 16:26:19 CET schreef Per Jessen:
> Carlos E.R. wrote:
> > On 08/03/2020 10.16, Per Jessen wrote:
> >> Dave Howorth wrote:
> >>> On Sat, 07 Mar 2020 23:39:29 +0100 Per Jessen <> wrote:
> >>>> On my newly installed TW system (KDE Plasma), when the screen
> > 
> >>>> locks, this process takes up about 100% CPU :
> > ...
> > 
> >>>> (this is maybe 10minutes after it locked).
> >>>> 
> >>>> I look forward to anyone helping me resolve this.
> >>> 
> >>> Best suggestion; ditch KDE and go with XFCE or LXDE/LXQt :)
> >> 
> >> Hmm, you might be right.  I prefer KDE, but for this machine it might
> >> not be so important.
> > 
> > Or just disable the screen saver. Go to black or better, energy save.
> 
> Well, I want to lock the screen, that's the important bit.
Can you try this: 
- Hit Alt-F2
- Type 'plasma renderer', click it
- Set it from "Automatic" to "Software", Apply
- Start the screenlocker and see if the issue persists. 

-- 
Gertjan Lettink a.k.a. Knurpht
openSUSE Forums Team


-- 
To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse-support+owner@opensuse.org

Op zondag 8 maart 2020 19:41:05 CET schreef Per Jessen:

Knurpht-openSUSE wrote:

...

Op zondag 8 maart 2020 16:26:19 CET schreef Per Jessen:

...

Carlos E.R. wrote:

...

On 08/03/2020 10.16, Per Jessen wrote:

...

Dave Howorth wrote:

...

On Sat, 07 Mar 2020 23:39:29 +0100 Per Jessen <> wrote: > On my newly installed TW system (KDE Plasma), when the screen

...

...

> locks, this process takes up about 100% CPU : ...

...

...

> (this is maybe 10minutes after it locked). > > I look forward to anyone helping me resolve this.

Best suggestion; ditch KDE and go with XFCE or LXDE/LXQt :)

Hmm, you might be right. I prefer KDE, but for this machine it might not be so important.

Or just disable the screen saver. Go to black or better, energy save.

Well, I want to lock the screen, that's the important bit.

Can you try this: - Hit Alt-F2 - Type 'plasma renderer', click it - Set it from "Automatic" to "Software", Apply - Start the screenlocker and see if the issue persists.

Aha, that seems to have made a difference - both with a manual lock and the automatic timed lock, kscreenlocker_greet now takes up less than 1% CPU. Nice. It also felt like the system is overall more responsive.

Any explanation as to what the issue is/was ? Not really. Seems to be a qt-quick only issue. I ran into some bug reports mentioning Qt-quick, then remembered a friend talking about that, so gave her a call. The bit she remembered was the Alt-F2, plasma rendererer, so we compared her values to mine. She stated that she got it from some bug report on kscreenlocker, but could not provide some reference. Mind, I'm glad you seem to have a solution now, and hope you will continu making posts on the opensuse@ML as before. That was never my goal or intention, the only thing I was looking for was a fix/workaround without having to tinker on system level.

-- Gertjan Lettink a.k.a. Knurpht openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org

Carlos E. R. wrote:

El 2020-03-08 a las 16:26 +0100, Per Jessen escribió:

...

Well, I want to lock the screen, that's the important bit.

Ah, but it is the screen locker part, not the screen saver?

I think so. kscreenlocker_greet is looping.

These things usually happen when the screen saver tries to display a complex graphic animation. Just asking for a password shouldn't.

I chose a plain colour for the background. Given that Gertjan's suggestion of opting to use "Software" worked like a charm, that is a strong indicator that the problem is in the graphics card support. Or perhaps rather in recognising when required features are not available :-) -- Per Jessen, Zürich (4.5°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org