pidgin crashed with SIGSEGV in notify_get_server_caps()

[Alexey Maximov]

Binary package hint: pidgin

bug occurs after enable/disable notify applet

ProblemType: Crash
Architecture: i386
Date: Thu Mar 11 11:12:51 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/pidgin
InstallationMedia: Error: [Errno 13] Отказано в доступе: '/var/log/installer/media-info'
Package: pidgin 1:2.6.6-1ubuntu4
ProcCmdline: pidgin
ProcEnviron:
 SHELL=/bin/bash
 LANG=ru_UA.utf8
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
SegvAnalysis:
 Segfault happened at: 0x16441cb <notify_get_server_caps+235>: mov 0x8(%eax),%eax
 PC (0x016441cb) ok
 source "0x8(%eax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 notify_get_server_caps () from /usr/lib/libnotify.so.1
 ?? () from /usr/lib/purple-2/pidgin-libnotify.so
 purple_plugin_load () from /usr/lib/libpurple.so.0
 ?? ()
 g_cclosure_marshal_VOID__STRING ()
Title: pidgin crashed with SIGSEGV in notify_get_server_caps()
Uname: Linux 2.6.32-16-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:8260): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (bluetooth-applet:8262): Gtk-CRITICAL **: gtk_action_set_sensitive: assertion `GTK_IS_ACTION (action)' failed
 (gnome-terminal:8443): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed

[Alexey Maximov (amax)]

should I recompile pidgin with debug and try again ?

[Apport retracing service (apport)]

StacktraceTop:
 notify_get_server_caps () at notify.c:228
 plugin_load (plugin=0x8930a88) at pidgin-libnotify.c:1193
 purple_plugin_load (plugin=0x8930a88)
 plugin_toggled (cell=0x96bbcf8, pth=0x9428858 "15",
 g_signal_handler_block () from /usr/lib/libgobject-2.0.so.0

[Ted Gould (ted)]

Looking at this it seems to be fixed in libnotify 0.5.0 in that it doesn't use the message in the error from proxy_call which doesn't always set it.

[Ted Gould (ted)]

I've got a package built in my bugfix PPA:

  https://launchpad.net/~ted/+archive/bugfix

It's libnotify 0.4.5-1ubuntu4 which removes the print which is causing this bug. Packaging branch is attached to the bug. If folks could try it and ensure it fixes the bug for them that would be wonderful. Thanks!

[Sebastien Bacher (seb128)]

I've sponsored the change now

[John Dong (jdong)]

ACK from SRU team

[Martin Pitt (pitti)]

Seb, I rejected your upload so that I could add the patch in bug 570462. I re-uploaded this now.

[Martin Pitt (pitti)]

Accepted libnotify into lucid-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

[Rafal-maj-it (rafal-maj-it)]

Sorry it seems to not be fixed.
Ubuntu lucid-proposed amd64.

Im on libnotify1 0.4.5-1ubuntu4 (is this correct? how to check?)

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff0b29d75 in dbus_g_proxy_call () from /usr/lib/libdbus-glib-1.so.2
(gdb) bt
#0 0x00007ffff0b29d75 in dbus_g_proxy_call () from /usr/lib/libdbus-glib-1.so.2
#1 0x00007fffe1b47ce2 in notify_get_server_caps () from /usr/lib/libnotify.so.1
#2 0x00007fffe23752fc in notify_check_caps (plugin=0x7e7480) at pidgin-libnotify.c:1193
#3 plugin_load (plugin=0x7e7480) at pidgin-libnotify.c:1218
#4 0x00007ffff4b90c1f in purple_plugin_load () from /usr/lib/libpurple.so.0
#5 0x000000000048e8eb in plugin_toggled (cell=<value optimized out>, pth=<value optimized out>, data=<value optimized out>) at /build/buildd/pidgin-2.6.6/./pidgin/gtkplugin.c:271
#6 0x00007ffff53235de in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#7 0x00007ffff5337598 in ?? () from /usr/lib/libgobject-2.0.so.0
#8 0x00007ffff5338a76 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#9 0x00007ffff5339033 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#10 0x00007ffff61bd529 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#11 0x00007ffff635e5f0 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#12 0x00007ffff635e9cb in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#13 0x00007ffff635bc14 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#14 0x00007ffff6257178 in ?? () from /usr/lib/l...

[Rafal-maj-it (rafal-maj-it)]

restarting pidgin, and re-logging in into desktop (logout/login) did not help. Toggling that plugin 1 or 2 times crashes as above

[Launchpad Janitor (janitor)]

This bug was fixed in the package libnotify - 0.4.5-1ubuntu4

---------------
libnotify (0.4.5-1ubuntu4) lucid-proposed; urgency=low

  [ Ted Gould ]
  * debian/patches/04_no_error_msg.patch: Remove reporting
    of proxy_call error messages as they don't always exist and
    have been removed upstream in 0.5.0. (LP: #537208)

  [ Guillaume Mazoyer ]
  * debian/patches/04_assertion-on-exit.patch: Fix an assertion when a process
    would init and uninit libnotify without send a notification (LP: #570462).
 -- Ted Gould <email address hidden> Wed, 07 Jul 2010 11:57:03 -0500

[Martin Pitt (pitti)]

Reopening since this failed verification.

[Rolf Leggewie (r0lf)]

lucid has seen the end of its life and is no longer receiving any updates. Marking the lucid task for this ticket as "Won't Fix".