[apport] pidgin crashed with SIGSEGV in g_hash_table_lookup()

Bug #115752 reported by Nicolas DERIVE
2
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: pidgin

Another pidgin crash, in the same conditions like the bug #115751 but the problem occurs elsewhere according to apport.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sun May 20 11:23:25 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/pidgin
Package: pidgin 1:2.0.0+dfsg.1-3ubuntu1
PackageArchitecture: i386
ProcCmdline: pidgin
ProcCwd: /home/nicolas
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 g_hash_table_lookup () from /usr/lib/libglib-2.0.so.0
 purple_presence_get_status () from /usr/lib/libpurple.so.0
 purple_prpl_got_user_status () from /usr/lib/libpurple.so.0
 msn_user_update () from /usr/lib/purple-2/libmsn.so
 ?? () from /usr/lib/purple-2/libmsn.so
Uname: Linux spiralo-vertigo 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video

Revision history for this message
Nicolas DERIVE (kalon33) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:_start () from /lib/ld-linux.so.2
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in pidgin:
importance: Undecided → Medium
Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Thank you for your bug report. Have you been able to reproduce this with an up to date Ubuntu system ?

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.