Bug#429569: xorg: Xorg consumes a lot of cpu at screensaver exit
ubject: xorg: Xorg consumes a lot of cpu at screensaver exit Package: xorg Version: 1:7.2-5 Severity: critical Justification: breaks the whole system *** Please type your report below this line *** Hello, After a long period with a screensaver, when I would like to return to my desktop, xorg consumes 50% or more of the cpu!!! I could move the mouse and the applications are not freeze, but I can't do anything other than ctr/alt/f1 or del to kill the Xorg processus. If I would like to start an application or deploy a menu, I have to restart the computer. I'm using kde desktop and I'm using the random screensaver functionnality. I've xcreensaver installed. I'have a nvidia card. I could use nv ou nvidia driver, the result is the same. Thanks. -- System Information: Debian Release: lenny/sid APT prefers stable APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.21-1-686 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xorg depends on: ii eterm [x-terminal-em 0.9.4.0debian1-2Enlightened Terminal Emulator ii gnome-terminal [x-te 2.18.0-2The GNOME 2 terminal emulator appl ii konsole [x-terminal- 4:3.5.7-1 X terminal emulator for KDE ii libgl1-mesa-glx [lib 6.5.2-5 A free implementation of the OpenG ii libglu1-mesa 6.5.2-5 The OpenGL utility library (GLU) ii rxvt-beta [x-termina 2.7.10-3VT102 terminal emulator for the X ii rxvt-unicode [x-term 7.9-2 RXVT-like terminal emulator with U ii type-handling [not+s 0.2.19 dpkg architecture generation scrip ii xbase-clients1:7.1.ds1-2 miscellaneous X clients ii xfce4-terminal [x-te 0.2.6-2 Xfce terminal emulator ii xfonts-100dpi1:1.0.0-3 100 dpi fonts for X ii xfonts-75dpi 1:1.0.0-3 75 dpi fonts for X ii xfonts-base 1:1.0.0-4 standard fonts for X ii xfonts-scalable 1:1.0.0-6 scalable fonts for X ii xkb-data 0.9-4 X Keyboard Extension (XKB) configu ii xorg-docs1:1.2+git20061105-3 Miscellaneous documentation for th ii xserver-xorg 1:7.2-5 the X.Org X server ii xterm [x-terminal-em 225-1 X terminal emulator ii xutils 1:7.1.ds.3-1X Window System utility programs Versions of packages xorg recommends: ii libgl1-mesa-dri 6.5.2-5A free implementation of the OpenG -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#429569: xorg: Xorg consumes a lot of cpu at screensaver exit
Processing commands for [EMAIL PROTECTED]: severity 429569 important Bug#429569: xorg: Xorg consumes a lot of cpu at screensaver exit Severity set to `important' from `critical' reassign 429569 xserver-xorg-core Bug#429569: xorg: Xorg consumes a lot of cpu at screensaver exit Bug reassigned from package `xorg' to `xserver-xorg-core'. thank you Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#429569: xorg: Xorg consumes a lot of cpu at screensaver exit
Brice Goglin a écrit : severity 429569 important reassign 429569 xserver-xorg-core thank you Le Gluon du Net wrote: Severity: critical Justification: breaks the whole system Actually, this kind of problem is important or normal. In fact i don't know, when it happens I've generally to kill Xorg (If I could) or restart the computer, so? desktop, xorg consumes 50% or more of the cpu!!! I could move the mouse and the applications are not freeze, but I can't do anything other than ctr/alt/f1 or del Do you see an increased memory usage? Is the computer swapping or so? I put my password to return to my desktop and I could see Xorg 50% on my cpu applet but the computer isn't swapping. to kill the Xorg processus. If I would like to start an application or deploy a menu, I have to restart the computer. I'm using kde desktop and I'm using the random screensaver functionnality. I've xcreensaver installed. Could you try to locate whether the type of screensaver has an impact? For instance, does a plain black screensaver do the same? What about 3D/OpenGL? In first I used the random screensaver. Then I tried the blank screensaver only, but always the same problem. I'have a nvidia card. I could use nv ou nvidia driver, the result is the same. Please switch back to the nv driver and send the whole output of /usr/share/bug/xserver-xorg/script 31 (it should have been automatically included by the reportbug tool). Doing this right after the problem occured and before restarting a new X session would be the best (in case smething appears in Xorg.0.log). I switch back to NV since I have this problem. I'll launch this script next time I have this problem (tomorrow sure!!!). Thanks. Brice
Bug#429569: xorg: Xorg consumes a lot of cpu at screensaver exit
severity 429569 important reassign 429569 xserver-xorg-core thank you Le Gluon du Net wrote: Severity: critical Justification: breaks the whole system Actually, this kind of problem is important or normal. desktop, xorg consumes 50% or more of the cpu!!! I could move the mouse and the applications are not freeze, but I can't do anything other than ctr/alt/f1 or del Do you see an increased memory usage? Is the computer swapping or so? to kill the Xorg processus. If I would like to start an application or deploy a menu, I have to restart the computer. I'm using kde desktop and I'm using the random screensaver functionnality. I've xcreensaver installed. Could you try to locate whether the type of screensaver has an impact? For instance, does a plain black screensaver do the same? What about 3D/OpenGL? I'have a nvidia card. I could use nv ou nvidia driver, the result is the same. Please switch back to the nv driver and send the whole output of /usr/share/bug/xserver-xorg/script 31 (it should have been automatically included by the reportbug tool). Doing this right after the problem occured and before restarting a new X session would be the best (in case smething appears in Xorg.0.log). Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]