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 (and Unsubmitted, if any) 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.)

Thank you for your help!

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

Here are the five most recent reported crashes:

bp-9b7b4347-93a7-4ba9-9397-be50b0240630 6/30/24, 3:50 PM View bp-ed24c792-ac79-4484-98b3-c42390240630 6/30/24, 12:07 PM View bp-edeed959-9c65-4648-9629-541a90240629 6/29/24, 7:46 AM View bp-25dd4aae-6872-4051-b61d-ddedf0240628 6/28/24, 4:04 PM View bp-012125f0-bdbc-4ee4-8c43-6ac570240627 6/27/24, 5:30 PM View

Here a five more recent crashes after some updates to Plasma 6 and Firefox.

bp-aa9f5f9c-32ae-489d-a9ab-50dc70240709 7/9/24, 8:48 AM View bp-29ae200f-7c24-48ac-9bb3-f5e160240709 7/9/24, 8:48 AM View bp-c409c262-bfcb-4d64-812f-2e9520240709 7/9/24, 8:48 AM View bp-fd401042-8154-42d9-986e-7a80d0240709 7/9/24, 8:48 AM View bp-1a388669-4d85-4a67-9a79-76c560240709 7/9/24, 8:48 AM View

Some more crash reports from today after updating to the latest Firefox version.

bp-56e66efe-0966-4c1f-be24-12e260240724 bp-ce16d2cb-b782-4081-b782-0debb0240724 bp-1de12e7b-b4c4-43c1-9527-ac6bf0240724 bp-e7de4be3-1a06-4a0f-b6fa-a3d890240724

Hey Paul,

He clearly demonstrated to me that the issue is in Wayland since it works in X11. Who's responsible for fixing this KDE / Wayland issue? Sounds like KDE to me.

I tried Wayland, surfed a few sites with no issue. The user needs to provide steps to replicate if it's not happening as soon as the browser opens. Do you have the same issues with Firefox in Troubleshoot Mode? https://support.mozilla.org/en-US/kb/diagnose-firefox-issues-using-troubleshoot-mode#search104

Operating System: openSUSE Tumbleweed 20240726 KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.9.9-1-default (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5825U with Radeon Graphics Memory: 62.1 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: HP Product Name: HP ProBook 455 15.6 inch G9 Notebook PC

Yesterday I ran Firefox in safe mode all day and there were no crashes. It used to crash in safe mode as well after the first update to Plasma 6.1, but there have been several updates since then and yesterday was the first day Firefox didn't crash in safe mode. Today it crashed twice in normal mode, once when I had a password extension enabled, and once when I had Plasma integration enabled. Since I've turned off both of those, I haven't had anymore crashes today.

I've been starting Firefox from a terminal so I can see the output after a crash. I've seen one error I haven't seen before:

"Unexpected error 9 on netlink descriptor 148."

I'm submitting the crash report that might be the one that corresponds with the above error.

bp-303c1de4-66f5-417c-a0e3-a8a760240731

Post a screenshot of the what you're running to start Firefox from the cmd line. I have 4 laptops running or should I say Tumbling and have no such issue.

I'm just entering 'firefox -p' and choosing the default Firefox. There hasn't been anyone yet on openSUSE forums who have posted they're having the same problem as I am.

There hasn't been anyone yet on openSUSE forums who have posted they're having the same problem as I am.

I would ass-u-me because not many start it that way. Interesting way to start if you're not switching all the time. What happens when you run firefox &? Running this also gives you the default profile. My guess is that the way you start Firefox, the process is not in the background. If you wanted to use that same window for something else, it would kill Firefox. Which is why you should put the process in the background using & so that you can continue to use the same windows for something else.

You can do firefox -p & and it should be fine.

I'm not sure what adding & to the command does, or what you mean about "switching all the time", but it doesn't matter because I figured it out. Two or three versions of the nvidia driver ago, the installer's default selection changed from "proprietary nvidia" to "MIT/GPL". I went ahead and used the default selection.

It didn't occur to me that this might affect anything until I decided to install an older driver to see if that made any difference to my problem with Firefox. I noticed that the default for the older driver was the proprietary one again. And that's when the light bulbs went off. I installed the proprietary version of the latest driver and the problem with Firefox went away.