Re: iBook + sleep = Can't open display: :0.0
Re: iBook + sleep = Can't open display: :0.0
- Subject: Re: iBook + sleep = Can't open display: :0.0
- From: Kurt P Lloyd <email@hidden>
- Date: Sat, 19 Apr 2003 12:31:35 -0400
- Organization: Lucent Technologies
While I did not always unplug the iBook from the
ethernet cable, I think that closing the iBook lid
must do something to affect this. I now notice
that sometimes reopening the iBook lid results in
not being able to create new X11 windows, whereas
sometimes I *can* create new X11 windows. And it
may have something to do with how long the iBook
lid is closed. The longer it is closed (say, a
couple minutes verses a couple seconds) the more
likely to have this problem. Also, I was able to
reproduce the same problem with quartz-wm.
I have unchecked both boxes in X11 Preferences->
Security, and I no longer seem to have this problem.
Thank you, Haroon!
By the way, it's OK with me if these Security
settings prevent me from, say, rlogin to some
machine, export DISPLAY=<iBook>:0, run X11 app.
The reason it's OK with me is that I find it
better to use VNC instead (the X11-based one,
installable via Fink).
-Kurt Lloyd
Haroon Sheikh wrote:
>
> Are you changing networking connections during the sleep? If so this may be related to Xauth.
>
> From the FAQ:
> Q: Why can I not connect to the X Server after a network config change? It requires a restart of the X server.
>
> A: This is expected behavior in the Xauthority authentication mechanism which X11 for Mac OS X uses by default. The problem is that Xauth uses two keys, the ip address and hostname of the system running the X server. But these keys don't get updated if you change the network configuration. You can disable authentication from the "Security" tab of X11.app 's preferences. Be aware that doing so may create a security hole.
>
> On Wednesday, April 16, 2003, at 6:16 PM, Kurt P Lloyd wrote:
>
> I noticed the following email in the archives, as I
> was looking for someone who, like me, was having this
> problem. I am using Beta 3 on 10.2.5, and I notice
> this problem occurs when running twm or sawfish, but
> not quartz-wm.
> Anyone know if this problem is understood?
> -Kurt Lloyd, email@hidden
>
> On Thursday, January 16, 2003, at 07:16 Uhr, Mark Byram wrote:
>
> Greetings,
>
> Has anybody noticed that putting an iBook to sleep with X11 running,
> then waking it up causes all subsequent attempts to load X11 apps to
> return:
>
> Xlib: connection to ":0.0" refused by server
> Xlib: No protocol specified
>
> xterm Xt error: Can't open display: :0.0
>
> ...until X11 is restarted? (OS 10.2.3, X11 0.1/4.2.1)
>
> Thanks,
> -mark
_______________________________________________
x11-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/x11-users
X11 for Mac OS X FAQ: http://developer.apple.com/qa/qa2001/qa1232.html
Report issues, request features, feedback: http://developer.apple.com/bugreporter
Do not post admin requests to the list. They will be ignored.