pidgin crashed with signal 5 in dbus_g_proxy_call()

Bug #262642 reported by Ian
8
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: pidgin

Was trying to connect Pidgin to Skype to use pidgins skype plugin

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/pidgin
Package: pidgin 1:2.5.0-0ubuntu2
ProcAttrCurrent: unconfined
ProcCmdline: pidgin
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: pidgin
StacktraceTop:
 ?? () from /usr/lib/libdbus-glib-1.so.2
 dbus_g_proxy_call () from /usr/lib/libdbus-glib-1.so.2
 send_message (
 ?? () from /usr/lib/libglib-2.0.so.0
 start_thread () from /lib/tls/i686/cmov/libpthread.so.0
Title: pidgin crashed with signal 5 in dbus_g_proxy_call()
Uname: Linux 2.6.27-1-generic i686
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

Revision history for this message
Ian (mail-ianargent) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:dbus_g_proxy_begin_call_internal (proxy=0x9f9ea00, method=<value optimized out>, notify=0, user_data=0x0,
dbus_g_proxy_call (proxy=0x9f9ea00, method=0xb622644e <Address 0xb622644e out of bounds>, error=0xb37ff33c,
?? ()
g_thread_create_proxy (data=0xb38110b0) at /build/buildd/glib2.0-2.17.7/glib/gthread.c:635
start_thread () from /lib/tls/i686/cmov/libpthread.so.0

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Could you try to reproduce the same with Ubuntu 8.10 or 9.04? Thanks in advance.

Changed in pidgin:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in pidgin:
status: Incomplete → 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.