Bug 206624 - CPU on 100% after creating a new X11 session
Summary: CPU on 100% after creating a new X11 session
Status: RESOLVED WORKSFORME
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-07 13:48 UTC by dcent
Modified: 2020-10-29 04:33 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dcent 2009-09-07 13:48:15 UTC
Version:           4.3.0 (using KDE 4.3.0)
Compiler:          gcc 4.3 
OS:                Linux
Installed from:    SuSE RPMs

I have desktop effects turned on. When I start a 2nd X-session from KDE, the 1st core of my dual-core CPU is on 100%. 
Solution: go back to 1st session by pressing Ctrl+Alt+F7 - after changing back, CPU load is back to 0% (but this is annoying)

OpenSuSE Linux 11.1
KDE 4.3 (from download.opensuse.org)

This also happened on previous KDE4 versions.
Comment 1 Dario Andres 2009-09-07 14:29:41 UTC
- Does this also happen if desktop effects are disabled ?
Thanks
Comment 2 dcent 2009-09-07 14:36:19 UTC
(In reply to comment #1)
> - Does this also happen if desktop effects are disabled ?
> Thanks

No - and when I activate effects later again in the same session, the problem doesn't appear as well.
Comment 3 Dario Andres 2009-09-07 14:37:06 UTC
- What is your graphics card / drivers ?
Adding KWin people to CC
Thanks
Comment 4 dcent 2009-09-07 14:44:56 UTC
I have a NVidia GeForce NX8600GT (256 MB), using the G02-driver package (version 185.18.14 - "rpm -qa | grep nvidia" says: nvidia-gfxG02-kmp-pae-185.18.14_2.6.27.23_0.1-2.2)
Comment 5 Martin Flöser 2009-09-07 14:58:30 UTC
I know that problem - have it all the time :-(
Actually I doubt it is a kwin problem, but I think it's a bug in the nvidia driver. I experience it most often when coming from suspend.
Comment 6 dcent 2009-09-07 15:02:53 UTC
Yeah, I always suspend my system and have the problem. I hope this can be fixed soon.
Comment 7 Thomas Lübking 2009-09-07 15:40:12 UTC
How do you start the second X?
"X :1 & sleep 4; xterm -display :1" creates high cpu load on :0 here as well, but "X :1 & sleep 4; xterm -display :1 & exit" does not...
(i noticed that konsole infinitly created newlines until i returned to :0, so i simply exited that bash)
Comment 8 Martin Flöser 2009-09-07 15:43:17 UTC
(In reply to comment #7)
> How do you start the second X?
I use the normal "new session"/"Benutzer wechseln" from inside KRunner
Comment 9 dcent 2009-09-07 15:44:34 UTC
I always used the KMenu for the 2nd X (KMenu -> Leave -> Switch User).
Comment 10 Thomas Lübking 2009-09-07 16:05:18 UTC
ok, krunner also locks the screen - no problem by my default (blank screen) but selecting a screensaver (flurry...) causes full cpu load in the screensaver - until i switch to :0 or VT1
Comment 11 Martin Flöser 2009-09-07 16:13:21 UTC
in my situation neither a screensaver is used nor a locked screen. KRunner locks the screen but later on I switch by ctral+alt+fx, so the screen isn't locked any more (yeah I know I have to be careful whenever I leave my computer, as there is the second unlocked X on tty9 ;-)
Comment 12 Nate Graham 2020-09-29 23:43:20 UTC
I don't suppose you're still able to reproduce this in a recent version of Plasma 5, like 5.19 or later?
Comment 13 Bug Janitor Service 2020-10-14 04:33:18 UTC
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!
Comment 14 Bug Janitor Service 2020-10-29 04:33:38 UTC
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!