gnome-control-center crashed with SIGSEGV in g_simple_async_result_complete()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-control-center (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Opened Online Accounts settings. Tried to add Facebook account but then just before entering login details I've pressed cancel (just didn't feel like doing it at this time). Window closed and the crash happened.
Just for the record: I am unable to make Online accounts to work at all (tried google and facebook). Empathy says that they need authorisation all the time and never goes online. Was working fine on 12.10.
Thx
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gnome-control-
ProcVersionSign
Uname: Linux 3.8.0-13-generic x86_64
ApportVersion: 2.9.2-0ubuntu1
Architecture: amd64
Date: Wed Mar 20 12:34:42 2013
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2013-03-19 (0 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130318)
MarkForUpload: True
ProcCmdline: gnome-control-
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_
PATH=(custom, no user)
LANGUAGE=en_GB:en
LANG=en_GB.UTF-8
SegvAnalysis:
Segfault happened at: 0x7f2c7a2d1410: movl $0x0,0x44(%rax)
PC (0x7f2c7a2d1410) ok
source "$0x0" ok
destination "0x44(%rax)" (0xaaaaaaaaaaaa
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-control-
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
g_simple_
?? () from /usr/lib/
g_simple_
Title: gnome-control-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
usr_lib_
activity-
deja-dup 25.5-0ubuntu1
gnome-
gnome-
indicator-datetime 12.10.3daily13.
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 #1157559, 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.