Bug 969784 - [abrt] control-center-3.8.2-1.fc19: type_to_string: Process /usr/bin/gnome-control-center was killed by signal 6 (SIGABRT)
Summary: [abrt] control-center-3.8.2-1.fc19: type_to_string: Process /usr/bin/gnome-co...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: control-center
Version: 19
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Control Center Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:6777cf3f482f779bd2d446f233a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-02 11:08 UTC by Vadim Rutkovsky
Modified: 2015-02-17 15:25 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 15:25:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (48.15 KB, text/plain)
2013-06-02 11:08 UTC, Vadim Rutkovsky
no flags Details
File: cgroup (140 bytes, text/plain)
2013-06-02 11:08 UTC, Vadim Rutkovsky
no flags Details
File: core_backtrace (4.72 KB, text/plain)
2013-06-02 11:08 UTC, Vadim Rutkovsky
no flags Details
File: dso_list (40.16 KB, text/plain)
2013-06-02 11:08 UTC, Vadim Rutkovsky
no flags Details
File: environ (1.71 KB, text/plain)
2013-06-02 11:08 UTC, Vadim Rutkovsky
no flags Details
File: limits (1.29 KB, text/plain)
2013-06-02 11:08 UTC, Vadim Rutkovsky
no flags Details
File: maps (143.21 KB, text/plain)
2013-06-02 11:08 UTC, Vadim Rutkovsky
no flags Details
File: open_fds (3.11 KB, text/plain)
2013-06-02 11:08 UTC, Vadim Rutkovsky
no flags Details
File: proc_pid_status (944 bytes, text/plain)
2013-06-02 11:08 UTC, Vadim Rutkovsky
no flags Details
File: var_log_messages (10.40 KB, text/plain)
2013-06-02 11:08 UTC, Vadim Rutkovsky
no flags Details

Description Vadim Rutkovsky 2013-06-02 11:08:14 UTC
Description of problem:
F18->F19 update, 'Network' component crashes

Version-Release number of selected component:
control-center-3.8.2-1.fc19

Additional info:
reporter:       libreport-2.1.4
backtrace_rating: 4
cmdline:        gnome-control-center --overview
crash_function: type_to_string
executable:     /usr/bin/gnome-control-center
kernel:         3.9.4-300.fc19.x86_64
runlevel:       N 5
uid:            1001
xsession_errors: 

Truncated backtrace:
Thread no. 1 (10 frames)
 #3 type_to_string at rfkill-glib.c:83
 #4 cc_rfkill_glib_open at rfkill-glib.c:232
 #5 cc_network_panel_constructed at cc-network-panel.c:362
 #7 g_object_new_valist at gobject.c:1836
 #9 cc_panel_loader_load_by_name at cc-panel-loader.c:213
 #10 activate_panel at cc-window.c:151
 #11 cc_window_set_active_panel_from_id at cc-window.c:998
 #12 ffi_call_unix64 at ../src/x86/unix64.S:76
 #13 ffi_call at ../src/x86/ffi64.c:522
 #14 g_cclosure_marshal_generic at gclosure.c:1454

Comment 1 Vadim Rutkovsky 2013-06-02 11:08:18 UTC
Created attachment 755829 [details]
File: backtrace

Comment 2 Vadim Rutkovsky 2013-06-02 11:08:22 UTC
Created attachment 755830 [details]
File: cgroup

Comment 3 Vadim Rutkovsky 2013-06-02 11:08:25 UTC
Created attachment 755831 [details]
File: core_backtrace

Comment 4 Vadim Rutkovsky 2013-06-02 11:08:29 UTC
Created attachment 755832 [details]
File: dso_list

Comment 5 Vadim Rutkovsky 2013-06-02 11:08:33 UTC
Created attachment 755833 [details]
File: environ

Comment 6 Vadim Rutkovsky 2013-06-02 11:08:36 UTC
Created attachment 755834 [details]
File: limits

Comment 7 Vadim Rutkovsky 2013-06-02 11:08:41 UTC
Created attachment 755835 [details]
File: maps

Comment 8 Vadim Rutkovsky 2013-06-02 11:08:44 UTC
Created attachment 755836 [details]
File: open_fds

Comment 9 Vadim Rutkovsky 2013-06-02 11:08:48 UTC
Created attachment 755837 [details]
File: proc_pid_status

Comment 10 Vadim Rutkovsky 2013-06-02 11:08:52 UTC
Created attachment 755838 [details]
File: var_log_messages

Comment 11 Juan A. Burgos 2013-06-03 16:35:40 UTC
This is commit that solves this problem.

https://mail.gnome.org/archives/commits-list/2013-May/msg04543.html


Network Control Center crash in machines with a new kernel rfkill type.

network-cc-panel:ERROR:rfkill-glib.c:83:type_to_string: code should not be reached

loosely related to https://bugzilla.redhat.com/show_bug.cgi?id=968611

perhaps is related to this issue too: 

https://lkml.org/lkml/2013/5/27/386

Comment 12 Fedora End Of Life 2015-01-09 18:17:53 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 13 Fedora End Of Life 2015-02-17 15:25:35 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.