Bug 1033793

Summary: [abrt] control-center-3.10.2-2.fc20: g_cancellable_disconnect: Process /usr/bin/gnome-control-center was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Thomas Spura <tomspur>
Component: control-centerAssignee: Control Center Maintainer <control-center-maint>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: control-center-maint, fmuellner, mkasik, ofourdan, rstrode, tiagomatos
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/4bd90a19f67346cb695a7735d65a8a1a26a78b0b
Whiteboard: abrt_hash:2c74311d1c354399a0834c7bd88668601f7ae8ec
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 13:07:11 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: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Thomas Spura 2013-11-22 22:46:19 UTC
Description of problem:
gnome-online-account crashed (see https://bugzilla.redhat.com/show_bug.cgi?id=958336) this time by reentering the passwort into the gnome-online-account window in gnome-control-center.

And gnome-control-center was taken with it...

Version-Release number of selected component:
control-center-3.10.2-2.fc20

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        gnome-control-center power
crash_function: g_cancellable_disconnect
executable:     /usr/bin/gnome-control-center
kernel:         3.11.7-300.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (4 frames)
 #0 g_cancellable_disconnect at gcancellable.c:616
 #1 ews_client_autodiscover_data_free at goaewsclient.c:100
 #5 g_main_context_iteration at gmain.c:3774
 #6 g_application_run at gapplication.c:1635

Potential duplicate: bug 1015730

Comment 1 Thomas Spura 2013-11-22 22:46:29 UTC
Created attachment 828023 [details]
File: backtrace

Comment 2 Thomas Spura 2013-11-22 22:46:33 UTC
Created attachment 828024 [details]
File: cgroup

Comment 3 Thomas Spura 2013-11-22 22:46:37 UTC
Created attachment 828025 [details]
File: core_backtrace

Comment 4 Thomas Spura 2013-11-22 22:46:42 UTC
Created attachment 828026 [details]
File: dso_list

Comment 5 Thomas Spura 2013-11-22 22:46:46 UTC
Created attachment 828027 [details]
File: environ

Comment 6 Thomas Spura 2013-11-22 22:46:50 UTC
Created attachment 828028 [details]
File: exploitable

Comment 7 Thomas Spura 2013-11-22 22:46:54 UTC
Created attachment 828029 [details]
File: limits

Comment 8 Thomas Spura 2013-11-22 22:46:59 UTC
Created attachment 828030 [details]
File: maps

Comment 9 Thomas Spura 2013-11-22 22:47:03 UTC
Created attachment 828031 [details]
File: open_fds

Comment 10 Thomas Spura 2013-11-22 22:47:07 UTC
Created attachment 828032 [details]
File: proc_pid_status

Comment 11 Thomas Spura 2013-11-22 22:47:11 UTC
Created attachment 828033 [details]
File: var_log_messages

Comment 12 Thomas Spura 2013-11-22 22:50:21 UTC
Seems like a 0x0 pointer is accessed:

#0  g_cancellable_disconnect (cancellable=0x285e540, handler_id=12117) at gcancellable.c:616
616	  while (priv->cancelled_running)

Thread 1 (Thread 0x7f0a77fdda40 (LWP 2557)):
#0  g_cancellable_disconnect (cancellable=0x285e540, handler_id=12117) at gcancellable.c:616
        priv = 0x0
#1  0x0000003ab082c9f5 in ews_client_autodiscover_data_free (user_data=0x7f0a58003b40) at goaewsclient.c:100
        data = 0x7f0a58003b40

Comment 13 Fedora End Of Life 2015-05-29 09:50:03 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 14 Fedora End Of Life 2015-06-29 13:07:11 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.