pidgin crashed with SIGSEGV in g_main_context_dispatch()

Bug #341434 reported by Åskar
86
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: pidgin

Description: Ubuntu jaunty (development branch)
Release: 9.04

pidgin:
  Installerad: 1:2.5.5-1ubuntu1
  Kandidat: 1:2.5.5-1ubuntu1
  Versionstabell:
 *** 1:2.5.5-1ubuntu1 0
        500 http://archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/pidgin
Package: pidgin 1:2.5.5-1ubuntu1
ProcCmdline: pidgin
ProcEnviron:
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 ?? () from /usr/lib/purple-2/libmsn.so
 ?? ()
 ?? () from /usr/lib/libglib-2.0.so.0
 g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/libglib-2.0.so.0
Title: pidgin crashed with SIGSEGV in g_main_context_dispatch()
Uname: Linux 2.6.28-9-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Related branches

Revision history for this message
Åskar (olskar) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:msn_soap_read_cb (data=0x9949740, fd=27, cond=PURPLE_INPUT_READ)
pidgin_io_invoke (source=0x98acac0,
g_io_unix_dispatch (source=0x9c47738,
IA__g_main_context_dispatch (context=0x92857e0)
g_main_context_iterate (context=0x92857e0, block=1,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in pidgin:
importance: Undecided → Medium
Revision history for this message
Sebastien Bacher (seb128) wrote :

the crash seems to match http://developer.pidgin.im/ticket/8594 which is fixed upstream now

Changed in pidgin (Ubuntu):
status: New → Fix Committed
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package pidgin - 1:2.5.5-1ubuntu7

---------------
pidgin (1:2.5.5-1ubuntu7) jaunty; urgency=low

  * debian/patches/71_upstream_change_fix_ssl_crasher.patch:
    - upstream change to fix a crasher issue which has lot of duplicate
      (lp: #328878, #341434, #354272)

 -- Sebastien Bacher <email address hidden> Thu, 09 Apr 2009 00:21:58 +0200

Changed in pidgin (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Shaw Terwilliger (sterwill) wrote :

I have pidgin 1:2.5.5-1ubuntu7 installed and I still see a SIGILL crash. Backtrace follows (with some of my personal information obscured):

#0 0xb5cf1330 in ?? ()
#1 0xb756da20 in xmlWarningMsg (ctxt=0xb5cf1330,
    error=XML_WAR_NS_URI_RELATIVE,
    msg=0xb765c8ec "xmlns: URI %s is not absolute\n",
    str1=0xadbcb11 "vcard-temp", str2=0x0) at parser.c:517
#2 0xb757c7d2 in xmlParseStartTag2 (ctxt=0xa8a06c8, pref=0xbf9dd908,
    URI=0xbf9dd904, tlen=0xbf9dd900) at parser.c:8439
#3 0xb757d044 in xmlParseElement__internal_alias (ctxt=0xa8a06c8)
    at parser.c:9035
#4 0xb75841ea in xmlParseDocument__internal_alias (ctxt=0xa8a06c8)
    at parser.c:9734
#5 0xb7584bf2 in xmlSAXUserParseMemory__internal_alias (sax=0xb78daae0,
    user_data=0xada14e8,
    buffer=0xa158258 "<vCard xmlns='vcard-temp'><FN>SomeNameHere</FN><PHOTO><TYPE>image/png</TYPE><BINVAL>somebase64imagedatahere"..., size=17057)
    at parser.c:13224
#6 0xb7890655 in xmlnode_from_str () from /usr/lib/libpurple.so.0
#7 0xb6196306 in jabber_set_info () from /usr/lib/purple-2/libjabber.so.0
#8 0xb6196596 in jabber_set_buddy_icon ()
   from /usr/lib/purple-2/libjabber.so.0
#9 0xb61969d4 in ?? () from /usr/lib/purple-2/libjabber.so.0
#10 0xb619efdd in jabber_iq_parse () from /usr/lib/purple-2/libjabber.so.0
#11 0xb61a7ef3 in jabber_process_packet ()
   from /usr/lib/purple-2/libjabber.so.0
#12 0xb61ac319 in ?? () from /usr/lib/purple-2/libjabber.so.0
#13 0xb7575248 in xmlParseEndTag2 (ctxt=0xadaebf0, prefix=0x0,
    URI=0xada2323 "jabber:client", line=0, nsNr=0, tlen=0) at parser.c:8794
#14 0xb7582199 in xmlParseChunk__internal_alias (ctxt=0xadaebf0,
    chunk=0xb61bf980 "somedatathatlookedlikebase64butisn'twashere"..., size=522,
    terminate=0) at parser.c:10539
#15 0xb61ac086 in jabber_parser_process ()
   from /usr/lib/purple-2/libjabber.so.0
#16 0xb61a6d95 in ?? () from /usr/lib/purple-2/libjabber.so.0
#17 0xb787bf2d in ?? () from /usr/lib/libpurple.so.0
#18 0x080a8e93 in ?? ()
#19 0xb7950c4d in g_io_unix_dispatch (source=0x20a, callback=0xa512c50,
    user_data=0xa5181d0) at /build/buildd/glib2.0-2.20.0/glib/giounix.c:162
#20 0xb7919a58 in IA__g_main_context_dispatch (context=0xa0eb078)
    at /build/buildd/glib2.0-2.20.0/glib/gmain.c:1814
#21 0xb791cfbb in g_main_context_iterate (context=0xa0eb078, block=1,
    dispatch=1, self=0xa0c13e8)
    at /build/buildd/glib2.0-2.20.0/glib/gmain.c:2448
#22 0xb791d48a in IA__g_main_loop_run (loop=0xa8909c8)
    at /build/buildd/glib2.0-2.20.0/glib/gmain.c:2656
#23 0xb7c0b5e9 in IA__gtk_main ()
#24 0x080c31ea in main ()

Revision history for this message
Shaw Terwilliger (sterwill) wrote :

You can ignore my comment with the backtrace, it's probably a libxml2 bug (not the original MSN thing).

Revision history for this message
Ricardo Pérez López (ricardo) wrote :

@Shaw:

Seems to be the same bug as mine. I opened a bug #358516 about it. Do you use Jabber accounts?

Revision history for this message
Shaw Terwilliger (sterwill) wrote :

Yes, I use Jabber via Google (both gmail account and paid apps account).

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.