[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#381069: marked as done (causes excessive CPU usage by Xorg)

Your message dated Sun, 03 Jun 2007 22:00:32 +0200
with message-id <46631DE0.3060402@ens-lyon.org>
and subject line Bug#381069: causes excessive CPU usage by Xorg
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: libxslt1.1
Version: 1.1.17-2

top shows that Xorg process eats too much CPU time -- it's grown up to
40% when I were moving the mouse. And everything is slow when X is on
screen.

xserver-xorg 1:7.0.22
xserver-xorg-core 1:1.0.2-9
libc6 2.3.6-13
libgcrypt 1.2.2-1
libgpg-error0 1.2-1
libxml2 2.6.26.dfsg-1
Linux delsoft 2.4.27-3-k7 #1 Tue May 30 00:34:05 UTC 2006 i686 GNU/Linux

Version 1.1.16-2 works well (luckily, I quickly found an unupdated
repository).

I have had such problem when using Sarge with backports, Xorg 6.x could
it up to 80-90%, but I couldn't notice which package caused it then.
Didn't try to reproduce this bug this time (the bug is too bad), but
then it was consistently annoying.

Probably it is caused by some of the backport libraries that I don't
update out of fear of a problem I had long ago in Etch (audio players
crashed often):
libxaw7, libxcomposite1, libxdamage1,libxkbui1, libxmu6,libxmuu1,
libxp6, libxpm4, libxss1, libxtrap6, libxtst6, libxxf86dga1,
libxxf86misc1 all seem to be 6.9.0.dfsg.1-5bpo2 (didn't check every of
them, aptitude shows 6.9.0.dfsg).

--- End Message ---
--- Begin Message --- 
Aleksej wrote:
> Hi, thanks for the reminder. I don't even remember what fixed it and
> when; I'm running the latest Etch now. I think it might have disappeared
> when I updated the rest of libraries that were from backports. You can
> close the bug.
>   

Ok, thanks, closing.

Brice

--- End Message ---
Reply to: