*** This bug is a duplicate of bug 307306 ***
    https://bugs.launchpad.net/bugs/307306

This comment is for those novise like me who mainly want a working
system and are not primarilly looking to fix the bug.

I had the described problem after upgrading from Intrepid to Jaunty a
couple of weeks ago. Xorg always over 30% CPU and often over 80%, even
though I wasn't doing anything.

Running Dell Latitude E6400, 4 gig memory etc. I did try to kill power-
manager and settings-daemon without any result. No vino-server running.

The behavior disappeared when I downgraded all xserver-xorg-<whatever>
packages back to the Intrepid version, and now the system is faster than
ever:-)

Since you who will go for this solution probably are as novice as me I
will outline just how I did the downgrade (which might not be the
standard way, I don't know).

edit the file /etc/apt/sourses.list (for instance sudo vim 
/etc/apt/sourses.list)
Comment out all lines including the word 'jaunty' (put # in front of the line)
#deb http://fr.archive.ubuntu.com/ubuntu/ jaunty main multiverse universe 
restricted
#deb-src http://fr.archive.ubuntu.com/ubuntu/ jaunty main multiverse universe 
restricted
#deb http://fr.archive.ubuntu.com/ubuntu/ jaunty-updates main multiverse 
universe restricted
#deb-src http://fr.archive.ubuntu.com/ubuntu/ jaunty-updates main multiverse 
universe restricted

add the following line (probably overkill with multiverse universe etc., I 
don't know)
deb http://fr.archive.ubuntu.com/ubuntu/ intrepid main multiverse universe 
restricted

save the file and do
sudo apt-get update

run aptitude (or your favourite package manager) and downgrade the following 
packages, including their dependencies (in my case 34 dependencies):
xserver-xorg
xserver-xorg-core
xserver-xorg-input-all
xserver-xorg-video-all

remember to uncomment the sources.list file and run 'sudo apt-get
update' to reset jaunty repositories (and do not update xserver packages
as suggested).

-- 
jaunty xorg 100% cpu usage
https://bugs.launchpad.net/bugs/309776
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to