Bug 1140353 - gnome control center fails to calibrate the screen
Summary: gnome control center fails to calibrate the screen
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: colord
Version: 22
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Control Center Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-10 18:01 UTC by Pavel Malyshev
Modified: 2016-07-19 19:30 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-07-19 19:30:22 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Pavel Malyshev 2014-09-10 18:01:33 UTC
Description of problem:

I use Spyder4Pro to calibrate the screen.
dispcalGUI detects the device and performs the calibration, but I'm not really satisfied with results, so I try to calibrate the screen with Gnome Control Center.

After few questions Control Center requests to put device on the screen and press "Start" button.
When I press "Start" the following message is displayed:
--------------------------------------
Calibration failed!
An internal error occured that could not be recovered.
You can remove the calibration device.
--------------------------------------

JournalCtl shows these messages:
--------------------------------------
сен 10 21:24:43 kelly.ddns.int.prhv.afunix.org colord[2801]: (colord:2801): Cd-WARNING **: the child exited with return code 1
сен 10 21:24:43 kelly.ddns.int.prhv.afunix.org gnome-session[3054]: (gnome-control-center:15514): color-cc-panel-WARNING **: calibration failed with code 1: spotread exited unexpectedly
сен 10 21:24:43 kelly.ddns.int.prhv.afunix.org colord[2801]: (colord:2801): Cd-WARNING **: no child pid to kill!
--------------------------------------

Abrt does not report anything. No SegFault in the log.


Version-Release number of selected component (if applicable):

Not sure which package might cause the issue

gnome-color-manager-3.10.1-2.fc20.x86_64
control-center-3.10.3-2.fc20.x86_64
dispcalGUI-2.5.0.0-221.1
argyllcms-1.6.3-1.fc20.x86_64
How reproducible:


