Bug 1007572 - [abrt] gnome-initial-setup-0.12-7.fc20: goa_panel_add_account_dialog_get_account: Process /usr/libexec/gnome-initial-setup was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnome-initial-setup-0.12-7.fc20: goa_panel_add_account_dialog_get_acco...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-initial-setup
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:7249ccb3a4687f47e4f3e24e741...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-12 19:02 UTC by Onuralp SEZER
Modified: 2015-06-29 12:22 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-29 12:22:06 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (57.14 KB, text/plain)
2013-09-12 19:02 UTC, Onuralp SEZER
no flags Details
File: cgroup (159 bytes, text/plain)
2013-09-12 19:03 UTC, Onuralp SEZER
no flags Details
File: core_backtrace (44.12 KB, text/plain)
2013-09-12 19:03 UTC, Onuralp SEZER
no flags Details
File: dso_list (30.19 KB, text/plain)
2013-09-12 19:03 UTC, Onuralp SEZER
no flags Details
File: environ (1.29 KB, text/plain)
2013-09-12 19:03 UTC, Onuralp SEZER
no flags Details
File: exploitable (82 bytes, text/plain)
2013-09-12 19:03 UTC, Onuralp SEZER
no flags Details
File: limits (1.29 KB, text/plain)
2013-09-12 19:03 UTC, Onuralp SEZER
no flags Details
File: maps (116.41 KB, text/plain)
2013-09-12 19:03 UTC, Onuralp SEZER
no flags Details
File: open_fds (2.16 KB, text/plain)
2013-09-12 19:03 UTC, Onuralp SEZER
no flags Details
File: proc_pid_status (939 bytes, text/plain)
2013-09-12 19:03 UTC, Onuralp SEZER
no flags Details

Description Onuralp SEZER 2013-09-12 19:02:51 UTC
Description of problem:
After install I was adding my social account and then It's close and crashed

Version-Release number of selected component:
gnome-initial-setup-0.12-7.fc20

Additional info:
reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        /usr/libexec/gnome-initial-setup
crash_function: goa_panel_add_account_dialog_get_account
executable:     /usr/libexec/gnome-initial-setup
kernel:         3.11.0-300.fc20.x86_64
runlevel:       N 5
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 goa_panel_add_account_dialog_get_account at cc-online-accounts-add-account-dialog.c:360
 #1 show_online_account_dialog at gis-goa-page.c:117
 #2 _g_closure_invoke_va at gclosure.c:840
 #5 gtk_real_button_released at gtkbutton.c:2101
 #10 gtk_button_button_release at gtkbutton.c:1933
 #11 _gtk_marshal_BOOLEAN__BOXEDv at gtkmarshalers.c:130
 #12 _g_closure_invoke_va at gclosure.c:840
 #15 gtk_widget_event_internal at gtkwidget.c:7146
 #16 gtk_widget_event at gtkwidget.c:6808
 #17 propagate_event_up at gtkmain.c:2392

Comment 1 Onuralp SEZER 2013-09-12 19:02:58 UTC
Created attachment 796978 [details]
File: backtrace

Comment 2 Onuralp SEZER 2013-09-12 19:03:02 UTC
Created attachment 796979 [details]
File: cgroup

Comment 3 Onuralp SEZER 2013-09-12 19:03:06 UTC
Created attachment 796980 [details]
File: core_backtrace

Comment 4 Onuralp SEZER 2013-09-12 19:03:11 UTC
Created attachment 796981 [details]
File: dso_list

Comment 5 Onuralp SEZER 2013-09-12 19:03:14 UTC
Created attachment 796982 [details]
File: environ

Comment 6 Onuralp SEZER 2013-09-12 19:03:18 UTC
Created attachment 796983 [details]
File: exploitable

Comment 7 Onuralp SEZER 2013-09-12 19:03:22 UTC
Created attachment 796984 [details]
File: limits

Comment 8 Onuralp SEZER 2013-09-12 19:03:28 UTC
Created attachment 796985 [details]
File: maps

Comment 9 Onuralp SEZER 2013-09-12 19:03:31 UTC
Created attachment 796986 [details]
File: open_fds

Comment 10 Onuralp SEZER 2013-09-12 19:03:52 UTC
Created attachment 796987 [details]
File: proc_pid_status

Comment 11 Onuralp SEZER 2013-09-14 13:11:09 UTC
Because crash It's pop-up again on next reboot and I just click "next" to the end after help menu that's crash again.

Comment 12 Alexander van Loon 2013-11-10 09:24:19 UTC
I encountered this bug in the Fedora 20 alpha too. I tried to add a Flickr account in GNOME's initial setup, signed in for Flickr and then it suddenly crashed.

Comment 14 Fedora End Of Life 2015-05-29 09:23:46 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 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  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 15 Fedora End Of Life 2015-06-29 12:22:06 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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


Note You need to log in before you can comment on or make changes to this bug.