dbus-launch crashed with SIGSEGV in kill()

[Grzegorz Bąk]

Binary package hint: dbus

Ubuntu jaunty (development branch)
Release: 9.04

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/dbus-launch
Package: dbus-x11 1.2.4-0ubuntu2
ProcCmdline: /usr/bin/dbus-launch --exit-with-session x-session-manager
ProcEnviron:
 SHELL=/bin/bash
 LANG=pl_PL.UTF-8
 LANGUAGE=pl_PL:pl:en_GB:en
Signal: 11
SourcePackage: dbus
StacktraceTop:
 kill () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
 ?? ()
 ?? ()
 _XIOError () from /usr/lib/libX11.so.6
Title: dbus-launch crashed with SIGSEGV in kill()
Uname: Linux 2.6.28-4-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:kill () from /lib/tls/i686/cmov/libc.so.6
kill_bus () at dbus-launch.c:343
kill_bus_and_exit (exitcode=0) at dbus-launch.c:354
x11_handle_event () at dbus-launch-x11.c:459
_XIOError (dpy=0x83a26e8) at ../../src/XlibInt.c:2947

[Connor Imes (ckimes)]

Forwarded from Ubuntu's Launchpad - https://launchpad.net/bugs/318963

Ubuntu Jaunty 9.04 (development)
Package: dbus-x11 1.2.4-0ubuntu2

Stacktrace is attached, and is also available on Launchpad.

If more information is needed, please respond on the Launchpad bug report if possible so that original reporter will see responses. Thank you.

[Connor Imes (ckimes)]

Created an attachment (id=22321)
Thread Stack Trace

[Scott James Remnant (Canonical) (canonical-scott)]

Absolutely no idea why things would crash inside kill(), we don't pass pointers to it

[Simon McVittie (smcv)]

Is this reproducible/has it ever happened again? As Scott says, the stack trace makes no sense, since kill() doesn't take pointer arguments.

Could it have been killed by some other process, or by the OOM-killer? (I'd expect that to use SIGKILL rather than SIGSEGV, though.)

[Simon McVittie (smcv)]

As Scott commented downstream, this makes very little sense; kill() doesn't take any pointer arguments...

Is this reproducible?

[Simon McVittie (smcv)]

I have no idea; the stack trace makes no sense. If this is reproducible, please reopen and provide more information.

[Connor Imes (ckimes)]

Closed upstream - if this is still a problem, please reopen the bug. Thanks.