Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

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

startup crash fixed

  • 2 cavab
  • 1 has this problem
  • 56 views
  • Last reply by hpfeil1

more options

Fixed a startup crash in Linux KDE5/Plasma5 with `chmod 1777 /dev/shm` Cryptic crash message in konqueror:

[7322, Main Thread] WARNING: failed to open shm: Permission denied: file /builds/worker/checkouts/gecko/ipc/chromium/src/base/shared_memory_posix.cc, line 246 ExceptionHandler::GenerateDump

Key phrase: "shm permission denied" - ignore the rest.

Spent a half hour trying to add the fix to the crash reports, found no way to do that. Once the cause of the crash is fixed, there is no way to add that information to the crash report. Developers just get bombed with crash reports every time I click Restart.

These should be closed with a note to check /dev/shm permissions. The '1777' was changed after a system update.

bp-bcedb86c-ca1f-4923-8c7f-ff3570200419 4/19/20, 4:48 PM bp-20bcf048-8fdc-4fc5-9dc0-272500200419 4/19/20, 4:42 PM bp-f9680944-e772-4b7d-8d95-4c8290200419 4/19/20, 4:41 PM bp-0cdd32ef-4e9f-4763-848c-3c8a30200419

Fixed a startup crash in Linux KDE5/Plasma5 with `chmod 1777 /dev/shm` Cryptic crash message in konqueror: [7322, Main Thread] WARNING: failed to open shm: Permission denied: file /builds/worker/checkouts/gecko/ipc/chromium/src/base/shared_memory_posix.cc, line 246 ExceptionHandler::GenerateDump Key phrase: "shm permission denied" - ignore the rest. Spent a half hour trying to add the fix to the crash reports, found no way to do that. Once the cause of the crash is fixed, there is no way to add that information to the crash report. Developers just get bombed with crash reports every time I click Restart. These should be closed with a note to check /dev/shm permissions. The '1777' was changed after a system update. bp-bcedb86c-ca1f-4923-8c7f-ff3570200419 4/19/20, 4:48 PM bp-20bcf048-8fdc-4fc5-9dc0-272500200419 4/19/20, 4:42 PM bp-f9680944-e772-4b7d-8d95-4c8290200419 4/19/20, 4:41 PM bp-0cdd32ef-4e9f-4763-848c-3c8a30200419

Chosen solution

Not a firefox bug. Bash permissions on /dev/shm was 755. Chmod go+w or 777 fixed the problem.

Read this answer in context 👍 0

All Replies (2)

more options

Looks like you need to download and reinstall Firefox. Looking at the crash reports, it seem like ff corrupted itself. Never heard of this before. Claim a bug report

more options

Seçilmiş Həll

Not a firefox bug. Bash permissions on /dev/shm was 755. Chmod go+w or 777 fixed the problem.