I don't know whether anyone has found a workaround, but watch out for the most recent version of MozillaFirefox from SuSe - 0.9.1. It says that to get it working you must first fire it up as root. Alas, if I try to do that off the console, I get Xlib: connection to ":0.0" refused by server Xlib: XDM authorization key matches an existing client! (firefox-bin:8909): Gtk-WARNING **: cannot open display: whether I use su, sux or xhost +localhost. If I actually log in as root on KDE (not advised), I can start Firefox OK. But when I log out and back in again as an ordinary user, then I can't start Firefox as an ordinary user, since I now get the same message as root used to get above. I really really really really wish SuSE would test this stuff a bit more before putting it on their ftp servers, or post a readme explaining how to get round this little circular argument. :) Fish
On Wednesday 30 June 2004 07:19 pm, Mark Crean wrote:
I don't know whether anyone has found a workaround, but watch out for the most recent version of MozillaFirefox from SuSe - 0.9.1.
It says that to get it working you must first fire it up as root. Alas, if I try to do that off the console, I get
Xlib: connection to ":0.0" refused by server Xlib: XDM authorization key matches an existing client!
(firefox-bin:8909): Gtk-WARNING **: cannot open display:
whether I use su, sux or xhost +localhost.
If I actually log in as root on KDE (not advised), I can start Firefox OK. But when I log out and back in again as an ordinary user, then I can't start Firefox as an ordinary user, since I now get the same message as root used to get above.
I really really really really wish SuSE would test this stuff a bit more before putting it on their ftp servers, or post a readme explaining how to get round this little circular argument.
Umm -- how could SuSE have tested something that didn't exist? Anyway there is a workaround that I read about on this list (I think) for 9.0 that worked for me on 9.1: xhost + firefox xhost - From that point on firefox should start without a fuss. If not, there is another workaround I read about somewhere but don't remember where -- search the archives or try google. -- Robert C. Paulsen, Jr. robert@paulsenonline.net
I don't know whether anyone has found a workaround, but watch out for the most recent version of MozillaFirefox from SuSe - 0.9.1.
It says that to get it working you must first fire it up as root. Alas, if I try to do that off the console, I get
Xlib: connection to ":0.0" refused by server Xlib: XDM authorization key matches an existing client!
(firefox-bin:8909): Gtk-WARNING **: cannot open display:
whether I use su, sux or xhost +localhost.
If I actually log in as root on KDE (not advised), I can start Firefox OK. But when I log out and back in again as an ordinary user, then I can't start Firefox as an ordinary user, since I now get the same message as root used to get above.
I really really really really wish SuSE would test this stuff a bit more before putting it on their ftp servers, or post a readme explaining how to get round this little circular argument.
:)
Fish I think if you do the following from konsole... $> sux [enter pw] #> [path to]/firefox ...you'll find it loads. The error you are getting indicates it cannot connect to the x-server, and 'sux' gets you connected. HTH... -- ...CH "The more they over-think the plumbing,
On Wednesday 30 June 2004 19:19, Mark Crean wrote: the easier it is to stop up the drain." Scotty
On Wednesday 30 June 2004 08:19 pm, Mark Crean wrote:
I don't know whether anyone has found a workaround, but watch out for the most recent version of MozillaFirefox from SuSe - 0.9.1.
It says that to get it working you must first fire it up as root. Alas, if I try to do that off the console, I get [...] If I actually log in as root on KDE (not advised), I can start Firefox OK. But when I log out and back in again as an ordinary user, then I can't start Firefox as an ordinary user, since I now get the same message as root used to get above.
I really really really really wish SuSE would test this stuff a bit more before putting it on their ftp servers, or post a readme explaining how to get round this little circular argument.
:)
Fish =========
Mark, This is not a SuSE problem and it's been discussed here already. There is a bug in the 0.9.x Firefox that causes this problem. Not easily fixed and certainly not by SuSE. You can check the archives for answers to this perplexing anomaly or you can do this! ;o) Open a shell as user and issue this command: xhost +local: then run firefox from shell it should open and once it does, close it down do: xhost -local: (to close this down) Now you should be able to run firefox from the shell or icon. Lee -- --- KMail v1.6.2 --- SuSE Linux Pro v9.1 --- Registered Linux User #225206 On any other day, that might seem strange...
On Thu, 2004-07-01 at 02:30, BandiPat wrote: [snip]
Now you should be able to run firefox from the shell or icon.
Thanks very much. Will reinstall later. I hope the bug is eventually fixed or that SuSE decide to post more about it in the readme on their ftp site. :) Fish
* Mark Crean
Thanks very much. Will reinstall later. I hope the bug is eventually fixed or that SuSE decide to post more about it in the readme on their ftp site.
$ pwd ftp.suse.com/pub/projects/mozilla/firefox $ cat README-0.9.x Because of missing registration features in firefox 0.9.x you have to start firefox as root the first time after installation. SuSE already did :) -- Mads Martin Joergensen, http://mmj.dk "Why make things difficult, when it is possible to make them cryptic and totally illogical, with just a little bit more effort?" -- A. P. J.
* Mads Martin Joergensen
$ pwd ftp.suse.com/pub/projects/mozilla/firefox $ cat README-0.9.x
Because of missing registration features in firefox 0.9.x you have to start firefox as root the first time after installation.
SuSE already did :)
BTW; instead of messing with xhost, simply use 'sux'. -- Mads Martin Joergensen, http://mmj.dk "Why make things difficult, when it is possible to make them cryptic and totally illogical, with just a little bit more effort?" -- A. P. J.
On Thursday 01 July 2004 09.56, Mads Martin Joergensen wrote:
* Mads Martin Joergensen
[Jul 01. 2004 09:53]: $ pwd ftp.suse.com/pub/projects/mozilla/firefox $ cat README-0.9.x
Because of missing registration features in firefox 0.9.x you have to start firefox as root the first time after installation.
SuSE already did :)
BTW; instead of messing with xhost, simply use 'sux'.
Doesn't work. The problem is that due to some bug, probably in gtk, two X connections are established at the same time with the same PID, so X complains about it. It isn't lack of authorisation, it's that X refuses to allow two connections with the same cookie. The only way around it, aside from fixing the bug :), is to completely turn off auth checking This problem still exists in the suse version, if you run it for the first time. The problem is when firefox tries to open the "import settings" window. If you already have the config files from a previous installation you don't see it
* Anders Johansson
$ pwd ftp.suse.com/pub/projects/mozilla/firefox $ cat README-0.9.x
Because of missing registration features in firefox 0.9.x you have to start firefox as root the first time after installation.
SuSE already did :)
BTW; instead of messing with xhost, simply use 'sux'.
Doesn't work. The problem is that due to some bug, probably in gtk, two X connections are established at the same time with the same PID, so X complains about it. It isn't lack of authorisation, it's that X refuses to allow two connections with the same cookie. The only way around it, aside from fixing the bug :), is to completely turn off auth checking
This problem still exists in the suse version, if you run it for the first time. The problem is when firefox tries to open the "import settings" window. If you already have the config files from a previous installation you don't see it
Oh, odd. I just installed 0.9.1 yesterday using nothing but 'sudo sux -'. -- Mads Martin Joergensen, http://mmj.dk "Why make things difficult, when it is possible to make them cryptic and totally illogical, with just a little bit more effort?" -- A. P. J.
On Thursday 01 July 2004 10.05, Mads Martin Joergensen wrote:
This problem still exists in the suse version, if you run it for the first time. The problem is when firefox tries to open the "import settings" window. If you already have the config files from a previous installation you don't see it
Oh, odd. I just installed 0.9.1 yesterday using nothing but 'sudo sux -'.
This isn't about having to run it as root, this is when you run it for the first time as a user. Did you already have an old installation? I installed 0.9 on a system where I already had 0.8 and everything worked perfectly. Then I cleared out everything, $HOME/.mozilla, $HOME/.firefox and all, and tried again, and then I got the error everyone else is seeing It seems to be very timing sensitive. I said the only way around it is to turn of authentication, but that's not true. When I experimented, I found that the error also went away when I changed the hash-bang in run-mozilla.sh from /bin/sh to /bin/sh -x. That slight change in timing was enough.
* Anders Johansson
This problem still exists in the suse version, if you run it for the first time. The problem is when firefox tries to open the "import settings" window. If you already have the config files from a previous installation you don't see it
Oh, odd. I just installed 0.9.1 yesterday using nothing but 'sudo sux -'.
This isn't about having to run it as root, this is when you run it for the first time as a user. Did you already have an old installation?
I installed 0.9 on a system where I already had 0.8 and everything worked perfectly. Then I cleared out everything, $HOME/.mozilla, $HOME/.firefox and all, and tried again, and then I got the error everyone else is seeing
It seems to be very timing sensitive. I said the only way around it is to turn of authentication, but that's not true. When I experimented, I found that the error also went away when I changed the hash-bang in run-mozilla.sh from /bin/sh to /bin/sh -x. That slight change in timing was enough.
Yeah, it makes sense, and yes, I did have 0.8 before. -- Mads Martin Joergensen, http://mmj.dk "Why make things difficult, when it is possible to make them cryptic and totally illogical, with just a little bit more effort?" -- A. P. J.
In you terminal try typing in "xhost + hostnaem:0" This should allow a user to attach to your X11 Sesion. On Wed, 2004-06-30 at 17:19, Mark Crean wrote:
I don't know whether anyone has found a workaround, but watch out for the most recent version of MozillaFirefox from SuSe - 0.9.1.
It says that to get it working you must first fire it up as root. Alas, if I try to do that off the console, I get
Xlib: connection to ":0.0" refused by server Xlib: XDM authorization key matches an existing client!
(firefox-bin:8909): Gtk-WARNING **: cannot open display:
whether I use su, sux or xhost +localhost.
If I actually log in as root on KDE (not advised), I can start Firefox OK. But when I log out and back in again as an ordinary user, then I can't start Firefox as an ordinary user, since I now get the same message as root used to get above.
I really really really really wish SuSE would test this stuff a bit more before putting it on their ftp servers, or post a readme explaining how to get round this little circular argument.
:)
Fish
-- Joseph Loo jloo@acm.org
On Thursday 01 July 2004 01:19, Mark Crean wrote:
I don't know whether anyone has found a workaround, but watch out for the most recent version of MozillaFirefox from SuSe - 0.9.1.
It says that to get it working you must first fire it up as root. Alas, if I try to do that off the console, I get
Xlib: connection to ":0.0" refused by server Xlib: XDM authorization key matches an existing client!
(firefox-bin:8909): Gtk-WARNING **: cannot open display:
whether I use su, sux or xhost +localhost.
If I actually log in as root on KDE (not advised), I can start Firefox OK. But when I log out and back in again as an ordinary user, then I can't start Firefox as an ordinary user, since I now get the same message as root used to get above.
I really really really really wish SuSE would test this stuff a bit more before putting it on their ftp servers, or post a readme explaining how to get round this little circular argument.
:)
OK, well go to: http://www.mozilla.org/products/firefox/ and download the default Linux file, which is: firefox-0.9.1-i686-linux-gtk2+xft.tar.gz su cp firefox-0.9.1-i686-linux-gtk2+xft.tar.gz /usr/local/ cd /usr/local tar zxf firefox-0.9.1-i686-linux-gtk2+xft.tar.gz cd bin ln -s /usr/local/firefox/firefox firefox Right-click your desktop and create a new link to application. You can get an icon by browsing to /usr/local/firefox/icons. Name it and give /usr/local/ firefox/firefox as the path to the executable. You're good to go, and you haven't had to access the x-server as root. And everything is nicely anti-aliased, etc. If you didn't care about whether other users could access it, you could just untar the whole thing in your $HOME and link to it there. HTH Fergus
Fish
-- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB Tel: +44 161 834 7961 Fax: +44 161 839 5797 http://www.chethams.org.uk
On Thu, Jul 01, 2004 at 08:50:17AM +0100, Fergus Wilde wrote:
If you didn't care about whether other users could access it, you could just untar the whole thing in your $HOME and link to it there.
Right... This is almost what I did. I just put it into every $HOME directory (only 4 of the suckers). Anyway, I had another problem with Firefox locking up as soon as someone typed on the keyboard. Only root was unaffected. As soon as I put the whole shooting match into the $HOME all my problems went away.
Xaos Katawin wrote:
On Thu, Jul 01, 2004 at 08:50:17AM +0100, Fergus Wilde wrote:
If you didn't care about whether other users could access it, you could just untar the whole thing in your $HOME and link to it there.
Right...
This is almost what I did. I just put it into every $HOME directory (only 4 of the suckers). Anyway, I had another problem with Firefox locking up as soon as someone typed on the keyboard. Only root was unaffected. As soon as I put the whole shooting match into the $HOME all my problems went away.
If you put it into say, /usr/local and "ln -s /usr/local/firefox/firefox /usr/local/bin/", when a user fires it up, it creates a .firefox directory in the user's home directory if one does not already exist, each user can then choose which plugins, extensions, themes etc. she wants. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer ===== LINUX ONLY USED HERE =====
On Thu, Jul 01, 2004 at 08:50:17AM +0100, Fergus Wilde wrote:
If you didn't care about whether other users could access it, you could just untar the whole thing in your $HOME and link to it there.
Right...
This is almost what I did. I just put it into every $HOME directory (only 4 of the suckers). Anyway, I had another problem with Firefox locking up as soon as someone typed on the keyboard. Only root was unaffected. As soon as I put the whole shooting match into the $HOME all my problems went away. Now that you meniton it... I had the lockup prob, too, w/the version on SuSE's CD. As soon as I d/l it from Mozilla & installed, that prob went away. Go
On Monday 05 July 2004 04:00, Xaos Katawin wrote: figure. -- ...CH "The more they over-think the plumbing, the easier it is to stop up the drain." Scotty
participants (10)
-
Anders Johansson
-
BandiPat
-
C Hamel
-
Fergus Wilde
-
Joseph Loo
-
Mads Martin Joergensen
-
Mark Crean
-
Robert Paulsen
-
Sid Boyce
-
Xaos Katawin