upstart crashed with SIGSEGV
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
ProcVersionSign
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=
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
UpstartRunningS
UserGroups:
modified.
modified.
modified.
modified.
modified.
modified.
modified.
modified.
modified.
modified.
modified.
mtime.conffile.
mtime.conffile.
mtime.conffile.
mtime.conffile.
mtime.conffile.
mtime.conffile.
mtime.conffile.
mtime.conffile.
mtime.conffile.
mtime.conffile.
mtime.conffile.
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.