pidgin crashed with SIGSEGV in g_type_check_instance_cast()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pidgin (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Pidgin reliably crashes when I try to connect to an IRC network. This is a recent regression in 12.10; it happened around the time I updated to libgtk-3-0 3.5.18-0ubuntu3 and libglib2.0-0 2.33.14-1.
To reproduce:
0) Make sure pidgin is configured to connect to an IRC network such as freenode.net
1) Launch pidgin
2) Set the connection status for the connection from "Offline" to "Online"
Expected results:
Pidgin connects to the IRC network and opens channels for which you're set to autojoin
Actual results:
Pidgin crashes
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: pidgin 1:2.10.6-0ubuntu2
ProcVersionSign
Uname: Linux 3.5.0-15-generic x86_64
NonfreeKernelMo
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
Date: Mon Sep 24 10:01:10 2012
ExecutablePath: /usr/bin/pidgin
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
ProcCmdline: pidgin
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f295a076e8c <g_type_
PC (0x7f295a076e8c) 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_
?? () from /usr/lib/
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
g_signal_
Title: pidgin crashed with SIGSEGV in g_type_
UpgradeStatus: Upgraded to quantal on 2012-08-07 (47 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
(telepathy-
(telepathy-
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1053944, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.