pidgin crashed with SIGSEGV in g_type_check_instance_cast()

Bug #1056419 reported by Mathieu Marquer
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Opening a contact in the contact list.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: pidgin 1:2.10.6-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Tue Sep 25 21:53:16 2012
ExecutablePath: /usr/bin/pidgin
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
ProcCmdline: pidgin
ProcEnviron:
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f141f9c2e8c <g_type_check_instance_cast+28>: mov (%rax),%rbp
 PC (0x7f141f9c2e8c) ok
 source "(%rax)" (0x700000008) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libdbusmenu-gtk.so.4
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: pidgin crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Mathieu Marquer (slasher-fun) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceSource:
 #0 g_type_check_instance_cast (type_instance=0x7f1424aae6a0, iface_type=139724489684304) at /build/buildd/glib2.0-2.33.14/./gobject/gtype.c:3997
   [Error: /build/buildd/glib2.0-2.33.14/./gobject/gtype.c was not found in source tree]
 #1 0x00007f140262dcbb in ?? ()
 #2 0x0000000000000000 in ?? ()
StacktraceTop:
 g_type_check_instance_cast (type_instance=0x7f1424aae6a0, iface_type=139724489684304) at /build/buildd/glib2.0-2.33.14/./gobject/gtype.c:3997
 ?? ()
 ?? ()

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):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libgtk2.0-0 version 2.24.13-0ubuntu1 required, but 2.24.13-0ubuntu2 is available
outdated debug symbol package for libcdparanoia0: package version 3.10.2+debian-11 dbgsym version 3.10.2+debian-10ubuntu1
outdated debug symbol package for libjack-jackd2-0: package version 1.9.8~dfsg.4+20120529git007cdc37-2ubuntu1 dbgsym version 1.9.8~dfsg.1-1ubuntu1
libglib2.0-0 version 2.33.14-1 required, but 2.33.14-1ubuntu2 is available
libglib2.0-data version 2.33.14-1 required, but 2.33.14-1ubuntu2 is available
libgtk2.0-bin version 2.24.13-0ubuntu1 required, but 2.24.13-0ubuntu2 is available
outdated debug symbol package for initscripts: package version 2.88dsf-13.10ubuntu13 dbgsym version 2.88dsf-13.10ubuntu11.1
libgtk2.0-common version 2.24.13-0ubuntu1 required, but 2.24.13-0ubuntu2 is available
outdated debug symbol package for libtxc-dxtn-s2tc0: package version 0~git20110809-3 dbgsym version 0~git20110809-2.1

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!

tags: removed: need-amd64-retrace
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.