Re: X11 after crash loses title bar
Re: X11 after crash loses title bar
- Subject: Re: X11 after crash loses title bar
- From: Jeremy Huddleston <email@hidden>
- Date: Sun, 13 Apr 2008 18:52:59 -0700
Hi Mark,
This is fixed in the latest release candidates and will be in 2.2.0.
--Jeremy
On Apr 13, 2008, at 18:29, Mark Aufflick wrote:
To all who experienced this, if you had to force-quit X11 with frozen
windows perhaps it is the same issue I am experiencing in:
http://trac.macosforge.org/projects/xquartz/ticket/77
I have occasionally seen quartz-wm not running afterwards as has been
described here.
Cheers,
Mark.
On Fri, Apr 4, 2008 at 9:11 PM, Peter Collinson <email@hidden>
wrote:
On 4 Apr 2008, at 11:22, Jeremy Huddleston wrote:
On Apr 4, 2008, at 02:52, Peter Collinson wrote:
I've been having occasional 'freezes' where all X11 windows stop
responding.
The menu bar stop functioning. It's as if the Xserver has gone
away?
I've not really put my finger on what was causing it.
I just noticed that it happened when I resized an X11 window. (I am
running inside Spaces - which may be the problem, of course).
(I force quitted X11 and had the no window manager problem - no
menu
bars on X11 windows. I eventually had to reboot to get things to work
properly again, your mail about removing X11 state in /tmp arrived
as this
was happening.)
(Check my previous post for more details)
You don't need to reboot. You just need to rm /tmp/.X* ... this
is due to
a crash leaving junk there coupled with a bug in startx when tcp
connections
are disabled and xauth is enabled... You can get the fix by
waiting for
2.2.0_rc3 or doing:
curl -Lo startx
http://xquartz.macosforge.org/downloads/startx-fixed-postcrash-gui
sudo cp startx /usr/X11/bin
Anyway before I reset things, a quick ps ax didn't show anything
obvious
- 'Stopped' processes were one possible cause but this wasn't the
case.
You probably saw this:
/Applications/Utilities/X11.app/Contents/MacOS/X11 :0 -nolisten
tcp :1
-auth ...
xinit /usr/X11/lib/X11/xinit/xinitrc -- -nolisten tcp :1 -auth ...
which reveals the problem.
When I get a freeze, I can start Terminal - what should I do to
give
useful debugging information?
You may be having the lockup that was mentioned in coot (check my
other
previous post for more info).
Run Applications->Utilities->Activity Monitor.app
Double click on the process that is hung
Click 'Sample'
That should help narrow down the problem... we can use that to see
what
functions the server is stuck in... if it's like coot, both threads
seem to
be stuck in a deadlock waiting on semaphores...
OK - I'll wait for the next one and see if I can generate some
information.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
--
Mark Aufflick
contact info at http://mark.aufflick.com/about/contact
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden