Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Learn More

After an update firefox crashes at start even in safe mode

  • 5 Antworten
  • 0 haben dieses Problem
  • 1 Aufruf
  • Letzte Antwort von jonzn4SUSE

more options

Crash ID: bp-c48a5523-2d22-4286-9a4b-c699f0221209

This was after an update last week to arch, I installed all the bits that seemed to be missing and now it crashes without giving me much info at all.

Crash ID: bp-c48a5523-2d22-4286-9a4b-c699f0221209 This was after an update last week to arch, I installed all the bits that seemed to be missing and now it crashes without giving me much info at all.

Alle Antworten (5)

more options

Try downloading Firefox from Mozilla, run firefox-bin from the folder and see if you have the same issue. https://www.mozilla.org/en-US/firefox/all/#product-desktop-release

What desktop? X11 or Wayland?


Operating System: openSUSE Tumbleweed 20221205 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 Kernel Version: 6.0.10-1-default (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-9850H CPU @ 2.60GHz Memory: 125.2 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 Manufacturer: HP Product Name: HP ZBook 17 G6

Geändert am von jonzn4SUSE

more options

Downloading it straight from mozilla including the nightlys produces the same crash Crash ID: bp-61778999-72c6-44d6-9ad5-a11f10221213

Gnome 43.1 on wayland Ryzen 3950X 64 gigs of ram Dual GPU: Radeon RX 570 (Running as the hosts display) Geforce 3060 (Blocked from the host and passed through to a VM)

more options

Is the crashing happening on a VM? Since it's crashing with all browsers, this doesn't seem like a browser issue. I think more of a OS issue. I would break out a live usb stick of another OS or the previous to test.

more options

The crash is happening on the host, it seems like a OS issue but I was hoping someone could clean some insight from the dumps sent up since firefox is giving me 0 insight and I don't understand it well enough to try and read the dumps. Its the only app doing it to be totally fair.

more options

Maybe this can narrow it down. Run this strace -o firefox_log -t firefox & see what kills firefox. The -o will output to the file firefox_log and the -t will put timestamps in the output.

Geändert am von jonzn4SUSE