Your message dated Thu, 03 Jul 2008 15:49:13 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#487995: 2.4.3 fixes problem?
has caused the Debian Bug report #487995,
regarding pidgin: Segfaults randomly on dbus message
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
487995: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=487995
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: pidgin
Version: 2.4.2-2
Severity: important
Hi,
Pidgin seems to be randomly segfaulting on receiving a particular dbus message.
The gdb backtrace and debug log are not very informative:
(11:10:44) cap: Executing: insert into cap_status (buddy, account,
protocol, status, event_time) values([EMAIL PROTECTED],
[EMAIL PROTECTED]/Gaim, prpl-jabber, available, now()); [New Thread
0xb515cb90 (LWP 29009)] libhal.c 3476 : Error unsubscribing to signals,
error=Connection is closed
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb71a2720 (LWP 28710)]
0xb7845766 in ?? () from /usr/lib/libdbus-1.so.3
(gdb) bt
#0 0xb7845766 in ?? () from /usr/lib/libdbus-1.so.3
#1 0xbfbc2378 in ?? ()
#2 0xb78451aa in ?? () from /usr/lib/libdbus-1.so.3
#3 0x00000000 in ?? ()
(gdb) bt full
#0 0xb7845766 in ?? () from /usr/lib/libdbus-1.so.3
No symbol table info available.
#1 0xbfbc2378 in ?? ()
No symbol table info available.
#2 0xb78451aa in ?? () from /usr/lib/libdbus-1.so.3
No symbol table info available.
#3 0x00000000 in ?? ()
No symbol table info available.
(gdb)
The first line is the last element of debug output. The I see the
peculiar hal warning, which always seems to occur just prior to the
segfault. It may well be that the dbus/hal environment on this machine
is slightly hosed (though I don't really see how), but I think that that
is not a valid cause for pidgin to segfault when it receives a bad dbus
message, do you?
Thanks
Christian
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.25-2-686-bigmem (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages pidgin depends on:
ii gconf2 2.22.0-1 GNOME configuration database syste
ii libatk1.0-0 1.22.0-1 The ATK accessibility toolkit
ii libc6 2.7-12 GNU C Library: Shared libraries
ii libcairo2 1.6.4-6 The Cairo 2D vector graphics libra
ii libdbus-1-3 1.2.1-2 simple interprocess messaging syst
ii libdbus-glib-1-2 0.76-1 simple interprocess messaging syst
ii libglib2.0-0 2.16.3-2 The GLib library of C routines
ii libgstreamer0.10-0 0.10.20-1 Core GStreamer libraries and eleme
ii libgtk2.0-0 2.12.10-2 The GTK+ graphical user interface
ii libgtkspell0 2.0.13-1 a spell-checking addon for GTK's T
ii libice6 2:1.0.4-1 X11 Inter-Client Exchange library
ii libpango1.0-0 1.20.2-2 Layout and rendering of internatio
ii libpurple0 2.4.2-2 multi-protocol instant messaging l
ii libsm6 2:1.0.3-2 X11 Session Management library
ii libstartup-notification0 0.9-1 library for program launch feedbac
ii libx11-6 2:1.1.4-2 X11 client-side library
ii libxss1 1:1.1.3-1 X11 Screen Saver extension library
ii perl 5.10.0-11 Larry Wall's Practical Extraction
ii perl-base [perlapi-5.10.0] 5.10.0-11 The Pathologically Eclectic Rubbis
ii pidgin-data 2.4.2-2 multi-protocol instant messaging c
Versions of packages pidgin recommends:
ii gstreamer0.10-plugins-base 0.10.20-1 GStreamer plugins from the "base"
ii gstreamer0.10-plugins-good 0.10.8-4 GStreamer plugins from the "good"
-- no debconf information
--- End Message ---
--- Begin Message ---
That's what I figured.
On Thu, 2008-07-03 at 15:23 -0400, Christian Weeks wrote:
> Hi
> This is just to update you that it appears that 2.4.3-1 has apparently
> fixed the problem. I speculate that the Network Manager fix was
> interfering with dbus somehow and causing the segfault.
--- End Message ---
