| Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
** smacks himself in the head **
THANK YOU.
Yeah, that's it. I was test driving Bitkeeper and it had complained that
my usually irrelevant hostname ('laptop') wasn't legal, so I changed it.
Changed it back and sure enough xhost goes back to working.
Duane
On Thu, 16 Oct 2003 gboyce at badbelly.com wrote:
> I've seen this error occur in the past when the hostname of the system
> gets changed. Did you happen to manually change your hostname? Or
> perhaps you're getting a hostname from the dhcp server, and your lease
> expired?
>
> On Thu, 16 Oct 2003, Duane Morin wrote:
>
> > I'll be running just fine for hours on my Redhat 9 laptop, opening windows
> > at will. Then all of a sudden I'll try to do something that requires
> > a window opening and get
> >
> > Xlib: connection to ":0.0" refused by server
> > Xlib: No protocol specified
> >
> > Application initialization failed: couldn't connect to display ":0.0"
> >
> >
> > I've done nothing different, and this error is thrown by the exact same
> > shell that 5 minutes ago let me open a window just fine.
> >
> > What could be going on behind the scenes that's causing this? I should
> > mention that when I say "opening windows at will" I don't mean hundreds, I
> > mean a handful - maybe a dozen, tops. And, right now, there's maybe 5
> > open.
> >
> > Duane
> >
> >
> > _______________________________________________
> > Discuss mailing list
> > Discuss at blu.org
> > http://www.blu.org/mailman/listinfo/discuss
> >
>