Steps to Reproduce:
1. Connect Spyder4Pro
2. Check that dispcalGUI detects the device
3. Open Control Center
4. Choose "Color"
5. Click on a device from the list and press "Calibrate" button
6. Choose calibration quality (I've tried all of them)
7. Choose display type (I have LCD, so this is the only option I've tried)
8. Choose whitepoint profile (I've tried "Native to display" and "D65")
9. Confirm brightness with "Continue" button
10. Click "Apply" to confirm profile name
11. Place device on the screen and confirm pressing "Start" button

Actual results:

Calibration fails

Expected results:

Calibration starts and finishes successfully.

Additional info:
Sometimes subsequent calibration attempts crashes Control Center.
Abrt detects such crashes as bug 1111818.

Comment 1 Fedora End Of Life 2015-05-29 12:50:42 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 2 Pavel Malyshev 2015-06-14 19:14:55 UTC
Still there in Fedora 22:


Jun 14 22:11:03 kelly.ddns.int.prhv.afunix.org colord[2148]: (colord:2148): Cd-WARNING **: the child exited with return code 1
Jun 14 22:11:03 kelly.ddns.int.prhv.afunix.org gnome-control-center.desktop[5293]: (gnome-control-center:5293): color-cc-panel-WARNING **: calibration failed with code 1: spotread exited unexpectedly

Comment 3 Pavel Malyshev 2015-06-14 19:15:15 UTC
Still there in Fedora 22:


Jun 14 22:11:03 kelly.ddns.int.prhv.afunix.org colord[2148]: (colord:2148): Cd-WARNING **: the child exited with return code 1
Jun 14 22:11:03 kelly.ddns.int.prhv.afunix.org gnome-control-center.desktop[5293]: (gnome-control-center:5293): color-cc-panel-WARNING **: calibration failed with code 1: spotread exited unexpectedly

Comment 4 Pavel Malyshev 2015-06-14 19:17:45 UTC
Gnome Control Center now crashes sometimes with https://bugzilla.redhat.com/show_bug.cgi?id=1208990

Comment 5 Federico Bruni 2015-09-23 17:00:02 UTC
I'm getting a similar error in Fedora 23:

(gnome-control-center:2951): color-cc-panel-WARNING **: calibration failed with code 1: spotread exited unexpectedly

(gnome-control-center:2951): color-cc-panel-WARNING **: /var/lib/gdm/.local/share/icc/edid-01c9d87ac148cb968fac56549e8440e3.icc is not usable by this user

(gnome-control-center:2951): color-cc-panel-WARNING **: failed to start calibrate: failed to calibrate


The second warning seems related to permissions of this directory:

$ ls -l /var/lib/ | grep gdm
drwxrwx--T. 6 gdm            gdm            4096 23 set 18.29 gdm


However, adding my user to the gdm group did not help:

$ groups
fede wheel gdm colord


The device is:

$ lsusb | grep X-Rite
Bus 004 Device 004: ID 0765:5020 X-Rite, Inc. i1 Display Pro


And the udev rule is present:

$ grep 0765 /usr/lib/udev/rules.d/69-cd-sensors.rules | grep 5020
ATTRS{idVendor}=="0765", ATTRS{idProduct}=="5020", ENV{COLORD_SENSOR_KIND}="i1-display3", ENV{COLORD_SENSOR_CAPS}="lcd crt projector ambient"

Comment 6 mertensb.mazda 2015-10-16 07:56:05 UTC
I encounter the same problem on my Fedora 22 (fully up to date) system.

On some of the crashes I see the following backtrace in journald:
Oct 15 22:56:59 formenos.lan org.gnome.Bijiben.SearchProvider[3574]: (bijiben-shell-search-provider:9614): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Oct 15 22:56:59 formenos.lan org.gnome.Bijiben.SearchProvider[3574]: (bijiben-shell-search-provider:9614): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Oct 15 22:56:59 formenos.lan org.gnome.Bijiben.SearchProvider[3574]: (bijiben-shell-search-provider:9614): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Oct 15 22:57:11 formenos.lan org.gnome.ControlCenter.SearchProvider[3574]: (gnome-control-center:4546): color-cc-panel-CRITICAL **: cc_color_calibrate_setup: assertion 'calibrate->priv->device_kind != CD_SENSOR_
CAP_UNKNOWN' failed
Oct 15 22:57:11 formenos.lan audit[4546]: <audit-1701> auid=1026 uid=1026 gid=1026 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=4546 comm="gnome-control-c" exe="/usr/bin/gnome-control-cen
ter" sig=11
Oct 15 22:57:11 formenos.lan kernel: gnome-control-c[4546]: segfault at 8 ip 0000000000460897 sp 00007ffc94e9eed0 error 4 in gnome-control-center[400000+381000]
Oct 15 22:57:20 formenos.lan systemd-coredump[9701]: Process 4546 (gnome-control-c) of user 1026 dumped core.


Stack trace of thread 4546:
#0 0x0000000000460897 gcm_prefs_calib_apply_cb (gnome-control-center)
#1 0x00007f4272781f04 _g_closure_invoke_va (libgobject-2.0.so.0)
#2 0x00007f427279bc7d g_signal_emit_valist (libgobject-2.0.so.0)
#3 0x00007f427279c29f g_signal_emit (libgobject-2.0.so.0)
#4 0x00007f4273110dd6 on_assistant_apply (libgtk-3.so.0)
#5 0x00007f4272781f04 _g_closure_invoke_va (libgobject-2.0.so.0)
#6 0x00007f427279bc7d g_signal_emit_valist (libgobject-2.0.so.0)
#7 0x00007f427279c29f g_signal_emit (libgobject-2.0.so.0)
#8 0x00007f427312626d gtk_button_do_release (libgtk-3.so.0)
#9 0x00007f42731262d5 gtk_real_button_released (libgtk-3.so.0)
#10 0x00007f4272781cd5 g_closure_invoke (libgobject-2.0.so.0)
#11 0x00007f427279322d signal_emit_unlocked_R (libgobject-2.0.so.0)
#12 0x00007f427279bef0 g_signal_emit_valist (libgobject-2.0.so.0)
#13 0x00007f427279c29f g_signal_emit (libgobject-2.0.so.0)
#14 0x00007f4273124350 multipress_released_cb (libgtk-3.so.0)
#15 0x00000033b7605db0 ffi_call_unix64 (libffi.so.6)
#16 0x00000033b7605818 ffi_call (libffi.so.6)
#17 0x00007f4272782a25 g_cclosure_marshal_generic_va (libgobject-2.0.so.0)
#18 0x00007f4272781f04 _g_closure_invoke_va (libgobject-2.0.so.0)
#19 0x00007f427279bc7d g_signal_emit_valist (libgobject-2.0.so.0)
#20 0x00007f427279c29f g_signal_emit (libgobject-2.0.so.0)
#21 0x00007f42731cceb1 gtk_gesture_multi_press_end (libgtk-3.so.0)
#22 0x00007f4272784aee g_cclosure_marshal_VOID__BOXEDv (libgobject-2.0.so.0)
#23 0x00007f4272781f04 _g_closure_invoke_va (libgobject-2.0.so.0)
#24 0x00007f427279bc7d g_signal_emit_valist (libgobject-2.0.so.0)
#25 0x00007f427279c29f g_signal_emit (libgobject-2.0.so.0)
#26 0x00007f42731ca4ce _gtk_gesture_check_recognized (libgtk-3.so.0)
#27 0x00007f42731cb91b gtk_gesture_handle_event (libgtk-3.so.0)
#28 0x00007f42731ce355 gtk_gesture_single_handle_event (libgtk-3.so.0)
#29 0x00007f42731a105b gtk_event_controller_handle_event (libgtk-3.so.0)
#30 0x00007f4273348ded _gtk_widget_run_controllers (libgtk-3.so.0)
#31 0x00007f427321315a _gtk_marshal_BOOLEAN__BOXEDv (libgtk-3.so.0)
#32 0x00007f4272781f04 _g_closure_invoke_va (libgobject-2.0.so.0)
#33 0x00007f427279b793 g_signal_emit_valist (libgobject-2.0.so.0)
#34 0x00007f427279c29f g_signal_emit (libgobject-2.0.so.0)
#35 0x00007f427334c6e4 gtk_widget_event_internal (libgtk-3.so.0)
#36 0x00007f427321064e propagate_event (libgtk-3.so.0)
#37 0x00007f42732122ae gtk_main_do_event (libgtk-3.so.0)
#38 0x00007f4272d98772 gdk_event_source_dispatch (libgdk-3.so.0)
#39 0x00007f4272481a8a g_main_context_dispatch (libglib-2.0.so.0)
#40 0x00007f4272481e20 g_main_context_iterate.isra.29 (libglib-2.0.so.0)
#41 0x00007f4272481ecc g_main_context_iteration (libglib-2.0.so.0)
#42 0x00007f4272a6d26c g_application_run (libgio-2.0.so.0)
#43 0x000000000044ca6b main (gnome-control-center)
#44 0x00007f4271d90700 __libc_start_main (libc.so.6)
#45 0x000000000044cc09 _start (gnome-control-center)


Stack trace of thread 4550:
#0 0x00007f4271e672fd poll (libc.so.6)
#1 0x00007f4272481dbc g_main_context_iterate.isra.29 (libglib-2.0.so.0)
#2 0x00007f4272481ecc g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007f4272481f09 glib_worker_main (libglib-2.0.so.0)
#4 0x00007f42724a90a5 g_thread_proxy (libglib-2.0.so.0)
#5 0x00007f4274859555 start_thread (libpthread.so.0)
#6 0x00007f4271e72b9d __clone (libc.so.6)

Stack trace of thread 4549:
#0 0x00007f4271e672fd poll (libc.so.6)
#1 0x00007f4272481dbc g_main_context_iterate.isra.29 (libglib-2.0.so.0)
#2 0x00007f4272482142 g_main_loop_run (libglib-2.0.so.0)
#3 0x00007f4272aa3696 gdbus_shared_thread_func (libgio-2.0.so.0)
#4 0x00007f42724a90a5 g_thread_proxy (libglib-2.0.so.0)
#5 0x00007f4274859555 start_thread (libpthread.so.0)
#6 0x00007f4271e72b9d __clone (libc.so.6)

I am using an eye1 device.

Strangely enough on my Fedora 21 system calibration worked well yesterday.
Working Fedora 21 versions:
gnome-color-manager-3.14.2-1.fc21.x86_64
control-center-3.14.5-1.fc21.x86_64

Comment 7 mertensb.mazda 2015-10-17 13:22:55 UTC
I tested on my laptop (also Fedora 22 fully up to date).

Color management fails as well.

No stack trace but this is the full set of log messages from plugging in the device to the point where color manager exits

Oct 17 15:20:46 thorondor.arda kernel: usb 1-3: new low-speed USB device number 5 using xhci_hcd
Oct 17 15:20:46 thorondor.arda kernel: usb 1-3: New USB device found, idVendor=0971, idProduct=2003
Oct 17 15:20:46 thorondor.arda kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 17 15:20:46 thorondor.arda kernel: usb 1-3: Product: Eye-One display 
Oct 17 15:20:46 thorondor.arda kernel: usb 1-3: Manufacturer: GretagMacbeth
Oct 17 15:20:46 thorondor.arda kernel: usb 1-3: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
Oct 17 15:20:46 thorondor.arda pulseaudio[1741]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended.
Oct 17 15:20:46 thorondor.arda gnome-session[2198]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2a0000f (Color)
Oct 17 15:21:03 thorondor.arda org.gnome.ControlCenter.SearchProvider[2195]: (gnome-control-center:3053): color-cc-panel-CRITICAL **: cc_color_calibrate_setup: assertion 'calibrate->priv->device_kind != CD_SENSOR_CAP_UNKNOWN' failed
Oct 17 15:21:03 thorondor.arda kernel: show_signal_msg: 6 callbacks suppressed
Oct 17 15:21:03 thorondor.arda kernel: gnome-control-c[3053]: segfault at 8 ip 0000000000460897 sp 00007ffc901564d0 error 4 in gnome-control-center[400000+381000]
Oct 17 15:21:03 thorondor.arda audit[3053]: <audit-1701> auid=1026 uid=1026 gid=1026 ses=1 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=3053 comm="gnome-control-c" exe="/usr/bin/gnome-control-center" sig=11
Oct 17 15:21:04 thorondor.arda gdb[3750]: detected unhandled Python exception

Oct 17 15:21:07 thorondor.arda dbus[967]: [system] Activating service name='org.freedesktop.problems' (using servicehelper)
Oct 17 15:21:07 thorondor.arda dbus[967]: [system] Successfully activated service 'org.freedesktop.problems'
Oct 17 15:21:07 thorondor.arda /usr/libexec/gdm-x-session[2117]: Activating service name='ca.desrt.dconf'
Oct 17 15:21:07 thorondor.arda /usr/libexec/gdm-x-session[2117]: Successfully activated service 'ca.desrt.dconf'

Comment 8 Fedora End Of Life 2016-07-19 19:30:22 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.