touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #45476
[Bug 1300235] Re: init crashed with SIGSEGV
Hi Brian - does running synaptic-pkexec in a terminal trigger the crash?
If not, we really need a trace showing what happens in cbOpenHomepage,
specifically what the 'cmd' vector contains.
--
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