Hide Forgot
Description of problem: Calibrate the colour of a display twice. If the first calibration fails, calibrating again results in a segfault. Version-Release number of selected component: 1:control-center-3.26.2-2.fc27 Additional info: reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: gnome-control-center --overview crash_function: gcm_prefs_calib_apply_cb executable: /usr/bin/gnome-control-center journald_cursor: s=adcb9d893ee94929adfd307ad85ee786;i=6c85f3;b=6d3cff70dc2e45a0aa0fa50b6212de25;m=860e37e51d;t=569cbf2efe731;x=404e627378cfabf8 kernel: 4.15.13-300.fc27.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gcm_prefs_calib_apply_cb at cc-color-panel.c:316 #5 on_assistant_apply at gtkassistant.c:1062 #6 _g_closure_invoke_va at gclosure.c:867 #9 gtk_button_do_release at gtkbutton.c:1843 #10 gtk_real_button_released at gtkbutton.c:1961 #11 _g_closure_invoke_va at gclosure.c:867 #14 multipress_released_cb at gtkbutton.c:666 #15 ffi_call_unix64 at ../src/x86/unix64.S:76 #16 ffi_call at ../src/x86/ffi64.c:525 #17 g_cclosure_marshal_generic_va at gclosure.c:1604
Created attachment 1421743 [details] File: backtrace
Created attachment 1421744 [details] File: cgroup
Created attachment 1421745 [details] File: core_backtrace
Created attachment 1421746 [details] File: cpuinfo
Created attachment 1421747 [details] File: dso_list
Created attachment 1421748 [details] File: environ
Created attachment 1421749 [details] File: exploitable
Created attachment 1421750 [details] File: limits
Created attachment 1421751 [details] File: maps
Created attachment 1421752 [details] File: mountinfo
Created attachment 1421753 [details] File: open_fds
Created attachment 1421754 [details] File: proc_pid_status
Similar problem has been detected: After the first attempt to calibrate the colours on my laptop monitor failed I tried to start calibration again. The first test was the medium calibration, the second test (which caused this crash) was the short calibration. I'm using an Gretag-Macbeth AG Eye-One display i1 calibration device reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: gnome-control-center color crash_function: gcm_prefs_calib_apply_cb executable: /usr/bin/gnome-control-center journald_cursor: s=1c4b08b4442343f989767af9606fdbe0;i=fc87;b=936b2e4863074d849912406057066225;m=bd521636;t=56a6bfb8e49cc;x=72aa0b83167b5e6f kernel: 4.15.17-300.fc27.x86_64 package: 1:control-center-3.26.2-2.fc27 reason: gnome-control-center killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1026
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.