Bug 194080

Summary:	Dual X-session consumes 100% cpu load after inactive screen auto-locks
Product:	[I don't know] kde	Reporter:	Jeroen van Disseldorp <jdizzl>
Component:	general	Assignee:	Unassigned bugs <unassigned-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	nate
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Jeroen van Disseldorp 2009-05-25 21:31:46 UTC

Version:           4.3 beta 1 (using KDE 4.2.85)
Compiler:          N/A N/A
OS:                Linux
Installed from:    Ubuntu Packages

I installed KDE 4.3 beta 1 from Kubuntu's (Jaunty) experimental repository. My girlfriend and I use a dual-X-session setup, switching users/desktops with CTRL-F7 and CTRL-F9 for each of our desktops. This works great until the inactive desktop in the background auto-locks the screen. After that the x.org of the inactive user eats away 100% cpu time (100% on Athlon X2).

Switching desktops and unlocking the previously inactive screen allows the CPU to drop to the normal 4-5% again. CPU load spikes again as soon as the next background desktop is locked.

I witnessed this behaviour already since I started using KDE 4.2 betas, so might be an older bug.

KDE: 4.3 beta 1, packages from Experimental repository
Distro: Kubuntu Jaunty
Machine: Athlon 64 X2 4600+
Graphics: ATI Radeon X550

If you need any more info, please let me know.

Comment 1 Jeroen van Disseldorp 2009-07-04 11:59:22 UTC

The problem remains present in 4.3b2 and 4.3rc1. Not sure if this is an x.org issue or KDE, but it does not seem to stem from the graphics card driver: I changed graphics cards 2 weeks ago from ATI to NVidia (with proprietary drivers), but witnessed no change in behavior.

Comment 2 Andrew Crouthamel 2018-11-02 23:01:14 UTC

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!

Comment 3 Andrew Crouthamel 2018-11-16 05:38:08 UTC

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?

Thank you for helping us make KDE software even better for everyone!

Comment 4 Nate Graham 2020-09-28 23:02:16 UTC

No response; assuming it was fixed since then.