empathy-auth-client crashed with SIGSEGV in g_hash_table_iter_init()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
empathy (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I've just enabled my online accounts (facebook, gmail, yahoo mail and msn) after fresh install of ubuntu 13.04 when i open empathy didn't work, so i did a reboot and started empathy again and it did work. but then I got this error.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: empathy 3.6.3-0ubuntu2
ProcVersionSign
Uname: Linux 3.8.0-5-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
Date: Sun Feb 10 15:42:28 2013
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2013-02-09 (1 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130208)
MarkForUpload: True
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_
PATH=(custom, no user)
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x7f89dfae239a <g_hash_
PC (0x7f89dfae239a) ok
source "0x44(%rsi)" (0x100000044) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
g_hash_
ag_auth_
ag_auth_
?? () from /usr/lib/
?? () from /usr/lib/
Title: empathy-auth-client crashed with SIGSEGV in g_hash_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors:
(process:2457): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed
(polkit-
(polkit-
(process:5049): 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 #1105240, 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.