pidgin crashed with SIGSEGV in dbus_g_proxy_call()

Bug #623555 reported by Colan Schwartz
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: pidgin

I noticed that I wasn't getting bubble pop-ups so I went to Tools -> Plugins -> Libnotify Popups to uncheck and then recheck the checkbox to see if that would help. When doing so, Pidgin crashed.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: pidgin 1:2.6.6-1ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-24.41-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Tue Aug 24 15:10:31 2010
ExecutablePath: /usr/bin/pidgin
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
ProcCmdline: pidgin --session 1068d642fdb887b504128225911682747800000030260038 --display :0.0
ProcEnviron:
 LANG=en_CA.utf8
 SHELL=/bin/zsh
SegvAnalysis:
 Segfault happened at: 0x7fe3699e1d75 <dbus_g_proxy_call+133>: cmp %rbp,(%rax)
 PC (0x7fe3699e1d75) ok
 source "%rbp" ok
 destination "(%rax)" (0x00000004) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 dbus_g_proxy_call ()
 notify_get_server_caps ()
 ?? () from /usr/lib/purple-2/pidgin-libnotify.so
 purple_plugin_load () from /usr/lib/libpurple.so.0
 ?? ()
Title: pidgin crashed with SIGSEGV in dbus_g_proxy_call()
UserGroups: adm admin cdrom dialout lp lpadmin plugdev sambashare

Revision history for this message
Colan Schwartz (colan) wrote :
Revision history for this message
Colan Schwartz (colan) wrote :

Here's a core dump without my password in it. ;)

visibility: private → public
Revision history for this message
Colan Schwartz (colan) wrote :

After restarting, I found that unchecking & rechecking the checkbox worked. However, the next time I waited a few minutes before doing it, rather than trying it immediately, and I was able to reproduce it.

Revision history for this message
Simon Déziel (sdeziel) wrote :

I am able to reproduce this using the same pidgin version on amd64. In my case the crash only occurs after I unchecked/checked the checkbox and try to send the pidgin to the system tray.

$ dpkg -l| grep pidgin
ii pidgin 1:2.6.6-1ubuntu4 graphical multi-protocol instant messaging c
ii pidgin-data 1:2.6.6-1ubuntu4 multi-protocol instant messaging client - da
ii pidgin-libnotify 0.14-1ubuntu14 display notification bubbles in pidgin

Note: I am not running the default Lucid kernel but this one :
$ uname -a
Linux simon-laptop 2.6.35-17-generic #23~lucid1-Ubuntu SMP Fri Aug 20 02:07:55 UTC 2010 x86_64 GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 10.04.1 LTS
Release: 10.04
Codename: lucid

Revision history for this message
Simon Déziel (sdeziel) wrote :

Here is the log extract corresponding to the 2 crashes I triggered :

$ grep pidgin /var/log/messages
Aug 24 16:01:27 simon-laptop kernel: [114264.935591] pidgin[2179]: segfault at 1d ip 00007fa209175448 sp 00007fff2bb1c810 error 4 in libgobject-2.0.so.0.2400.1[7fa209166000+45000]
Aug 24 16:32:40 simon-laptop kernel: [116138.656170] pidgin[15648]: segfault at 1d ip 00007f6c9e1bf448 sp 00007ffff2dcd3a0 error 4 in libgobject-2.0.so.0.2400.1[7f6c9e1b0000+45000]

Changed in pidgin (Ubuntu):
status: New → Confirmed
Revision history for this message
Dennis Sheil (dennis-sheil) wrote :

I've reproduced the bug, using the debug symbol packages, for a more robust trace. Trace attached.

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

StacktraceTop:
 dbus_g_proxy_call (proxy=0x1f126b0,
 notify_get_server_caps () at notify.c:226
 plugin_load (plugin=0x1c413b0)
 purple_plugin_load (plugin=0x1c413b0)
 plugin_toggled (cell=<value optimized out>,

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 pidgin (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
dino99 (9d9) wrote :

This version is outdated and no more supported

Changed in pidgin (Ubuntu):
status: Confirmed → 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.