On Tuesday 15 June 2004 21:52, Patrick Shanahan wrote:

* Anders Johansson [06-15-04 21:50]:

...

On Wednesday 16 June 2004 04.46, Bryce Hardy wrote:

...

I downloaded the new Mozilla Firefox browser today, unpacked it into /usr/local, and when I tried to start it, I got this error message:

Xlib: connection to ":0.0" refused by server Xlib: XDM authorization key matches an existing client!

I swear.......

Try running it as your regular user, not as root

At this rate, we are no safer than <shudder> windoz!

Ack! You're gonna make me have friggin' nightmares talking like that! John

On Wednesday 16 June 2004 04.55, Bryce Hardy wrote:

On Tuesday 15 June 2004 07:50 pm, Anders Johansson wrote:

...

...

I downloaded the new Mozilla Firefox browser today, unpacked it into /usr/local, and when I tried to start it, I got this error message:

Xlib: connection to ":0.0" refused by server Xlib: XDM authorization key matches an existing client!

I swear.......

Try running it as your regular user, not as root

I'm not running it as root, here see for yourself, with the regular user prompt:

cygnia@cygniapolis:/usr/local/firefox> ./firefox Xlib: connection to ":0.0" refused by server Xlib: XDM authorization key matches an existing client!

(firefox-bin:13340): Gtk-WARNING **: cannot open display:

My apologies, too many people ask about the "connection refused" thing, my answer was a reflex action. Your error is different than normal though, I haven't seen that one before. googling around, it looks like some sort of race condition, and all the posts I can find on the net are about gtk I can't reproduce it here though, firefox works well for me

Anders Johansson wrote:

On Wednesday 16 June 2004 04.55, Bryce Hardy wrote:

...

On Tuesday 15 June 2004 07:50 pm, Anders Johansson wrote:

...

...

I downloaded the new Mozilla Firefox browser today, unpacked it into /usr/local, and when I tried to start it, I got this error message:

Xlib: connection to ":0.0" refused by server Xlib: XDM authorization key matches an existing client!

I swear.......

Try running it as your regular user, not as root

I'm not running it as root, here see for yourself, with the regular user prompt:

cygnia@cygniapolis:/usr/local/firefox> ./firefox Xlib: connection to ":0.0" refused by server Xlib: XDM authorization key matches an existing client!

(firefox-bin:13340): Gtk-WARNING **: cannot open display:

My apologies, too many people ask about the "connection refused" thing, my answer was a reflex action. Your error is different than normal though, I haven't seen that one before.

googling around, it looks like some sort of race condition, and all the posts I can find on the net are about gtk

I can't reproduce it here though, firefox works well for me

I'm getting the same error.

brooks@7:~> firefox/firefox Xlib: connection to ":0.0" refused by server Xlib: XDM authorization key matches an existing client!

(firefox-bin:18192): Gtk-WARNING **: cannot open display:

Jack

On Tuesday 15 June 2004 08:43 pm, Jim Sabatke wrote:

Are you ssh'ing into the box from another machine?  Or have you su'd to another user in the process?

If so, then there may be easy answers.

No on both counts. This is a stand-alone box with no other users even on it except mine and root. As an aside, I just downloaded the newest release candidate of thunderbird 0.7 and it resulted in the same error message. -- Bryce Hardy (Santa Rosa, CA USA) cygnia@sonic.net

On Tuesday 15 June 2004 11:43 pm, Bryce Hardy wrote:

On Tuesday 15 June 2004 08:43 pm, Jim Sabatke wrote:

...

Are you ssh'ing into the box from another machine?  Or have you su'd to another user in the process?

If so, then there may be easy answers.

No on both counts. This is a stand-alone box with no other users even on it except mine and root.

As an aside, I just downloaded the newest release candidate of thunderbird 0.7 and it resulted in the same error message.

-- Bryce Hardy (Santa Rosa, CA USA) cygnia@sonic.net ==========

I'm curious Bryce and maybe some others can offer input as well. I believe you mentioned that you installed this in /usr/local. Did you other guys do the same or did you install it in your $HOME directory? It certainly sounds like a bug in Firefox, but just curious about the installation. I've always installed it & TBird into my /home directory and ran it from there, since I'm only running a single user system and it's worked great each time. Of course, I am using SuSE's installation from 9.1 now and wanted to wait on the final release of 0.9 before installing or trying it. I suspect that SuSE will have an rpm for that version as well, so may wait. Just curious, Lee -- --- KMail v1.6.2 --- SuSE Linux Pro v9.1 --- Registered Linux User #225206 On any other day, that might seem strange...

