On Sat, Apr 05, 2014 at 07:09:56PM -0000, David Oftedal wrote: > And when I "apt-get show upstart", I get "Version: 1.12.1-0ubuntu1". > That means that the bug either wasn't fixed in version 1.11-0ubuntu2, or > there's been a regression after version 1.11-0ubuntu2.
No, it doesn't mean either of those things; it only means that the currently-available version of upstart is 1.12.1-0ubuntu1. But that is not the version you would have been running *during* the upgrade, so that is not the version that segfaulted. You said you ran into this "during the upgrade to 10.04", but that's clearly not the release you were upgrading to if you now have the upstart from 14.04 in your apt list. You will need to provide more information about what version of Ubuntu you were upgrading *from* when this happened. You probably should also be filing a separate bug report, since this bug is about a crash only in a 14.04 pre-release version of init: while you may have experienced a crash of init when upgrading from a previous Ubuntu release, it would almost certainly not be *this* bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1269731 Title: init crashed with SIGSEGV Status in Upstart: Fix Released Status in “alsa-utils” package in Ubuntu: Fix Released Status in “upstart” package in Ubuntu: Fix Released Bug description: $ telinit U ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: upstart 1.11-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-8.16-generic 3.12.6 Uname: Linux 3.12.0-8-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Thu Jan 16 08:03:58 2014 ExecutablePath: /sbin/init ExecutableTimestamp: 1384521990 InstallationDate: Installed on 2012-12-22 (389 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) ProcCmdline: /sbin/init ProcCwd: / ProcEnviron: TERM=linux PATH=(custom, no user) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.12.0-8-generic root=UUID=8905185c-9d82-498c-970c-6fdb9ee07c45 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7f1191eb98d9: mov 0x20(%rax),%rsi PC (0x7f1191eb98d9) ok source "0x20(%rax)" (0x00000020) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: upstart StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: init crashed with SIGSEGV UpgradeStatus: Upgraded to trusty on 2013-06-19 (210 days ago) UpstartBugCategory: System UpstartRunningSystemVersion: init (upstart 1.11) UserGroups: _LogindSession: / _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] modified.conffile..etc.default.whoopsie: [modified] modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-12-11T09:58:09.227262 mtime.conffile..etc.default.whoopsie: 2013-12-19T16:30:43.528594 mtime.conffile..etc.libvirt.qemu.networks.default.xml: 2013-06-29T21:43:59.656854 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1269731/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
