initctl crashed with SIGSEGV in _dbus_message_iter_get_args_valist()

[micu]

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:

[Apport retracing service (apport)]

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

[James Hunt (jamesodhunt)]

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

[micu (lgmosneagu)]

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