Just ran into this problem myself. Occurred after debian auto updates, with first apparent symptom being that Chromium wouldn't open. Paying closer attention showed that Chromium was actually opening, but closing quickly.
This led to an attempt to open Chromium from the Terminal with parameters "--enable-logging --v=1" : which produced a report that included diagnosis/prescription: [13435:13435:543904710486:FATAL:shared_memory_posix.cc(176)] This is frequently caused by incorrect permissions on /dev/shm. Try 'sudo chmod 1777 /dev/shm' to fix Tried 'sudo chmod 1777 /dev/shm' , and the fix worked. Am able to reopen Chromium now! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/886054 Title: chromium-browser crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/886054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
