pidgin crashed with SIGSEGV in __kernel_vsyscall()

Bug #341584 reported by Xavier Fung
This bug report is a duplicate of:  Bug #349009: pidgin crashed with SIGSEGV. Edit Remove
8
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: pidgin

Apport comes up and reports this error after a reboot. No apparent crash happened before, and Pidgin was not closed before rebooting.

ProblemType: Crash
Architecture: i386
Disassembly: 0x0:
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/pidgin
Package: pidgin 1:2.5.5-1ubuntu1
ProcCmdline: pidgin
ProcEnviron:
 PATH=(custom, no user)
 LANG=zh_HK.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 __kernel_vsyscall ()
 select () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
 start_thread () from /lib/tls/i686/cmov/libpthread.so.0
 clone () from /lib/tls/i686/cmov/libc.so.6
Title: pidgin crashed with SIGSEGV in __kernel_vsyscall()
Uname: Linux 2.6.28-9-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare scanner video

Revision history for this message
Xavier Fung (xavier114fch) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:__kernel_vsyscall ()
select () from /lib/tls/i686/cmov/libc.so.6
?? ()
start_thread () from /lib/tls/i686/cmov/libpthread.so.0
clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

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
Andreas Moog (ampelbein) wrote :

I think this is dupe of bug 349009, should be fixed with -ubuntu5

visibility: private → public
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.