Bug 1043155

Summary: [abrt] control-center-3.10.2-3.fc20: ap_activated: Process /usr/bin/gnome-control-center was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Jacek Pliszka <Jacek.Pliszka>
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: abhijit4daksh, control-center-maint, fmuellner, mcatanzaro+wrong-account-do-not-cc, mkasik, ofourdan, pacheco_20, pratyush.a.sahay, rajgfx, rstrode, thomas, tiagomatos, tomspur
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/8bbb0bacc52d015d42904393a69884bf7d05518c
Whiteboard: abrt_hash:9e8a99526aa578b09108c547baf8843c4a12e388
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 13:31:14 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 Jacek Pliszka 2013-12-14 11:24:10 UTC
Description of problem:
HArd to tell, I was turning off Wifi in my notebook.

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

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        gnome-control-center network show-device /org/freedesktop/NetworkManager/Devices/1
crash_function: ap_activated
executable:     /usr/bin/gnome-control-center
kernel:         3.11.10-301.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 ap_activated at net-device-wifi.c:1918
 #1 g_cclosure_marshal_VOID__OBJECTv at gmarshal.c:1312
 #2 _g_closure_invoke_va at gclosure.c:840
 #5 gtk_list_box_real_button_release_event at /lib64/libgtk-3.so.0
 #6 _gtk_marshal_BOOLEAN__BOXEDv at /lib64/libgtk-3.so.0
 #7 _g_closure_invoke_va at gclosure.c:840
 #10 gtk_widget_event_internal at /lib64/libgtk-3.so.0
 #11 propagate_event at /lib64/libgtk-3.so.0
 #12 gtk_main_do_event at /lib64/libgtk-3.so.0
 #13 gdk_event_source_dispatch at /lib64/libgdk-3.so.0

Potential duplicate: bug 957323

Comment 1 Jacek Pliszka 2013-12-14 11:24:16 UTC
Created attachment 836631 [details]
File: backtrace

Comment 2 Jacek Pliszka 2013-12-14 11:24:18 UTC
Created attachment 836632 [details]
File: cgroup

Comment 3 Jacek Pliszka 2013-12-14 11:24:20 UTC
Created attachment 836633 [details]
File: core_backtrace

Comment 4 Jacek Pliszka 2013-12-14 11:24:22 UTC
Created attachment 836634 [details]
File: dso_list

Comment 5 Jacek Pliszka 2013-12-14 11:24:24 UTC
Created attachment 836635 [details]
File: environ

Comment 6 Jacek Pliszka 2013-12-14 11:24:26 UTC
Created attachment 836636 [details]
File: exploitable

Comment 7 Jacek Pliszka 2013-12-14 11:24:28 UTC
Created attachment 836637 [details]
File: limits

Comment 8 Jacek Pliszka 2013-12-14 11:24:30 UTC
Created attachment 836638 [details]
File: maps

Comment 9 Jacek Pliszka 2013-12-14 11:24:32 UTC
Created attachment 836639 [details]
File: open_fds

Comment 10 Jacek Pliszka 2013-12-14 11:24:34 UTC
Created attachment 836641 [details]
File: proc_pid_status

Comment 11 Jacek Pliszka 2013-12-14 11:24:36 UTC
Created attachment 836642 [details]
File: var_log_messages

Comment 12 Thomas Spura 2014-04-05 17:02:56 UTC
My steps to produce this issue:
- Trying to connect a network, but DHCP wasn't working for whatever reasons.
- I killed the wifi with the hardware switch as NM wasn't giving up fast enough.
- The control-center still showed, that it is trying to connect to the network.
- I clicked to another access point just to see if "selecting another network" is working.
---> see the crash

Comment 13 Fedora End Of Life 2015-05-29 09:59:26 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:31:14 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.