gnome-control-center crashed with SIGSEGV in ap_plugin_set_user_cancelled()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-control-center (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
After upgrading to Saucy (~Beta1 Sept 2, 2012), I loaded evolution and tested my Google online contacts/
On next reboot, I received a notification to check my Online accounts for authentication.
I proceeded to the Online Accounts... and and selected the pending "Grant Access" for my Google account (only online account setup on this computer).
I received some sort of response-reply error from Google; I didn't capture it. There was no way to move forwards, because Google did not present the password dialogue, but instead this error message. I hit the 'Cancel' button (the only button) and then apport generated this crash report.
A subsequent attempt to go in and grant access was sucessful; I actually did not even need to enter my password, so I guess my existing/stored session/
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-control-
ProcVersionSign
Uname: Linux 3.11.0-4-generic x86_64
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
Date: Tue Sep 3 20:37:11 2013
ExecutablePath: /usr/bin/
MarkForUpload: True
ProcCmdline: gnome-control-
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_
PATH=(custom, no user)
LANGUAGE=en_US
LANG=en_US.utf8
SegvAnalysis:
Segfault happened at: 0x7fac76f3ca1d <ap_plugin_
PC (0x7fac76f3ca1d) ok
source "%rax" ok
destination "(%rdx)" (0xaaaaaaaaaaaa
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-control-
StacktraceTop:
ap_plugin_
?? () from /usr/lib/
g_simple_
?? () from /usr/lib/
g_simple_
Title: gnome-control-
UpgradeStatus: Upgraded to saucy on 2013-09-03 (0 days ago)
UserGroups: adm admin cdrom dialout dip disk fax fuse kismet libvirtd lpadmin mythtv netdev plugdev pulse pulse-access sambashare scanner tape vboxusers vde2-net video
usr_lib_
activity-
deja-dup 27.3.1-0ubuntu1
gnome-
gnome-
gnome-
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 #1197998, 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.