Ubuntu
upstart package

initctl crashed with SIGSEGV in _dbus_message_iter_get_args_valist()

Bug #1013897 reported by micu
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
upstart (Ubuntu)
New
Medium
Unassigned

Bug Description

on computer start

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: upstart 1.5-0ubuntu7
ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0
Uname: Linux 3.4.0-5-generic i686
ApportVersion: 2.2.3-0ubuntu3
Architecture: i386
Date: Fri Jun 15 20:05:46 2012
ExecutablePath: /sbin/initctl
ProcCmdline: status container-detect
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
Signal: 11
SourcePackage: upstart
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
 dbus_message_get_args_valist () from /lib/i386-linux-gnu/libdbus-1.so.3
 dbus_message_get_args () from /lib/i386-linux-gnu/libdbus-1.so.3
 dbus_set_error_from_message () from /lib/i386-linux-gnu/libdbus-1.so.3
 dbus_connection_send_with_reply_and_block () from /lib/i386-linux-gnu/libdbus-1.so.3
Title: initctl crashed with SIGSEGV in dbus_message_get_args_valist()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
micu (lgmosneagu) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _dbus_message_iter_get_args_valist (iter=0xbfe24268, error=0x0, first_arg_type=115, var_args=0xbfe242fc ",C\342\277") at ../../dbus/dbus-message.c:792
 dbus_message_get_args_valist (message=0xb926e270, error=0x0, first_arg_type=115, var_args=0xbfe242fc ",C\342\277") at ../../dbus/dbus-message.c:1880
 dbus_message_get_args (message=0xb926e270, error=0x0, first_arg_type=115) at ../../dbus/dbus-message.c:1852
 dbus_set_error_from_message (error=0xbfe24448, message=0xb926e270) at ../../dbus/dbus-message.c:3664
 dbus_connection_send_with_reply_and_block (connection=0xb926baa0, message=0xb926be80, timeout_milliseconds=-1, error=0xbfe24448) at ../../dbus/dbus-connection.c:3525

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in upstart (Ubuntu):
importance: Undecided → Medium
summary: - initctl crashed with SIGSEGV in dbus_message_get_args_valist()
+ initctl crashed with SIGSEGV in _dbus_message_iter_get_args_valist()
tags: removed: need-i386-retrace
micu (lgmosneagu)
visibility: private → public
Revision history for this message
James Hunt (jamesodhunt) wrote :

Hi Micu - thanks for reporting this problem. Please can you tell me if you see this error consistently. It appears to be happening on boot, but do you see the problem "post-boot" if you run:

  /sbin/initctl status container-detect

or,

  sudo /sbin/initctl status container-detect

Revision history for this message
micu (lgmosneagu) wrote :

After a last distribution upgrade a error has disappeared
Now the status of container-detect is stop/waiting, and i don't see the problem
thanks

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.