Bugzilla – Bug 502568
gnome-session causes X to run with high cpu usage
Last modified: 2009-07-15 07:59:50 UTC
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.10) Gecko/2009042700 SUSE/3.0.10-2.1 Firefox/3.0.10 gnome-session causes 50% cpu usage per core on a dual core cpu (100% on a single core cpu?) Updated to gnome 2.26.1 from the following repositories: http://download.opensuse.org/repositories/GNOME%3a/STABLE%3a/2.26/openSUSE_11.1/ http://download.opensuse.org/repositories/GNOME:/Backports:/2.26/openSUSE_11.1/ gnome-session version 2.26.1-1.6 xorg-x11-server version 7.4-17.7.5 Reproducible: Always Steps to Reproduce: 1. 2. 3.
Can you try to install the xorg-x11-server from http://widehat.opensuse.org/repositories/home:/MBoman/openSUSE_11.1/ That's what I'm using and I don't see these issues.
I have tried that too, but it doesn't solves the problem for me (with vino-server running I still get high cpu)
I see a similar issue with KDE and the Xorg process of an idle user having a high CPU usage. I presume this is the same story. I installed the xorg-x11-server suggested above to see if it helps. Time will tell (or I will). I cleared the needinfo flag as I suppose Istvan just forgot to do it.
(In reply to comment #1) > Can you try to install the xorg-x11-server from > http://widehat.opensuse.org/repositories/home:/MBoman/openSUSE_11.1/ > > That's what I'm using and I don't see these issues. Doesn't solve the issue for me either.
I'm not sure you are having the same problem as I do, because I think this is related to gnome only. But maybe not. Anyways i have found a workaround for the problem: turning off vino-server. So at this stage I cannot decide what causes the problem, the gnome-session, the xorg-x11-server or vino-server? (In reply to comment #4) > (In reply to comment #1) > > Can you try to install the xorg-x11-server from > > http://widehat.opensuse.org/repositories/home:/MBoman/openSUSE_11.1/ > > > > That's what I'm using and I don't see these issues. > > Doesn't solve the issue for me either.
Installing the latest update fixed this problem