Join the Mozilla’s Test Days event from Dec 2–8 to test the new Firefox address bar on Firefox Beta 134 and get a chance to win Mozilla swag vouchers! 🎁

Avatar for Username

Vyhľadajte odpoveď

Vyhnite sa podvodom s podporou. Nikdy vás nebudeme žiadať, aby ste zavolali alebo poslali SMS na telefónne číslo alebo zdieľali osobné informácie. Nahláste prosím podozrivú aktivitu použitím voľby “Nahlásiť zneužitie”.

Ďalšie informácie

Táto téma bola archivovaná. Ak potrebujete pomôcť, založte prosím novú otázku.

default profile only works when run with --profile

  • 3 odpovede
  • 1 má tento problém
  • 4 zobrazenia
  • Posledná odpoveď od cor-el

titaniumbones
titaniumbones
more options

After a crash, I'm having a strange problem where firefox (nightly 69.0a1+20190604+hdfc513e7e141 , Arch Linux AUR package, under GNOME Wayland) only actually loads/renders web pages if run with the command-line switch

`--profile ~/.mozila/firefox/xxxxxxxx`

where `xxxxxxxx` is the path to the default profile. If I omit the command-line switch, firefox seems to run fine except that no connections are ever successfully made and all pages remain blanck.

I imagine there is a corrupted file somewhere but i don't understand why the default profile would work fine when it is explicitly invoked with the `--profile` switch, but not otherwise.

Thank yo uas always!

After a crash, I'm having a strange problem where firefox (nightly 69.0a1+20190604+hdfc513e7e141 , Arch Linux AUR package, under GNOME Wayland) only actually loads/renders web pages if run with the command-line switch `--profile ~/.mozila/firefox/xxxxxxxx` where `xxxxxxxx` is the path to the default profile. If I omit the command-line switch, firefox seems to run fine except that no connections are ever successfully made and all pages remain blanck. I imagine there is a corrupted file somewhere but i don't understand why the default profile would work fine when it is explicitly invoked with the `--profile` switch, but not otherwise. Thank yo uas always!

Vybrané riešenie

See also:

  • Bug 1543600 - [Wayland] Enable by default on nighly & qualified systems
  • Bug 1522780 - [Wayland] Use MOZ_ENABLE_WAYLAND to enable wayland backend
Čítať túto odpoveď v kontexte 👍 0

Všetky odpovede (3)

titaniumbones
titaniumbones Autor otázky
more options

Just checked with a local file, and it appears that local resources load but all non-local resources are blocked -- they don't even appear in the network pane of the devtools. THank you for hte help!

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 10 Contributor
more options

When you start Nightly without a profile path, what profile does it use? Try loading the internal about:profiles page to see its name and path. There also is a possibility that it creates and uses a temporary profile. And/or that it's a new Nightly glitch that support forum volunteers won't know anything about.

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Vybrané riešenie

See also:

  • Bug 1543600 - [Wayland] Enable by default on nighly & qualified systems
  • Bug 1522780 - [Wayland] Use MOZ_ENABLE_WAYLAND to enable wayland backend