Kde freeze after approx an hour inaction

You mention Super Karamba is running. Do you also experience this problem if you don't use Super Karamba?
Can you keep a KSysGuard window, or console running "top", open and see what CPU and memory usage is like (and what apps are using it) when the system freezes?

Le Monday 03 March 2008 00:30:01 wolfger, vous avez écrit :
> You mention Super Karamba is running. Do you also experience this problem
> if you don't use Super Karamba? Can you keep a KSysGuard window, or console
> running "top", open and see what CPU and memory usage is like (and what
> apps are using it) when the system freezes?
>
> ** Changed in: ubuntu
> Status: New => Incomplete
>
> ** Tags added: verification-needed

What do you mean by this "Can you keep a KSysGuard window, or console
> running "top","

Go to your "System" menu, and launch "KSysGuard - Performance Monitor" and then keep that window visible so that you can see it when the system freezes. Alternately, (also from the "System" menu) run "Konsole" and type "top" at the prompt and hit return. Keep this window visible so you can see it when the system freezes. If you can it would be nice to do both, using KSysGuard to monitor total CPU/mem usage, and "top" to see which applications are using the most CPU.

Le Saturday 08 March 2008 11:07:38 wolfger, vous avez écrit :
> Go to your "System" menu, and launch "KSysGuard - Performance Monitor"
> and then keep that window visible so that you can see it when the system
> freezes. Alternately, (also from the "System" menu) run "Konsole" and
> type "top" at the prompt and hit return. Keep this window visible so you
> can see it when the system freezes. If you can it would be nice to do
> both, using KSysGuard to monitor total CPU/mem usage, and "top" to see
> which applications are using the most CPU.

I don't have ksysguard option in my system menu

I am confused how you are running KDE and do not have KSysGuard in your menu, but that is ok. You can also type "ksysguard" at a Konsole prompt to run the application.

Le Saturday 08 March 2008 12:15:02 wolfger, vous avez écrit :
> I am confused how you are running KDE and do not have KSysGuard in your
> menu, but that is ok. You can also type "ksysguard" at a Konsole prompt
> to run the application.

Thanks,
in fact, i've the option "surveillance du système" cause my kubuntu is in
french

Le Saturday 08 March 2008 12:15:02 wolfger, vous avez écrit :
> I am confused how you are running KDE and do not have KSysGuard in your
> menu, but that is ok. You can also type "ksysguard" at a Konsole prompt
> to run the application.

when it freeze, screensaver is running, i can login, but windows are not
correctly drawn and the mouse pointer is not responding weel.
Top process is xorg using among 90% cpu and 10% memory.
Information in sysguard and top windows are correctly updated even the windows
are not correctly drawn (screen saver colors and form replace bleu color,
title and boutons). no actions possible including switching from a virtual
desktop to another

Le Saturday 08 March 2008 12:15:02 wolfger, vous avez écrit :
> I am confused how you are running KDE and do not have KSysGuard in your
> menu, but that is ok. You can also type "ksysguard" at a Konsole prompt
> to run the application.

i forgot : xorg is using nvidia-glx-new driver

I'm confused what you mean by "freeze" if you are still able to log in. Normally when we say something freezes, it is not accepting any input.

If you disable your screen saver, does the problem persist?

Selon wolfger <email address hidden>:

> I'm confused what you mean by "freeze" if you are still able to log in.
> Normally when we say something freezes, it is not accepting any input.
>
> If you disable your screen saver, does the problem persist?
>
> --
> Kde freeze after approx an hour inaction
> https://bugs.launchpad.net/bugs/173682
> You received this bug notification because you are a direct subscriber
> of the bug.
>

yes

Looking back, it seems you never answered my initial question about if this happens without using Super Karamba. Sorry for so many questions, but I'm having trouble determining which package is the source of the problem.

Oh i'm sorry, this appens also without using superkaramba.
I believe it's an hard problem

many thanks for your persistence

OK, I'm going to have to go with the assumption that xorg is the problem here, since that is what's eating your CPU, and the problem doesn't seem to be based on any other applications being running. Now I need you to collect some detailed data:

Log out of your current session.

Press Control-Alt-F1 to enter a text terminal, and log in there,

Stop the display manager. If you are using Kubuntu, this should be done with
sudo invoke-rc.d kdm stop
If you started with an Ubuntu installation, you may still be runnning on gdm, so that would be
sudo invoke-rc.d gdm stop

enter the following commands:
sudo dpkg-reconfigure xserver-xorg
uname -a > uname.txt
lspci -vvnn > lspci.txt
sudo discover --disable=parallel,serial,usb,ide,scsi,pcmcia --format="%M\t%S\t%D\t%i\n" video > discover.txt

Attach to this bug report the files created above (uname.txt lspci.txt and discover.txt) as well as /var/log/Xorg.0.log and /etc/X11/xorg.conf

Le Saturday 22 March 2008 12:09:56 wolfger, vous avez écrit :
> OK, I'm going to have to go with the assumption that xorg is the problem
> here, since that is what's eating your CPU, and the problem doesn't seem
> to be based on any other applications being running. Now I need you to
> collect some detailed data:
>
> Log out of your current session.
>
> Press Control-Alt-F1 to enter a text terminal, and log in there,
>
> Stop the display manager. If you are using Kubuntu, this should be done
> with sudo invoke-rc.d kdm stop
> If you started with an Ubuntu installation, you may still be runnning on
> gdm, so that would be sudo invoke-rc.d gdm stop
>
> enter the following commands:
> sudo dpkg-reconfigure xserver-xorg
> uname -a > uname.txt
> lspci -vvnn > lspci.txt
> sudo discover --disable=parallel,serial,usb,ide,scsi,pcmcia
> --format="%M\t%S\t%D\t%i\n" video > discover.txt
>
> Attach to this bug report the files created above (uname.txt lspci.txt
> and discover.txt) as well as /var/log/Xorg.0.log and /etc/X11/xorg.conf
>
>
> ** Changed in: xorg (Ubuntu)
> Sourcepackagename: None => xorg

what do you mean the 2 last lines above ?

here are the files requested

Setting to incomplete since none of the data collected so far identifies what the error was. Perhaps a backtrace would help.

Ph Fdn: Please follow the instructions at https://wiki.ubuntu.com/Backtrace?highlight=%28backtrace%29 and provide a backtrace on this bug. Thank you.

Le Saturday 26 April 2008 08:53:22 wolfger, vous avez écrit :
> Ph Fdn: Please follow the instructions at
> https://wiki.ubuntu.com/Backtrace?highlight=%28backtrace%29 and provide
> a backtrace on this bug. Thank you.

Hello
I've updated to hardy 64, installed the compiz options and no more problem
appears using the kde window manager...

???

Le Saturday 26 April 2008 08:53:22 wolfger, vous avez écrit :
> Ph Fdn: Please follow the instructions at
> https://wiki.ubuntu.com/Backtrace?highlight=%28backtrace%29 and provide
> a backtrace on this bug. Thank you.

backtrace of which program ?
kde windows manager ? (if yes, which name do i use ?)

Backtrace of the X server; for more details please see http://wiki.ubuntu.com/X/Backtracing

Hello
 I've updated to hardy, installed the compiz options, running it with normal option.
I came back to no options and then no more problem...
 using the kde window manager...
???

Reported fixed.