RE: that X/Gnome lockup thing. How to trace it?

[Daniel Weber <dweber1 austin rr com>]

Same thing happened to me when I upgraded to the new Sawfish WM.  I believe it
happened because of the re-naming from Sawmill to Sawfish.  It was the window
manager locking up, not X.  I had remote access and killed Sawmill and then
restarted Sawfish and all was well.

 On Sun, 09 Jul 2000,
Rob Brown-Bayliss wrote: > I had this problem the other day.
> 
> I run Helix gnome and installed the sawfish update via the helix updater.
> 
> 
> When it updated my X froze and the pc speaker was beeping 300bpm.
> 
> I could not move mouse at all, but I could tell from a couple of applets
> that the machine was infact still running (cpu, mem meters and clock still
> working, email counter updated with new mail and net trafic meter showing a
> down load.)
> 
> Unfortunatly I could not use the keyboard to activate a term and kill X so I
> had to pull the plug...  
> 
> Could there be something usefull in this that relates to the general lockups
> you are having?  What does the sawfish rpm do in it's scripts for example? 
> 
> _______________________________________________
> gnome-list mailing list
> gnome-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/gnome-list