init assert failure: alloc.c:633: Assertion failed in nih_unref: ref != NULL

Bug #1319083 reported by Michał Sawicz
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
upstart (Ubuntu)
New
Medium
Unassigned

Bug Description

Another crash like bug #1222705

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: upstart 1.12.1-0ubuntu6
Uname: Linux 3.4.0-5-mako armv7l
ApportVersion: 2.14.2-0ubuntu2
Architecture: armhf
AssertionMessage: alloc.c:633: Assertion failed in nih_unref: ref != NULL
CurrentDesktop: Unity
Date: Tue May 13 17:19:06 2014
ExecutablePath: /sbin/init
ExecutableTimestamp: 1399492066
InstallationDate: Installed on 2014-05-13 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140513.1)
ProcCmdline: init --user
ProcCwd: /home/phablet
Signal: 6
SourcePackage: upstart
StacktraceTop:
 ?? () from /lib/arm-linux-gnueabihf/libc.so.6
 raise () from /lib/arm-linux-gnueabihf/libc.so.6
 abort () from /lib/arm-linux-gnueabihf/libc.so.6
 nih_unref () from /lib/arm-linux-gnueabihf/libnih.so.1
 ?? ()
Title: init assert failure: alloc.c:633: Assertion failed in nih_unref: ref != NULL
UpgradeStatus: No upgrade log present (probably fresh install)
UpstartBugCategory: Session
UpstartRunningSessionCount: 1
UpstartRunningSessionJobs: Error: command ['initctl', 'list'] failed with exit code 1: initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart-session/32011/1910: Connection refused
UpstartRunningSessionVersion: Error: command ['initctl', 'version'] failed with exit code 1: initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart-session/32011/1910: Connection refused
UpstartRunningSystemVersion: init (upstart 1.12.1)
UserGroups: adm autopilot cdrom dialout dip nopasswdlogin plugdev sudo tty video
upstart.tty1.override: manual
upstart.tty2.override: manual
upstart.tty3.override: manual
upstart.tty4.override: manual
upstart.tty5.override: manual
upstart.tty6.override: manual

Revision history for this message
Michał Sawicz (saviq) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Possible regression detected

This crash has the same stack trace characteristics as bug #1222705. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

tags: added: regression-retracer
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __libc_do_syscall () at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44
 raise () from /tmp/apport_sandbox_UGsutp/lib/arm-linux-gnueabihf/libc.so.6
 abort () from /tmp/apport_sandbox_UGsutp/lib/arm-linux-gnueabihf/libc.so.6
 nih_unref () at alloc.c:633
 job_change_state ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in upstart (Ubuntu):
importance: Undecided → Medium
tags: removed: need-armhf-retrace
Michał Sawicz (saviq)
information type: Private → Public
Revision history for this message
James Hunt (jamesodhunt) wrote :

Hi Michał - yes, it seems to be the same issue as bug #1222705. What is new is the fact that we now know the call site so tracking down a proper fix should now be easier. Looks like the issue is related to the initctl set-env functions, which only affect Session Inits.

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.