upstart crashed with SIGSEGV

Bug #1429736 reported by vito
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
upstart (Ubuntu)
New
Undecided
Unassigned

Bug Description

after rebooting, popups this error

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: upstart-bin 1.13.2-0ubuntu9
ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
Uname: Linux 3.19.0-7-generic i686
ApportVersion: 2.16.2-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Thu Mar 5 13:57:05 2015
ExecutablePath: /sbin/upstart
InstallationDate: Installed on 2015-03-03 (5 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha i386 (20150224)
ProcCmdline: /sbin/init
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic root=UUID=c8ac14f5-b6c9-4080-9eaf-b50a94e3a591 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x104d0: mov %edi,0x18(%esi)
 PC (0x000104d0) not located in a known VMA region (needed executable region)!
 source "%edi" ok
 destination "0x18(%esi)" (0x0000404a) not located in a known VMA region (needed writable region)!
 Stack pointer not within stack segment
SegvReason:
 executing unknown VMA
 writing NULL VMA
Signal: 11
SourcePackage: upstart
Stacktrace:
 #0 0x000104d0 in ?? ()
 No symbol table info available.
 #1 0x0001012d in ?? ()
 No symbol table info available.
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)
StacktraceTop:
 ?? ()
 ?? ()
Title: upstart crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UpstartBugCategory: System
UpstartRunningSystemVersion: init (upstart 1.13.2)
UserGroups:

modified.conffile..etc.console.setup.compose.ISO.8859.1.inc: [modified]
modified.conffile..etc.console.setup.compose.ISO.8859.13.inc: [modified]
modified.conffile..etc.console.setup.compose.ISO.8859.14.inc: [modified]
modified.conffile..etc.console.setup.compose.ISO.8859.15.inc: [modified]
modified.conffile..etc.console.setup.compose.ISO.8859.2.inc: [modified]
modified.conffile..etc.console.setup.compose.ISO.8859.3.inc: [modified]
modified.conffile..etc.console.setup.compose.ISO.8859.4.inc: [modified]
modified.conffile..etc.console.setup.compose.ISO.8859.7.inc: [modified]
modified.conffile..etc.console.setup.compose.ISO.8859.9.inc: [modified]
modified.conffile..etc.console.setup.compose.VISCII.inc: [modified]
modified.conffile..etc.console.setup.remap.inc: [modified]
mtime.conffile..etc.console.setup.compose.ISO.8859.1.inc: 2015-03-03T20:32:59
mtime.conffile..etc.console.setup.compose.ISO.8859.13.inc: 2015-03-03T20:32:59
mtime.conffile..etc.console.setup.compose.ISO.8859.14.inc: 2015-03-03T20:32:59
mtime.conffile..etc.console.setup.compose.ISO.8859.15.inc: 2015-03-03T20:32:59
mtime.conffile..etc.console.setup.compose.ISO.8859.2.inc: 2015-03-03T20:32:59
mtime.conffile..etc.console.setup.compose.ISO.8859.3.inc: 2015-03-03T20:32:59
mtime.conffile..etc.console.setup.compose.ISO.8859.4.inc: 2015-03-03T20:32:59
mtime.conffile..etc.console.setup.compose.ISO.8859.7.inc: 2015-03-03T20:32:59
mtime.conffile..etc.console.setup.compose.ISO.8859.9.inc: 2015-03-03T20:32:59
mtime.conffile..etc.console.setup.compose.VISCII.inc: 2015-03-03T20:32:59
mtime.conffile..etc.console.setup.remap.inc: 2015-03-03T20:32:59

Revision history for this message
vito (vshvirkov) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1419393, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.