gnome-control-center crashed with SIGSEGV in g_simple_async_result_complete()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-control-center-signon (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Was in the online accounts screen via System Settings.
1) Clicked add new account
2) Clicked Facebook
3) Decided not to authorize and clicked somewhere, I think it was outside the window
4) System settings crashed
lsb_release -rd
Description: Ubuntu Raring Ringtail (development branch)
Release: 13.04
gnome-control-
Installed: 1:3.6.3-0ubuntu13
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gnome-control-
ProcVersionSign
Uname: Linux 3.8.0-7-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
Date: Wed Feb 27 22:21:34 2013
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2013-02-12 (14 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130212)
MarkForUpload: True
ProcCmdline: gnome-control-
SegvAnalysis:
Segfault happened at: 0x7f9b669611e5: mov 0x28(%rbx),%rdi
PC (0x7f9b669611e5) ok
source "0x28(%rbx)" (0xaaaaaaaaaaaa
destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-control-
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
g_simple_
?? () from /usr/lib/
g_main_
Title: gnome-control-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors:
(process:2305): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed
(diodon:2031): LIBDBUSMENU-
(diodon:2031): LIBDBUSMENU-
(diodon:2031): LIBDBUSMENU-
usr_lib_
activity-
deja-dup 25.5-0ubuntu1
gnome-
gnome-
indicator-datetime 12.10.3daily13.
affects: | gnome-control-center (Ubuntu) → gnome-control-center-signon (Ubuntu) |
I tried to reproduce this but was not able to do so. It is hard to debug without debug symbols in the stack trace, but I could not find debug packages for account-plugin nor gnome-control- center- signon, so I filed bug 1135475. Once it is fixed, please try to reproduce with the debug packages installed and attach the stack trace here. Thanks!