This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Ova tema je arhivirana. Pitajte drugo pitanje ako vam je potrebna pomoć.

Firefox crashes whenever I try saving an image on Arch Linux

  • 1 odgovor
  • 1 ima ovaj problem
  • 1 view
  • Posljednji odgovor poslao nickmcummins

nickmcummins
nickmcummins
more options

This is similar to https://support.mozilla.org/en-US/questions/1113518, except I am using Arch Linux, not Windows.

I do not know specifically when this started happening, but it was within the past 2 days, if not with the last 24 hours. Since Arch Linux has continuous rollouts rather than periodic releases, there are almost always some packages that get updated each day, but there was not anything out of the ordinary that was installed/updated in the past few days.

Here are the links to my crash reports: https://crash-stats.mozilla.com/report/index/bp-d879cc0b-7662-4ee9-bd0e-55d072160520 https://crash-stats.mozilla.com/report/index/bp-77ba4932-4105-4580-8465-ec14f2160520

I uploaded the error message that appeared, also: http://www.nickmcummins.com/files/firefox-crash.log

A few additional comments: - I first noticed this in the standard release version of Firefox, but I tried on Nightly to see if it was happening there too. The problem occurs for both versions. - I have un-installed and re-installed firefox through Arch's pacman package management system. - I have created a new profile and ensured that no extensions were installed. - I have profile sync and am logged in on both my Arch and OSX Firefox. The crashing behavior does not happen on OSX when using the same profile/account as the one I use on Arch Linux.

Thanks in advance for any help, this problem is frustrating.

This is similar to https://support.mozilla.org/en-US/questions/1113518, except I am using Arch Linux, not Windows. I do not know specifically when this started happening, but it was within the past 2 days, if not with the last 24 hours. Since Arch Linux has continuous rollouts rather than periodic releases, there are almost always some packages that get updated each day, but there was not anything out of the ordinary that was installed/updated in the past few days. Here are the links to my crash reports: https://crash-stats.mozilla.com/report/index/bp-d879cc0b-7662-4ee9-bd0e-55d072160520 https://crash-stats.mozilla.com/report/index/bp-77ba4932-4105-4580-8465-ec14f2160520 I uploaded the error message that appeared, also: http://www.nickmcummins.com/files/firefox-crash.log A few additional comments: - I first noticed this in the standard release version of Firefox, but I tried on Nightly to see if it was happening there too. The problem occurs for both versions. - I have un-installed and re-installed firefox through Arch's pacman package management system. - I have created a new profile and ensured that no extensions were installed. - I have profile sync and am logged in on both my Arch and OSX Firefox. The crashing behavior does not happen on OSX when using the same profile/account as the one I use on Arch Linux. Thanks in advance for any help, this problem is frustrating.

Izabrano rješenje

I'm not sure what changed, and I didn't do anything specifically to fix this, but as of today, after running pacman to get my latest updates, and restarting my machine, this issue is no longer happening.

Pročitajte ovaj odgovor sa objašnjenjem 👍 0

All Replies (1)

nickmcummins
nickmcummins Vlasnik pitanja
more options

Odabrano rješenje

I'm not sure what changed, and I didn't do anything specifically to fix this, but as of today, after running pacman to get my latest updates, and restarting my machine, this issue is no longer happening.