James Hunt, I currently have a consistent way of reproducing this. First, I have both Chromium and Chrome installed as per below in a fresh+fully updated version of Trusty. Next I opened up Synaptic > typed in the Quick Filter textbox pepper > highlight pepperflashplugin-nonfree > click Visit Homepage and this consistently causes a _sbin_init.0.crash file to appear in var/crash.
For me, the WORKAROUND is just to simply not click the link as the problem has not been reproducible otherwise so far. For an example errors crash of this, please see https://errors.ubuntu.com/oops/341b7c12-8f2f-11e4-b173-fa163e525ba7 . Let me know if this isn't enough information to reproduce and I can up the verbosity on my environment. apt-cache policy google-chrome-stable:i386 google-chrome-stable:i386: Installed: 39.0.2171.95-1 Candidate: 39.0.2171.95-1 Version table: *** 39.0.2171.95-1 0 500 http://dl.google.com/linux/chrome/deb/ stable/main i386 Packages 100 /var/lib/dpkg/status apt-cache policy chromium-browser chromium-browser: Installed: 39.0.2171.65-0ubuntu0.14.04.1.1064 Candidate: 39.0.2171.65-0ubuntu0.14.04.1.1064 Version table: *** 39.0.2171.65-0ubuntu0.14.04.1.1064 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/universe amd64 Packages 100 /var/lib/dpkg/status 34.0.1847.116-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages ** Changed in: upstart (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1300235 Title: init crashed with SIGSEGV Status in upstart package in Ubuntu: Triaged Bug description: none ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: upstart 1.12.1-0ubuntu1 Uname: Linux 3.14.0-031400rc8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 Date: Mon Mar 31 09:53:16 2014 Disassembly: => 0x7fa2b65e94d7: Cannot access memory at address 0x7fa2b65e94d7 ExecutablePath: /sbin/init InstallationDate: Installed on 2014-03-05 (25 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140305) ProcCmdline: /sbin/init ProcEnviron: TERM=linux PATH=(custom, no user) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.14.0-031400rc8-generic root=UUID=bef08855-3273-4d41-ac06-bad06bdd08a4 ro quiet splash SegvAnalysis: Segfault happened at: 0x7fa2b65e94d7: Cannot access memory at address 0x7fa2b65e94d7 PC (0x7fa2b65e94d7) not located in a known VMA region (needed executable region)! Stack pointer not within stack segment SegvReason: executing unknown VMA Signal: 11 SourcePackage: upstart StacktraceTop: ?? () ?? () ?? () Title: init crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSystemVersion: init (upstart 1.12.1) UserGroups: modified.conffile..etc.default.cups: [modified] mtime.conffile..etc.default.cups: 2014-03-11T13:23:34.740893 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1300235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
