pidgin crashed with SIGSEGV in g_type_check_instance_cast()

Bug #588931 reported by Jānis Kangarooo
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: pidgin

Installed pidgin-festival plugin while pidgin was open. plugin didnt work immidiatly. after purgin and installing while closed it worked. later using it and just minimizind made pidgin unresponsive and made pidgin crash or i maybe pressed 2x close and then Yes to close it and then poped up this crash report.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: pidgin 1:2.6.6-1ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
CrashCounter: 1
Date: Wed Jun 2 21:11:18 2010
ExecutablePath: /usr/bin/pidgin
InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: pidgin
ProcCwd: /home/kng
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x677189 <g_type_check_instance_cast+41>: mov (%eax),%eax
 PC (0x00677189) ok
 source "(%eax)" (0x00000002) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 g_type_check_instance_cast ()
 ?? ()
 ?? () from /lib/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/libglib-2.0.so.0
 ?? () from /lib/libglib-2.0.so.0
Title: pidgin crashed with SIGSEGV in g_type_check_instance_cast()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Jānis Kangarooo (kangarooo) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_instance_cast ()
 ensure_plugin_visible (data=0x8d42160)
 ?? () from /lib/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/libglib-2.0.so.0
 ?? () from /lib/libglib-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in pidgin (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

However, processing it in order to get sufficient information for the developers failed (it does not generate an useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report. Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

Changed in pidgin (Ubuntu):
importance: Medium → Low
status: New → 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.