This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Etsi tuesta

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Lue lisää

I use Firefox in Ubuntu (actually, Zorin). FF doesn't start correctly intermittently (greyed out; can't get URLs). But it works if I log out & back in. Ideas?

  • 4 vastausta
  • 1 henkilöllä on sama ongelma
  • 1 näyttö
  • Viimeisin kirjoittaja joeTheUser

more options

The clue is that it works without a hitch when this flares up by simply logging out then back in.

I'm new to Ubuntu. I'm actually using the Zorin fork of Ubuntu, which uses a Gnome rather than Unity interface. But for all practical purposes, it's Ubuntu I'm Firefoxing with as an Ubuntu newbie.

The clue is that it works without a hitch when this flares up by simply logging out then back in. I'm new to Ubuntu. I'm actually using the Zorin fork of Ubuntu, which uses a Gnome rather than Unity interface. But for all practical purposes, it's Ubuntu I'm Firefoxing with as an Ubuntu newbie.

Valittu ratkaisu

YUPT!

about:config > browser.tabs.remote.autostart = false

reconciled these inconsistencies, so all's well in paradise. =)

Lue tämä vastaus kontekstissaan 👍 0

Kaikki vastaukset (4)

more options

Be aware that Ubuntu builds its own version of Firefox from source code, so there are some differences between their version and the Linux version that Mozilla builds and distributes. http://ubuntuforums.org/


Just a SWAG: See if disabling Use hardware acceleration when available helps with that fault. https://support.mozilla.org/en-US/kb/performance-settings?as=u&utm_source=inproduct

more options

Thank you kindly for the response. I use the Linux version. I tried those preference tweaks, including the the proxy, IPv6 & disablePrefetch as described in https://support.mozilla.org/en-US/kb/firefox-cant-load-websites-other-browsers-can to no avail. BTW, when it flares up, even about:config & preferences are grey-out/inaccessible.

THE GOOD NEWS: upon closer examination, I was able to get this error info to relay:

Failed to connect to Mir: Failed to connect to server socket: No such file or directory Unable to init server: Could not connect: Connection refused

(/usr/lib/firefox/firefox:22345): Gtk-WARNING **: cannot open display: :1 [Parent 22275, Gecko_IOThread] WARNING: pipe error: Broken pipe: file /build/firefox-CIsUqV/firefox-60.0.2+build1/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 709 [Parent 22275, Gecko_IOThread] WARNING: FileDescriptorSet destroyed with unconsumed descriptors: file /build/firefox-CIsUqV/firefox-60.0.2+build1/ipc/chromium/src/chrome/common/file_descriptor_set_posix.cc, line 22

I got that by entering

firefox -P

at the command prompt, then "start Firefox".

It then complained at me things like:

[Parent 22732, Gecko_IOThread] WARNING: pipe error (105): Connection reset by peer: file /build/firefox-CIsUqV/firefox-60.0.2+build1/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353

Then that

!!! [Parent][MessageChannel] Error: (msgtype=0x15007F,name=PBrowser::Msg_Destroy) Channel error: cannot send/recv

Muokattu , muokkaaja joeTheUser

more options

I'm not sure, but I'm hoping that https://github.com/SeleniumHQ/docker-selenium/issues/388 has a working fix:

workaround is to disable remote autostart: in: about:config set (historical mode):

browser.tabs.remote.autostart = false <--------------------------- <--------- (also browser.tabs.remote.autostart.2 = false if applicable)

So far, so good. I don't understand why it works, but would like to know. I know it's common enough of a problem, somebody someday may see this and benefit from it.

If it flares up again, I'll come crying back here and strike that.

Happy Fourth!

more options

Valittu ratkaisu

YUPT!

about:config > browser.tabs.remote.autostart = false

reconciled these inconsistencies, so all's well in paradise. =)