init (chromium-browser) crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
Fix Released
|
High
|
Brian Murray | ||
chromium-browser (Ubuntu) |
Won't Fix
|
High
|
Unassigned |
Bug Description
Test Case
---------
1) Set your default browser to Chromium.
2) Launch synaptic
3) Click on the home page url for a package.
4) Observe chromium-browser not launch
5) Receive apport crash dialog
5) Also notice the apport crash dialog refers to upstart / systemd
none
ProblemType: CrashDistroRelease: Ubuntu 14.04
Package: upstart 1.12.1-0ubuntu1
Uname: Linux 3.14.0-
NonfreeKernelMo
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=
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: 11SourcePackage: upstart
StacktraceTop:
?? ()
?? ()
?? ()
Title: init crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UpstartBugCategory: System
UpstartRunningS
UserGroups:
modified.
mtime.conffile.
Related branches
- Martin Pitt (community): Approve
-
Diff: 27 lines (+8/-5)1 file modifieddata/apport (+8/-5)
CVE References
Changed in upstart (Ubuntu): | |
importance: | Undecided → High |
summary: |
- init crashed with SIGSEGV + init (chromium-browser) crashed with SIGSEGV |
affects: | upstart (Ubuntu) → chromium-browser (Ubuntu) |
StacktraceSource:
#0 0x00007fa2b65e94d7 in ?? ()
#1 0x0000000000000020 in ?? ()
#2 0x0000000000000000 in ?? ()
StacktraceTop:
?? ()
?? ()
?? ()