On Tuesday 15 June 2004 22:55, Bryce Hardy wrote:

I'm not running it as root, here see for yourself, with the regular user prompt:

He's right folks - we had a user here experience precisely the same problem(although I didn't - same hardware/software!). Anyway, we fixed the problem: % xhost + % firefox ...then quit firefox % xhost - this disables X authentication temporarily to let firefox come up, then when you quit it seems to have fixed itself. The final command re-establishes authentication, but firefox will load properly after that. We couldn't figure out why this happened. Cheers, J.C. -- John Coldrick www.axyzfx.com Axyz Animation Houdini/Renderman/Discreet 425 Adelaide St W 416-504-0425 Toronto, ON Canada jc@axyzfx.com M5V 1S4 ----------------------------------------------------------------------- Millions long for immortality who do not know what to do with themselves on a rainy Sunday afternoon. -- Susan Ertz

On Wednesday 16 June 2004 11:43, Patrick Shanahan wrote:

* John Coldrick [06-16-04 10:22]:

...

Anyway, we fixed the problem:

% xhost + % firefox

...then quit firefox

% xhost -

this disables X authentication temporarily to let firefox come up,

Instead of baring your backside, why wouldn't you use 'sux' or 'sudo' to allow root access to X?

We're talking all of 30 seconds, behind a firewall, and this was the only way we found to fix it. In case it's not clear - this needed to be done *once*. Are you seriously suggesting that opening up xauth for less than a minute at a random point in time is some sort of security nightmare? I think everytime I turn on Windows at home I'm open to a higher security risk. J.C. -- John Coldrick www.axyzfx.com Axyz Animation Houdini/Renderman/Discreet 425 Adelaide St W 416-504-0425 Toronto, ON Canada jc@axyzfx.com M5V 1S4 ----------------------------------------------------------------------- Millions long for immortality who do not know what to do with themselves on a rainy Sunday afternoon. -- Susan Ertz

Mark McKibben wrote:

On Tuesday 15 June 2004 09:46 pm, Bryce Hardy wrote:

...

I downloaded the new Mozilla Firefox browser today, unpacked it into /usr/local, and when I tried to start it, I got this error message:

Xlib: connection to ":0.0" refused by server Xlib: XDM authorization key matches an existing client!

(firefox-bin:13199): Gtk-WARNING **: cannot open display:

I'm running SuSE 9.0 Pro (KDE 3.2.2) and was getting the same error. After a bit of mucking around, I got Firefox 0.9 to work for me. What I did was: 1. Delete my old 0.8 directory 2. Delete the new 0.9 directory 3. Delete the old firefox's settings directory (e.g. /home/username/.phoenix/) 4. Delete the new firefox's settings directory (e.g. /home/username/.mozilla/firefox/) 5. Run firefox once as root.

Just downloaded the new version and installed it. Works great (SuSE 9.0). In fact, they even fixed the font problem. The only reason I wasn't using FireFox 0.8 was because the fonts were horrible. FireFox 0.9 may now be my browser of choice. Russ

After that, I was able to run the new version of firefox w/out that nasty error. Hope that helps!

On Wednesday 16 June 2004 12:17 am, Bryce Hardy wrote:

...

2. Delete the new 0.9 directory

Unclear on that one; you mean you unpack the tar.gz file again? How can you run it if you delete it?

I'd unpacked it once, deleted that new directory and then later unpacked it again, once I 'd finished getting rid of the old version completely

It won't work. The same basic error message pops up.

Hmm, maybe the permissions on the directory firefox are messed up? I might have played around with those as well, but I can't recall as I got mine up & running before I saw your email on the list here. If it had been the other way round; I would have kept notes. -- Mark McKibben http://www.vision-at-work.org/~manzabar/ "We are bits of stellar matter that got cold by accident, bits of a star gone wrong." - Sir Arthur Eddington

On Wednesday 16 June 2004 07:11 am, Brad Bourn wrote:

I got the same message, so I typed [xhost +] to turn off access control run firefox then [xhost -] to turn access control back on.

OK, I broke down and followed this advice and now firefox seems to be running. Just using sux didn't have any effect. So for the record that's how we need to get it to work. Thanks for everyone who responded and those who had the same problem. -- Bryce Hardy (Santa Rosa, CA USA) cygnia@sonic.net