pidgin crashed with SIGSEGV in xmlParseElement()

Bug #358949 reported by Copernicvs
6
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Binary package hint: pidgin

jaunty 2.6.28-11
pidgin 2.5.5-1

loading the contact list (probably on either connecting to gtalk or msn) crashes the program at startup

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: nvidia
Package: pidgin 1:2.5.5-1ubuntu8
ProcCmdline: pidgin
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_HK.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 ?? () from /usr/lib/nss/libfreebl3.so
 ?? () from /usr/lib/libxml2.so.2
 ?? () from /usr/lib/libxml2.so.2
 xmlParseElement () from /usr/lib/libxml2.so.2
 xmlParseDocument () from /usr/lib/libxml2.so.2
Title: pidgin crashed with SIGSEGV in xmlParseElement()
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev video

Revision history for this message
Copernicvs (kornenator) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:ec_points_mul (params=0xb5cbc330, k1=0xb5cbc920,
?? () from /usr/lib/libxml2.so.2
?? () from /usr/lib/libxml2.so.2
xmlParseElement () from /usr/lib/libxml2.so.2
xmlParseDocument () from /usr/lib/libxml2.so.2

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in pidgin (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Sebastien Bacher (seb128) wrote :

do you still get the issue?

Revision history for this message
Copernicvs (kornenator) wrote : Re: [Bug 358949] Re: pidgin crashed with SIGSEGV in xmlParseElement()

not really. when the 9.40RC came out, i did a clean install of the 64bit
version, and pidgin also seems to work fine now. it was xmms (gtalk) by
the way, but now it's fine.

On Wed, 2009-04-29 at 22:06 +0000, Sebastien Bacher wrote:
> do you still get the issue?
>

visibility: private → public
Changed in pidgin (Ubuntu):
status: New → Triaged
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.