Message-ID: <email address hidden>
Date: Thu, 15 Jul 2004 10:38:30 +0200
From: =?utf-8?Q?Mart=C4=B3n?= van de Streek <email address hidden>
To: Eric Dorland <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#259215: mozilla-firefox: firefox fails to start with 'Xlib: connection to ":0.0"
refused by server'
On Wed, 14 Jul 2004, Eric Dorland wrote:
> > martijn@hertz:~$ mozilla-firefox
> > selected locale: en-US
> > Xlib: connection to ":0.0" refused by server
> > Xlib: XDM authorization key matches an existing client!
> >
> > (firefox-bin:11812): Gtk-WARNING **: cannot open display:
> >
> >
> > I'm using experimental (now with the unstable mozilla-firefox, which
> > seems to be newer), XDM, and removing all of my "mozilla-ish"
> > directories (.mozilla, .firefox, .phoenix) doesn't seem to fix it.
>
> This really, really looks like something more fundamentally wrong with
> your X configuration. Is any other X application exhibiting strange
> behavior?
It has something to do with xdm. After switching to gdm, the problem is
gone.
Message-ID: <email address hidden> Q?Mart= C4=B3n? = van de Streek <email address hidden>
Date: Thu, 15 Jul 2004 10:38:30 +0200
From: =?utf-8?
To: Eric Dorland <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#259215: mozilla-firefox: firefox fails to start with 'Xlib: connection to ":0.0"
refused by server'
On Wed, 14 Jul 2004, Eric Dorland wrote:
> > martijn@hertz:~$ mozilla-firefox bin:11812) : Gtk-WARNING **: cannot open display:
> > selected locale: en-US
> > Xlib: connection to ":0.0" refused by server
> > Xlib: XDM authorization key matches an existing client!
> >
> > (firefox-
> >
> >
> > I'm using experimental (now with the unstable mozilla-firefox, which
> > seems to be newer), XDM, and removing all of my "mozilla-ish"
> > directories (.mozilla, .firefox, .phoenix) doesn't seem to fix it.
>
> This really, really looks like something more fundamentally wrong with
> your X configuration. Is any other X application exhibiting strange
> behavior?
It has something to do with xdm. After switching to gdm, the problem is
gone.
Martijn
--