pidgin crashed with SIGSEGV in __GI___pthread_mutex_lock()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pidgin (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Crash when starting Pidgin, restart was successful. As I can't access the back-trace information I can't guess whether or not this is a duplicate of another bug.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: pidgin 1:2.10.7-0ubuntu3
ProcVersionSign
Uname: Linux 3.8.0-14-generic x86_64
ApportVersion: 2.9.2-0ubuntu4
Architecture: amd64
Date: Wed Mar 27 16:49:06 2013
ExecutablePath: /usr/bin/pidgin
InstallationDate: Installed on 2012-11-27 (120 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcCmdline: pidgin
SegvAnalysis:
Segfault happened at: 0x7f42d107ef94 <__GI__
PC (0x7f42d107ef94) ok
source "0x10(%rdi)" (0x00000081) not located in a known VMA region (needed readable region)!
destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: pidgin
StacktraceTop:
__GI__
XrmQGetResource () from /usr/lib/
XGetDefault () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: pidgin crashed with SIGSEGV in __GI___
UpgradeStatus: Upgraded to raring on 2013-03-27 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors:
(polkit-
(process:10786): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed
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 #1153369, 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.