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
Created attachment 1031230 [details] File: backtrace
Created attachment 1031231 [details] File: cgroup
Created attachment 1031232 [details] File: core_backtrace
Created attachment 1031233 [details] File: dso_list
Created attachment 1031235 [details] File: environ
Created attachment 1031236 [details] File: limits
Created attachment 1031237 [details] File: maps
Created attachment 1031238 [details] File: mountinfo
Created attachment 1031239 [details] File: namespaces
Created attachment 1031240 [details] File: open_fds
Created attachment 1031241 [details] File: proc_pid_status
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.
*** This bug has been marked as a duplicate of bug 1226229 ***