Ubuntu
xchat package

xchat crashed with SIGSEGV in dbus_connection_dispatch()

Bug #549972 reported by David Mazary
28
This bug affects 3 people
Affects Status Importance Assigned to Milestone
xchat (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: xchat

Using Lucid with most recent updates.
Closed xchat with Ctrl+Q, window closed but apport caught a crash.
I recently installed the xchat-indicator package, so that is what I suspect.

ProblemType: Crash
Architecture: amd64
Date: Sat Mar 27 20:18:23 2010
Disassembly: => 0x7fd4a48a7a40: Cannot access memory at address 0x7fd4a48a7a40
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/xchat
NonfreeKernelModules: nvidia
Package: xchat 2.8.6-4ubuntu4
ProcCmdline: xchat
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
SegvAnalysis:
 Segfault happened at: 0x7fd4a48a7a40: Cannot access memory at address 0x7fd4a48a7a40
 PC (0x7fd4a48a7a40) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: xchat
StacktraceTop:
 ?? ()
 dbus_connection_dispatch () from /lib/libdbus-1.so.3
 ?? () from /usr/lib/libdbus-glib-1.so.2
 g_main_context_dispatch ()
 ?? () from /lib/libglib-2.0.so.0
Title: xchat crashed with SIGSEGV in dbus_connection_dispatch()
Uname: Linux 2.6.32-17-generic x86_64
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

Revision history for this message
David Mazary (dmaz) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 dbus_connection_dispatch (connection=0x1e743a0)
 message_queue_dispatch (
 g_main_context_dispatch ()
 ?? () from /lib/libglib-2.0.so.0

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 xchat (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Fabien Tassin (fta) wrote :

same here:

Program received signal SIGSEGV, Segmentation fault.
0x015c1d70 in ?? ()
(gdb) bt
#0 0x015c1d70 in ?? ()
#1 0x00a84c6d in dbus_connection_dispatch () from /lib/libdbus-1.so.3
#2 0x00a5e97d in ?? () from /usr/lib/libdbus-glib-1.so.2
#3 0x00e111b5 in g_main_dispatch (context=0x8108bd0) at /build/buildd/glib2.0-2.25.11/glib/gmain.c:2119
#4 g_main_context_dispatch (context=0x8108bd0) at /build/buildd/glib2.0-2.25.11/glib/gmain.c:2672
#5 0x00e14fc8 in g_main_context_iterate (context=0x8108bd0, block=<value optimized out>, dispatch=1, self=0x80ddc58) at /build/buildd/glib2.0-2.25.11/glib/gmain.c:2750
#6 0x00e15507 in g_main_loop_run (loop=0x8155b78) at /build/buildd/glib2.0-2.25.11/glib/gmain.c:2958
#7 0x003f634d in IA__gtk_clipboard_store (clipboard=0x85300b8) at /build/buildd/gtk+2.0-2.21.2/gtk/gtkclipboard.c:2042
#8 0x003f63ff in _gtk_clipboard_store_all () at /build/buildd/gtk+2.0-2.21.2/gtk/gtkclipboard.c:2078
#9 0x0028979b in IA__gtk_main () at /build/buildd/gtk+2.0-2.21.2/gtk/gtkmain.c:1270
#10 0x0806045b in fe_main () at fe-gtk.c:290
#11 0x080adeff in main (argc=1, argv=0xbffff8e4) at xchat.c:922

maverick i386.

Changed in xchat (Ubuntu):
status: New → Confirmed
Andreas Moog (ampelbein)
visibility: private → public
Revision history for this message
dino99 (9d9) wrote :

This version has expired long ago; no more supported

Changed in xchat (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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