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”.

Learn More

Firefox password sync causes crash? [Ubuntu Focal]

  • 7 odpovedí
  • 0 má tento problém
  • 42 zobrazení
  • Posledná odpoveď od jonzn4SUSE

more options

Brand new installation of Ubuntu Focal (on an ARM Chromebook, using Crouton). Installed Firefox (104), runs fine but as soon as I sign into my Firefox account it immediately crashes. Continues to crash if I start in safe-mode, so I don't think the problem is an extension. After some online research and some trial and error I seem to have determined that I can sign into my Firefox account as long as password sync is disabled. But as soon as I enable password sync, Firefox immediately crashes.

Error message in terminal is always about GPU, which maybe isn't properly set up or maybe Firefox has a problem with it, but if I use the software renderer it doesn't cause a problem (MOZ_ENABLE_WAYLAND=0 firefox). Hard to imagine that this has anything to do with crashing when syncing passwords?

Crash Annotation GraphicsCriticalError: |[0][GFX1-]: No GPUs detected via PCI (t=2.77546) [GFX1-]: No GPUs detected via PCI Crash Annotation GraphicsCriticalError: |[0][GFX1-]: No GPUs detected via PCI (t=2.77546) |[1][GFX1-]: glxtest: process failed (received signal 11) (t=2.77573) [GFX1-]: glxtest: process failed (received signal 11) Missing chrome or resource URL: resource://gre/modules/UpdateListener.sys.mjs Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Receive IPC close with reason=AbnormalShutdown (t=3.29811) Exiting due to channel error. Segmentation fault (core dumped)

Brand new installation of Ubuntu Focal (on an ARM Chromebook, using Crouton). Installed Firefox (104), runs fine but as soon as I sign into my Firefox account it immediately crashes. Continues to crash if I start in safe-mode, so I don't think the problem is an extension. After some online research and some trial and error I seem to have determined that I can sign into my Firefox account as long as password sync is disabled. But as soon as I enable password sync, Firefox immediately crashes. Error message in terminal is always about GPU, which maybe isn't properly set up or maybe Firefox has a problem with it, but if I use the software renderer it doesn't cause a problem (MOZ_ENABLE_WAYLAND=0 firefox). Hard to imagine that this has anything to do with crashing when syncing passwords? Crash Annotation GraphicsCriticalError: |[0][GFX1-]: No GPUs detected via PCI (t=2.77546) [GFX1-]: No GPUs detected via PCI Crash Annotation GraphicsCriticalError: |[0][GFX1-]: No GPUs detected via PCI (t=2.77546) |[1][GFX1-]: glxtest: process failed (received signal 11) (t=2.77573) [GFX1-]: glxtest: process failed (received signal 11) Missing chrome or resource URL: resource://gre/modules/UpdateListener.sys.mjs Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Receive IPC close with reason=AbnormalShutdown (t=3.29811) Exiting due to channel error. Segmentation fault (core dumped)

Všetky odpovede (7)

more options

We're sorry to hear that Firefox is crashing. In order to assist you better, please follow the steps below to provide us crash IDs to help us learn more about your crash.

The crash report is several pages of data. We need the report numbers to see the whole report.

  1. Enter about:crashes in the Firefox address bar and press Enter. A list of Submitted/Unsubmitted Crash Reports will appear, similar to the one shown below.
  2. Copy the 5 most recent Submitted Report IDs that start with bp- and then go back to your forum question and paste those IDs into the "Post a Reply" box.

Note: If a recent Report ID does not start with bp- click on it to submit the report.

(Please don't take a screenshot of your crashes, just copy and paste the IDs. The below image is just an example of what your Firefox screen should look like.)

Fx64Beta-aboutcrashes-unsubmitted

Thank you for your help!

More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.

Pomohla vám táto odpoveď?

more options

About:crashes doesn’t exist, gives an error. I guess this means that the version that I am using (Ubuntu) was compiled without crash reporting?

I've switched from Ubuntu Focal to Debian Bullseye, and I'm now using debian's firefox-esr which I know from previous testing has the same issue. Here are the last five crash reports from firefox-esr:

https://crash-stats.mozilla.org/report/index/bp-a2d02bac-4250-46c8-96bf-9e4fd0220830 https://crash-stats.mozilla.org/report/index/bp-f0c8a0fa-9908-462c-8512-ca1800220830 https://crash-stats.mozilla.org/report/index/bp-bb805793-f592-48e9-8c76-05fde0220830 https://crash-stats.mozilla.org/report/index/bp-d8e0bb6f-2fd3-44c1-aa02-19d2d0220830 https://crash-stats.mozilla.org/report/index/bp-49d66377-d6da-48a4-91fb-ec0bf0220830

Each of these is an immediate crash as soon as Firefox starts up and attempts to sync. Now that I have de-selected password sync, I am able to use FIrefox normally.

Upravil(a) mc510 dňa

Pomohla vám táto odpoveď?

more options

Wayland.... Can you try in X11 to see if you have the same issue?

Pomohla vám táto odpoveď?

more options

Looks to me like I'm already using X11 rather than Wayland about:support screenshot attached

Pomohla vám táto odpoveď?

more options

After searching the error Crash Annotation GraphicsCriticalError: |[0][GFX1-]: No GPUs detected via PCI looks like a BUG.

Pomohla vám táto odpoveď?

more options

jonzn4SUSE said

After searching the error Crash Annotation GraphicsCriticalError: |[0][GFX1-]: No GPUs detected via PCI looks like a BUG.

Meaning this is already on radar of Firefox developers? Or I should open a bug report?

Pomohla vám táto odpoveď?

more options

Why not open one and let them advise on the next step.

Pomohla vám táto odpoveď?

Položiť otázku

Ak chcete pridať odpoveď, musíte sa prihlásiť k svojmu účtu. Ak účet doteraz nemáte, položte novú otázku.