Bug 1225900

Summary: [abrt] control-center: gtk_application_impl_before_emit(): gnome-control-center killed by SIGSEGV
Product: [Fedora] Fedora Reporter: kartochka378
Component: control-centerAssignee: Control Center Maintainer <control-center-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: control-center-maint, debarshir, fmuellner, mkasik, ofourdan, oholy, rstrode, tiagomatos
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/e5a888133fe48b243fc969eae5a1a3cfe7292d4a
Whiteboard: abrt_hash:8bba8b1eaae71fa07dd68f2b44f7523b69a9894f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 14:19:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status none

Description kartochka378 2015-05-28 12:01:24 UTC 
Description of problem:
Trying to calibrate monitor using ColorMunki Calibrator, first attempt after disabling SELinux, more info in https://bugzilla.redhat.com/show_bug.cgi?id=1225867

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

Additional info:
reporter:       libreport-2.5.1
backtrace_rating: 4
cmdline:        /usr/bin/gnome-control-center
crash_function: gtk_application_impl_before_emit
executable:     /usr/bin/gnome-control-center
global_pid:     2629
kernel:         4.0.4-301.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            42
var_log_messages: [System Logs]:\n-- Logs begin at Вт 2015-05-26 18:10:34 MSK, end at Чт 2015-05-28 14:00:52 MSK. --

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 gtk_application_impl_before_emit at gtkapplicationimpl.c:83
 #1 g_application_impl_method_call at gapplicationimpl-dbus.c:272
 #2 call_in_idle_cb at gdbusconnection.c:4884
 #6 g_main_context_iteration at gmain.c:3869
 #7 g_application_run at gapplication.c:2328
Comment 1 kartochka378 2015-05-28 12:01:28 UTC 
Created attachment 1031230 [details]
File: backtrace
Comment 2 kartochka378 2015-05-28 12:01:30 UTC 
Created attachment 1031231 [details]
File: cgroup
Comment 3 kartochka378 2015-05-28 12:01:31 UTC 
Created attachment 1031232 [details]
File: core_backtrace
Comment 4 kartochka378 2015-05-28 12:01:33 UTC 
Created attachment 1031233 [details]
File: dso_list
Comment 5 kartochka378 2015-05-28 12:01:34 UTC 
Created attachment 1031235 [details]
File: environ
Comment 6 kartochka378 2015-05-28 12:01:35 UTC 
Created attachment 1031236 [details]
File: limits
Comment 7 kartochka378 2015-05-28 12:01:38 UTC 
Created attachment 1031237 [details]
File: maps
Comment 8 kartochka378 2015-05-28 12:01:39 UTC 
Created attachment 1031238 [details]
File: mountinfo
Comment 9 kartochka378 2015-05-28 12:01:40 UTC 
Created attachment 1031239 [details]
File: namespaces
Comment 10 kartochka378 2015-05-28 12:01:41 UTC 
Created attachment 1031240 [details]
File: open_fds
Comment 11 kartochka378 2015-05-28 12:01:43 UTC 
Created attachment 1031241 [details]
File: proc_pid_status
Comment 12 Fedora End Of Life 2016-07-19 14:19:51 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.
Comment 13 Debarshi Ray 2017-06-19 14:10:13 UTC 

*** This bug has been marked as a duplicate of bug 1226229 ***