Bug 1035801

Created attachment 830246 [details]
File: backtrace

Created attachment 830247 [details]
File: cgroup

Created attachment 830248 [details]
File: core_backtrace

Created attachment 830249 [details]
File: dso_list

Created attachment 830250 [details]
File: environ

Created attachment 830251 [details]
File: limits

Created attachment 830252 [details]
File: maps

Created attachment 830253 [details]
File: open_fds

Created attachment 830254 [details]
File: proc_pid_status

Created attachment 830255 [details]
File: var_log_messages

tried to use all setings/sharing in f20 gnome3.10.2 fully updated and it crashed

got this bug today

Steps to reproduce:
1. open G-C-C
2. Open Share
3. disable share (right-top button)

100% reproduce

Proposed as a Blocker for 20-final by Fedora user ignatenkobrain using the blocker tracking app because:

 Default application functionality 
All applications that can be launched using the standard graphical mechanism of a release-blocking desktop after a default installation of that desktop must start successfully and withstand a basic functionality test. 

Sharing is basic functionality I think.

I think this: https://git.gnome.org/browse/gnome-control-center/commit/panels/sharing/cc-sharing-panel.c?id=70a4183168604b22f830a7541e3cdeb5479642f1 need to be imported

(In reply to Igor Gnatenko from comment #13)
> Steps to reproduce:
> 1. open G-C-C
> 2. Open Share
> 3. disable share (right-top button)
> 
> 100% reproduce

I can reproduce this, crashes.

Discussed in 2013-12-09 Blocker Review meeting [1]. Voted as a RejectedBlocker and a AcceptedFreezeException. It's rejected as a blocker because this is considered beyond 'basic functionality', but accepted as an FE as the fix looks straightforward and would avoid a potential crasher bug in lives.

[1] http://meetbot.fedoraproject.org/fedora-blocker-review/2013-12-09/

I was trying to toggle the Sharing button

reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        gnome-control-center --overview
crash_function: _g_log_abort
executable:     /usr/bin/gnome-control-center
kernel:         3.11.9-300.fc20.i686+PAE
package:        control-center-3.10.2-2.fc20
reason:         Process /usr/bin/gnome-control-center was killed by signal 6 (SIGABRT)
runlevel:       N 5
type:           CCpp
uid:            1000

Another user experienced a similar problem:

When you turn off sharing control-center falls

reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        gnome-control-center --overview
crash_function: _g_log_abort
executable:     /usr/bin/gnome-control-center
kernel:         3.12.5-302.fc20.x86_64
package:        control-center-3.10.2-3.fc20
reason:         gnome-control-center killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000

Fixed by 

https://git.gnome.org/browse/gnome-control-center/commit/?h=gnome-3-10&id=f5ec0cd8d6e41628d8a6663f448988aeec2885a2

Did this fix ever get released?

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.

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.