pidgin crashed with SIGSEGV in g_slice_alloc()

Bug #162547 reported by Jaakan Shorter
18
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: pidgin

i was using it and it just crashed

ProblemType: Crash
Architecture: amd64
Date: Tue Nov 13 19:19:20 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: nvidia cdrom
Package: pidgin 1:2.2.1-1ubuntu4
PackageArchitecture: amd64
ProcCmdline: pidgin
ProcCwd: /home/jaakan
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 ?? () from /usr/lib/libglib-2.0.so.0
 g_slice_alloc () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/libglib-2.0.so.0
 g_hash_table_insert ()
 ?? () from /usr/lib/libpurple.so.0
Title: pidgin crashed with SIGSEGV in g_slice_alloc()
Uname: Linux AMD64 2.6.22-14-generic #1 SMP Sun Oct 14 21:45:15 GMT 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video

Tags: apport-crash
Revision history for this message
Jaakan Shorter (jaakanshorter) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:IA__g_slice_alloc (mem_size=32)
g_hash_node_new (key=0xfa68, value=0x0, key_hash=18096080)
IA__g_hash_table_insert (hash_table=0x6c9880, key=0xfa68,
new_node (name=0x2ae39050f66e "contact", type=XMLNODE_TYPE_TAG)
purple_blist_sync () at ../../libpurple/blist.c:185

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
Pedro Fragoso (ember) 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? 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.