Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

After recent update, firefox 60 won't start

  • 3 antwurd
  • 1 hat dit probleem
  • 7 werjeftes
  • Lêste antwurd fan JonaSF

more options

Hi all,

Firefox has been updating itself successfully over the past year, but today when I followed the most recent update (I think I had version 60.8 prior to the update), it didn't restart. When I tried running it using the command line, I got the error message:

firefox: symbol lookup error: libxul.so: undefined symbol: dbus_validate_bus_name

For now, I reverted back to an old version (55).

Any tips on how to resolve this problem?

I'm using firefox on linux 32bit with Fedora 17

Thanks!

Hi all, Firefox has been updating itself successfully over the past year, but today when I followed the most recent update (I think I had version 60.8 prior to the update), it didn't restart. When I tried running it using the command line, I got the error message: firefox: symbol lookup error: libxul.so: undefined symbol: dbus_validate_bus_name For now, I reverted back to an old version (55). Any tips on how to resolve this problem? I'm using firefox on linux 32bit with Fedora 17 Thanks!

Keazen oplossing

Hi, can you use a Linux file from here to put 60.0.1 back in ? :

Also see if you can find a newer fontconfig package as that was the error from 43 and that fixed the issue.

Please let us know if this solved your issue or if need further assistance.

Dit antwurd yn kontekst lêze 👍 1

Alle antwurden (3)

more options

Keazen oplossing

Hi, can you use a Linux file from here to put 60.0.1 back in ? :

Also see if you can find a newer fontconfig package as that was the error from 43 and that fixed the issue.

Please let us know if this solved your issue or if need further assistance.

more options
more options

Pkshadow, Thank you so much! I installed version 60.0.1, per the link you provided, and it has been quite stable for the past couple of days.

I do have the most recent version of fontconfig

Thanks again!