Bug 783311

Summary: [abrt] control-center-3.2.2-1.fc16: Process /usr/bin/gnome-control-center was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Javier Jardón <jjardon>
Component: control-centerAssignee: Control Center Maintainer <control-center-maint>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: control-center-maint, david.w.h.chin, mkasik, polesz, rstrode, willdavidwarren
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:8c375c872b3c8bb77e81b45e49c5389206908585
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 13:13:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: dso_list
none
File: build_ids
none
File: maps
none
File: backtrace
none
File: backtrace none

Description Javier Jardón 2012-01-19 22:36:28 UTC
libreport version: 2.0.8
abrt_version:   2.0.7
backtrace_rating: 3
cmdline:        gnome-control-center online-accounts
crash_function: goa_oauth_provider_get_callback_uri
executable:     /usr/bin/gnome-control-center
kernel:         3.1.9-1.fc16.x86_64
pid:            26930
pwd:            /home/jjardon
reason:         Process /usr/bin/gnome-control-center was killed by signal 11 (SIGSEGV)
time:           Thu 19 Jan 2012 10:29:55 PM CET
uid:            1000
username:       jjardon
var_log_messages: Jan 19 22:30:05 eregion abrt[26960]: Saved core dump of pid 26930 (/usr/bin/gnome-control-center) to /var/spool/abrt/ccpp-2012-01-19-22:29:55-26930 (1156083712 bytes)

backtrace:      Text file, 46923 bytes
build_ids:      Text file, 8118 bytes
dso_list:       Text file, 20521 bytes
maps:           Text file, 89985 bytes

environ:
:XDG_VTNR=1
:XDG_SESSION_ID=2
:HOSTNAME=eregion.lan
:IMSETTINGS_INTEGRATE_DESKTOP=yes
:SHELL=/bin/bash
:TERM=dumb
:HISTSIZE=1000
:XDG_SESSION_COOKIE=8a9ecea27e3a0b60b6727a6c0000000a-1327005258.596542-273193395
:GNOME_KEYRING_CONTROL=/tmp/keyring-NwBzdu
:IMSETTINGS_MODULE=none
:USER=jjardon
:USERNAME=jjardon
:MAIL=/var/spool/mail/jjardon
:PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/jjardon/.local/bin:/home/jjardon/bin
:DESKTOP_SESSION=gnome
:QT_IM_MODULE=xim
:PWD=/home/jjardon
:XMODIFIERS=@im=none
:GNOME_KEYRING_PID=1159
:LANG=en_US.UTF-8
:GDMSESSION=gnome
:HISTCONTROL=ignoredups
:HOME=/home/jjardon
:XDG_SEAT=seat0
:SHLVL=1
:LOGNAME=jjardon
:DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-Gm53rPNFsf,guid=7e97bb7a0d2a5b10e2a167d300000020
:'LESSOPEN=||/usr/bin/lesspipe.sh %s'
:WINDOWPATH=1
:XDG_RUNTIME_DIR=/run/user/jjardon
:DISPLAY=:0
:XAUTHORITY=/var/run/gdm/auth-for-jjardon-ONuesZ/database
:_=/usr/bin/gnome-session
:GNOME_DESKTOP_SESSION_ID=this-is-deprecated
:SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1164,unix/unix:/tmp/.ICE-unix/1164
:GPG_AGENT_INFO=/tmp/keyring-NwBzdu/gpg:0:1
:SSH_AUTH_SOCK=/tmp/keyring-NwBzdu/ssh
:GJS_DEBUG_OUTPUT=stderr
:'GJS_DEBUG_TOPICS=JS ERROR;JS LOG'
:GIO_LAUNCHED_DESKTOP_FILE=/usr/share/applications/gnome-contacts.desktop
:GIO_LAUNCHED_DESKTOP_FILE_PID=26913

Comment 1 Javier Jardón 2012-01-19 22:36:32 UTC
Created attachment 556405 [details]
File: dso_list

Comment 2 Javier Jardón 2012-01-19 22:36:34 UTC
Created attachment 556406 [details]
File: build_ids

Comment 3 Javier Jardón 2012-01-19 22:36:39 UTC
Created attachment 556407 [details]
File: maps

Comment 4 Javier Jardón 2012-01-19 22:36:42 UTC
Created attachment 556408 [details]
File: backtrace

Comment 5 Will Warren 2012-02-12 14:33:13 UTC
Package: control-center-3.2.1-2.fc16
Architecture: i686
OS Release: Fedora release 16 (Verne)

Comment
-----
I added an online account (Google). I was able to authorize no problem, but then when I was finished, the online accounts window froze, then it disappeared, and then this crash happened

Comment 6 Gergely POLONKAI 2012-04-09 23:17:33 UTC
I have just granted access to a third Google account

backtrace_rating: 4
Package: control-center-3.2.2-1.fc16
Architecture: i686
OS Release: Fedora release 16 (Verne)

Comment 7 Gergely POLONKAI 2012-04-09 23:17:38 UTC
Created attachment 576327 [details]
File: backtrace

Comment 8 Alexey 2012-08-18 10:54:42 UTC
Try grant acces to google account

backtrace_rating: 4
Package: control-center-3.2.3-1.fc16
Architecture: i686
OS Release: Fedora release 16 (Verne)

Comment 9 Fedora End Of Life 2013-01-16 12:43:21 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 10 Fedora End Of Life 2013-02-13 13:13:49 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.