init crashed with SIGSEGV in nih_main_loop()

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

Bug Description

init crashed with SIGSEGV in nih_main_loop()

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: upstart 1.9.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1
Uname: Linux 3.10.0-3-generic i686
ApportVersion: 2.11-0ubuntu1
Architecture: i386
Date: Wed Jul 17 20:15:00 2013
ExecutablePath: /sbin/init
InstallationDate: Installed on 2013-06-07 (40 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130607)
MarkForUpload: True
ProcCmdline: init --user
ProcEnviron:
 LANGUAGE=ru
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb7754090: cmpl $0x2,0x10(%esi)
 PC (0xb7754090) ok
 source "$0x2" ok
 destination "0x10(%esi)" (0x45434e51) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: upstart
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 nih_main_loop () from /lib/i386-linux-gnu/libnih.so.1
Title: init crashed with SIGSEGV in nih_main_loop()
UpgradeStatus: No upgrade log present (probably fresh install)
UpstartBugCategory: Session
UpstartRunningSessionCount: 1
UpstartRunningSystemVersion: init (upstart 1.9.1)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
upstart.upstart-file-bridge.log:
 Job got added /com/ubuntu/Upstart/jobs/unicast_2dlocal_2davahi
 Job got added /com/ubuntu/Upstart/jobs/update_2dnotifier_2dcrash
 Job got added /com/ubuntu/Upstart/jobs/update_2dnotifier_2drelease

Related branches

Revision history for this message
rolmops (dr150259) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
Revision history for this message
James Hunt (jamesodhunt) wrote :

@rolmops - Thanks for reporting this bug but without a stack trace, this is going to be difficult to track down.

Can you tell me what was happening when the crash occurred? Also:

- Had you just installed package updates?
- Have you got a ~/.cache/upstart/upstart.state file?
- Do you happen to have the ~/.xsession-error file from when the crash occurred?

James Hunt (jamesodhunt)
information type: Private → Public
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.