UC C-6, Gnome Question

Home » CentOS » UC C-6, Gnome Question
CentOS 5 Comments

Another Firefox “funny” to be aware of occurs if you have a $HOME shared between multiple machines. Firefox will refuse to start on the second machine whilst the first is running Firefox, it believes that there is already an instance running. Rebooting the second machine will not help. The quick-and-dirty way around this is to log in as a different user (and hence different $HOME) on the second machine.

This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. QinetiQ may monitor email traffic data and also the content of email for the purposes of security. QinetiQ Limited (Registered in England
& Wales: Company Number: 3796233) Registered office: Cody Technology Park, Ively Road, Farnborough, Hampshire, GU14 0LX http://www.qinetiq.com.

5 thoughts on - UC C-6, Gnome Question

  • That sort of stuff gets my back up, wondering who the hell is making these design changes. Not folks that are aware of how stuff is used in the “real world? Not folks who understand the concept of “regression testing”? Not folks who look outside their walls and solicit comment from their victims? I don’t know, but I get obnoxiously resistant (often to my own detriment) in such cases and tend to do things like my patch.

    Yep, long-term potential negatives, but sometimes it’s worth it to me. E.g., a very long time ago, device drivers for network cards did not work well for a particular card I was using. So I grabbed the code and
    “Holy Crap”. What a piss-poor bunch of code. And it didn’t handle the hardware properly either. So I got the technical docs for the card, modified the driver, tested every edge condition I could think of and, when satisfied, made a patch and got it ready for contribution.

    Well, they changed maintainers while I was doing all that and the new code set was so far off what I was working with that my patch became useless.

    So I just used my driver for myself, making my effort worthwhile, but I
    wouldn’t have been so stringent in the testing and commentary in the code if I had known what was happening. So it cost me some extra time and effort.

    MHO, Bill

  • I’ve been using a network filesystem for $HOME for decades, and Firefox (and Netscape Navigator before it) has always been this way. Not a design change. What would be nice is if Firefox used the
    /run/user/$UID/ directory for per-instance files instead of a directory in $HOME. Y’know, like Gnome 3 does. :)

  • You will see the same effect on MicroSoft Domains with users using roaming profiles. They leave one host with FF open and go to another, log on and try, vainly, to start FF in the new session. I presume this has to do with preventing destructive overwrites of the user’s profile but it is annoying. Not a Linux problem though.

  • James B. Byrne wrote:

    This firefox invocation inhibits the surprising behavior:

    firefox -new-instance -no-remote

    BTW, thanks for the up-thread patch!

    Best regards,