On Wed, May 23, 2007 12:19 pm, M Harris wrote:

On Wednesday 23 May 2007 14:05, Kai Ponte wrote:

...

Yes - and before anyone else freaks out about how to get back (I did) CTRL+ALT+F7 gets you back.

:P But, when you got back... is X (KDE) unlocked?

No, it wasn't. In fact it was locked up tight. HOWEVER... ...I left it in the locked state for a few hours. Went off to a meeting, and it has been working perfectly. Could it have been "The Return of Beagle"? I'd forgotten about the dog, and I have it running. I currently have KDE System guard running to see if anything is stealing my processes, but so far, it has worked flawlessly for the past hour. I wonder if BeagleD or some other rogue process simply had taken over and now is finished doing whatever it was. Go figure! Anyway, back to our regular list full of exciting flame wars, boobie pics and beer threads.... ....oh wait. Wrong group. My bad! -- k -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Kenneth Aar, Grafikern.no wrote:

Kai Ponte wrote:

...

...I left it in the locked state for a few hours. Went off to a meeting, and it has been working perfectly. Could it have been "The Return of Beagle"? I'd forgotten about the dog, and I have it running.

Hi

I suspect beagle. I have yet to see this fantastic app do anything but consume fantastic amounts of CPU cycles. Firefox crashed alot when I had beagle and the accompanying firefoxplugin installed, but now it hasn't crashed since uninstalling.

I am currently looking for an app that really causes my cpu to burn. This is in order to work towards my goal of having a silent but stably running PC. Maybe I will simply install beagle, once again. Thanks for the helpful hint ;-)) Kind regards Eberhard -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Hi, On 5/23/07, Kai Ponte wrote:

No, it wasn't. In fact it was locked up tight.

HOWEVER...

...I left it in the locked state for a few hours. Went off to a meeting, and it has been working perfectly. Could it have been "The Return of Beagle"? I'd forgotten about the dog, and I have it running.

It's unlikely to be Beagle if your system is locking up hard. The multitasking nature of Linux means that even if one process is hogging all the CPU, the other processes still get to run. Is your hard drive thrashing while it's unresponsive? You could temporarily move /usr/bin/beagled out of the way (and run beagle-shutdown to stop a running daemon) and see if the hangs persist to see if it's Beagle. I'm interested in hearing if it is. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org