Bug 1213179 - [abrt] control-center: gtk_widget_destroy(): gnome-control-center killed by SIGSEGV
Summary: [abrt] control-center: gtk_widget_destroy(): gnome-control-center killed by S...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: control-center
Version: 22
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Control Center Maintainer
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:6517055d41a6872a9ab09babcf7...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-19 20:46 UTC by Niko
Modified: 2016-07-19 13:46 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-07-19 13:46:54 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (30.39 KB, text/plain)
2015-04-19 20:46 UTC, Niko
no flags Details
File: cgroup (190 bytes, text/plain)
2015-04-19 20:46 UTC, Niko
no flags Details
File: core_backtrace (6.98 KB, text/plain)
2015-04-19 20:46 UTC, Niko
no flags Details
File: dso_list (27.28 KB, text/plain)
2015-04-19 20:46 UTC, Niko
no flags Details
File: environ (1.66 KB, text/plain)
2015-04-19 20:46 UTC, Niko
no flags Details
File: limits (1.29 KB, text/plain)
2015-04-19 20:46 UTC, Niko
no flags Details
File: maps (124.29 KB, text/plain)
2015-04-19 20:46 UTC, Niko
no flags Details
File: open_fds (1.43 KB, text/plain)
2015-04-19 20:46 UTC, Niko
no flags Details
File: proc_pid_status (963 bytes, text/plain)
2015-04-19 20:46 UTC, Niko
no flags Details
File: var_log_messages (3.23 KB, text/plain)
2015-04-19 20:46 UTC, Niko
no flags Details

Description Niko 2015-04-19 20:46:20 UTC
Description of problem:
Tried to connect to bluetooth mouse

Version-Release number of selected component:
control-center-3.15.90-1.fc22

Additional info:
reporter:       libreport-2.4.0
backtrace_rating: 4
cmdline:        gnome-control-center bluetooth
crash_function: gtk_widget_destroy
executable:     /usr/bin/gnome-control-center
kernel:         4.0.0-0.rc1.git0.1.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (6 frames)
 #0 gtk_widget_destroy at gtkwidget.c:4791
 #1 create_callback at bluetooth-settings-widget.c:823
 #2 g_simple_async_result_complete at gsimpleasyncresult.c:763
 #3 complete_in_idle_cb at gsimpleasyncresult.c:775
 #7 g_main_context_iteration at gmain.c:3869
 #8 g_application_run at gapplication.c:2289

Comment 1 Niko 2015-04-19 20:46:24 UTC
Created attachment 1016142 [details]
File: backtrace

Comment 2 Niko 2015-04-19 20:46:26 UTC
Created attachment 1016143 [details]
File: cgroup

Comment 3 Niko 2015-04-19 20:46:29 UTC
Created attachment 1016144 [details]
File: core_backtrace

Comment 4 Niko 2015-04-19 20:46:32 UTC
Created attachment 1016145 [details]
File: dso_list

Comment 5 Niko 2015-04-19 20:46:34 UTC
Created attachment 1016146 [details]
File: environ

Comment 6 Niko 2015-04-19 20:46:35 UTC
Created attachment 1016147 [details]
File: limits

Comment 7 Niko 2015-04-19 20:46:40 UTC
Created attachment 1016148 [details]
File: maps

Comment 8 Niko 2015-04-19 20:46:42 UTC
Created attachment 1016149 [details]
File: open_fds

Comment 9 Niko 2015-04-19 20:46:43 UTC
Created attachment 1016150 [details]
File: proc_pid_status

Comment 10 Niko 2015-04-19 20:46:45 UTC
Created attachment 1016151 [details]
File: var_log_messages

Comment 11 Fedora End Of Life 2016-07-19 13:46:54 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.