dbus-launch crashed with SIGSEGV in read()

Bug #336849 reported by pitwalker
6
Affects Status Importance Assigned to Milestone
D-Bus
Invalid
Medium
dbus (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: dbus

I start a gnome-terminal (l run su and mc)
I start a firexox
I start a guest session (I launch gedit)
I switch back to the previous user and the crash report comes
everyting works

(I run Jaunty under virtualbox 2.1.4, I have kernel oops in every login.)

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/dbus-launch
Package: dbus-x11 1.2.12-0ubuntu2
ProcCmdline: /usr/bin/dbus-launch --exit-with-session /usr/bin/pulse-session /usr/bin/seahorse-agent --execute /usr/bin/gnome-session
ProcEnviron:
 LANG=hu_HU.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: dbus
StacktraceTop:
 read () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /usr/lib/libxcb.so.1
 xcb_poll_for_event () from /usr/lib/libxcb.so.1
 ?? () from /usr/lib/libX11.so.6
 ?? () from /usr/lib/libX11.so.6
Title: dbus-launch crashed with SIGSEGV in read()
Uname: Linux 2.6.28-8-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
pitwalker (pitwalker) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:read () from /lib/tls/i686/cmov/libc.so.6
_xcb_in_read (c=0x8464e08) at /usr/include/bits/unistd.h:45
xcb_poll_for_event (c=0x8464e08)
wait_or_poll_for_event (dpy=0x8464690, wait=11)
process_responses (dpy=0x8464690, wait_for_first_event=0,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in dbus:
importance: Undecided → Medium
Revision history for this message
In , Scott James Remnant (Canonical) (canonical-scott) wrote :

Filed in Launchpad:

#0 0xb7f2ee52 in read () from /lib/tls/i686/cmov/libc.so.6
No locals.
#1 0xb7e49bfe in _xcb_in_read (c=0x8464e08) at /usr/include/bits/unistd.h:45
 n = 32
#2 0xb7e4a2a0 in xcb_poll_for_event (c=0x8464e08)
    at /build/buildd/libxcb-1.1.93/./src/xcb_in.c:439
 ret = (xcb_generic_event_t *) 0x0
#3 0xb7fff459 in wait_or_poll_for_event (dpy=0x8464690, wait=11)
    at ../../src/xcb_io.c:145
 c = (xcb_connection_t *) 0x8464e08
 event = <value optimized out>
#4 0xb7fff607 in process_responses (dpy=0x8464690, wait_for_first_event=0,
    current_error=0x0, current_request=0) at ../../src/xcb_io.c:209
 req = (PendingRequest *) 0x846e280
 event_sequence = <value optimized out>
 reply = (void *) 0xb80dd828
 event = (xcb_generic_event_t *) 0x846e128
 error = (xcb_generic_error_t *) 0xb80cde7b
 c = (xcb_connection_t *) 0x8464e08
 __PRETTY_FUNCTION__ = "process_responses"
#5 0xb80000e5 in _XEventsQueued (dpy=0x8464690, mode=2)
    at ../../src/xcb_io.c:256
No locals.
#6 0xb7fe8738 in XPending (dpy=0x8464690) at ../../src/Pending.c:56
 ret_val = 0
#7 0x0804b396 in x11_handle_event () at dbus-launch-x11.c:453
No locals.
#8 0x080498bd in kill_bus_when_session_ends () at dbus-launch.c:471
 tty_fd = -1
 x_fd = 6
 read_set = {__fds_bits = {64, 0 <repeats 31 times>}}
 err_set = {__fds_bits = {0 <repeats 32 times>}}
 act = {__sigaction_handler = {
    sa_handler = 0x80494a0 <signal_handler>,
    sa_sigaction = 0x80494a0 <signal_handler>}, sa_mask = {__val = {
      0 <repeats 32 times>}}, sa_flags = 0, sa_restorer = 0xbfcdb21c}
 empty_mask = {__val = {0 <repeats 32 times>}}
#9 0x0804a97f in main (argc=6, argv=0xbfcdb8b4) at dbus-launch.c:649
 write_pid_fd_as_string = "e0e108b621904f2255ed69a749a843b4\000\000\000\000\004\000\000\000Î\005\f¸\220\002\f¸\000\000\000\000\000\000\000\000õP\r¸\b\000\000"
 write_address_fd_as_string = '\0' <repeats 36 times>, "õÌÍ¿N\237ì·ÙÁ÷·ôß\004\b\b¸Í¿l\217\004\bô\237û·"
 prev_arg = 0xbfcdcd0a "--exit-with-session"
 shname = <value optimized out>
 runprog = 0xbfcdcd1e "/usr/bin/pulse-session"
 remaining_args = 3
 exit_with_session = 1
 binary_syntax = 0
 c_shell_syntax = 0
 bourne_shell_syntax = 0
 auto_shell_syntax = 0
 autolaunch = 0
 requires_arg = 0
 close_stderr = 0
 i = <value optimized out>
 bus_pid_to_launcher_pipe = {4, 6}
 bus_pid_to_babysitter_pipe = {10, 11}
 bus_address_to_launcher_pipe = {8, 9}
 config_file = 0x0

Changed in dbus (Ubuntu):
status: New → Triaged
Changed in dbus:
status: Unknown → Confirmed
Changed in dbus:
importance: Unknown → Medium
Changed in dbus:
importance: Medium → Unknown
Changed in dbus:
importance: Unknown → Medium
Revision history for this message
In , Simon McVittie (smcv) wrote :

I think it's safe to say this is in the category of "a bug was auto-filed in Launchpad and nobody knows how to reproduce it". It might even be an xcb bug anyway.

Changed in dbus:
status: Confirmed → Invalid
Revision history for this message
Mörgæs (moergaes) wrote :

Closing due to age.
If a similar bug appears in 21.10 please open a new report.

Changed in dbus (Ubuntu):
status: Triaged → Invalid
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.