Bug 1208990

Created attachment 1010957 [details]
File: backtrace

Created attachment 1010958 [details]
File: cgroup

Created attachment 1010959 [details]
File: core_backtrace

Created attachment 1010960 [details]
File: dso_list

Created attachment 1010961 [details]
File: environ

Created attachment 1010962 [details]
File: limits

Created attachment 1010963 [details]
File: maps

Created attachment 1010964 [details]
File: mountinfo

Created attachment 1010965 [details]
File: namespaces

Created attachment 1010966 [details]
File: open_fds

Created attachment 1010967 [details]
File: proc_pid_status

Still a problem when trying to calibrate a MacbookPro 8,2 with an i1Pro2. The problem happens when naming the profile and clicking Apply.
control-center-3.16.1-1.fc22.x86_64

[ 3198.162762] f22m.localdomain gnome-control-center.desktop[3477]: (gnome-control-center:3477): color-cc-panel-CRITICAL **: cc_color_calibrate_setup: assertion 'calibrate->priv->device_kind != CD_SENSOR_CAP_UNKNOWN' failed
[ 3196.593900] f22m.localdomain kernel: gnome-control-c[3477]: segfault at 8 ip 0000000000460877 sp 00007ffd4535e930 error 4 in gnome-control-center[400000+380000]
[ 3198.163366] f22m.localdomain audit[3477]: <audit-1701> auid=1000 uid=1000 gid=1000 ses=1 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=3477 comm="gnome-control-c" exe="/usr/bin/gnome-control-center" sig=11
[ 3198.582824] f22m.localdomain gdb[3657]: detected unhandled Python exception

I built a printer profile with argyllcms-1.6.3-4.fc22 and this same i1 Pro 2 just a bit ago and it worked fine, so I don't think it's a device problem.

Created attachment 1022356 [details]
journal output

This is also a problem with a colorhug2, I get an error about "color" when connecting the device, and then a crash when trying to calibrate shortly after clicking Apply.

This occurs to me when trying to calibrate my Thinkpad T400s (internal display). Strangely enough, there's no crash when calibrating my externally attached NEC 1980SX (same host, same ColorHUG device).

Another user experienced a similar problem:

See Bug 1140353 (https://bugzilla.redhat.com/show_bug.cgi?id=1140353)

Steps to reproduce:
 - attach a color calibration device (Gretag-Macbeth AG Eye-One display in my case)
 - open the color management application
 - select the monitor to calibrate
 - fill in the different screens of the wizard
 - click apply to start the calibration

Expected result:
color calibration starts

Actual results:
screen closes, no message reported to the user.
Logs show:
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'

reporter:       libreport-2.6.2
backtrace_rating: 4
cmdline:        gnome-control-center color
crash_function: gcm_prefs_calib_apply_cb
executable:     /usr/bin/gnome-control-center
global_pid:     3053
kernel:         4.1.10-200.fc22.x86_64
package:        control-center-3.16.3-1.fc22
reason:         gnome-control-center killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1026

I managed to calibrate one of my monitors using gcm-calibrate:

First I used `colormgr get-devices` to get a list of devices.
I don't understand all of the output, e.g. I don't understand why my monitor is listed twice with two different device IDs:
Object Path:   /org/freedesktop/ColorManager/devices/xrandr_eDP34_gdm_42
Owner:         gdm
Created:       October 17 2015, 01:26:09 PM
Modified:      October 17 2015, 01:26:09 PM
Type:          display
Enabled:       Yes
Embedded:      Yes
Model:         W65 67SZ
Vendor:        Notebook
Serial:        unknown
Seat:          seat0
Scope:         temp
Colorspace:    rgb
Device ID:     xrandr-eDP34
Metadata:      XRANDR_name=eDP34
Metadata:      OutputPriority=primary
Metadata:      OwnerCmdline=/usr/libexec/gnome-settings-daemon 
Metadata:      OutputEdidMd5=80bedfd52d6cdc6b9c1a32cfdf8fdc98

Object Path:   /org/freedesktop/ColorManager/devices/xrandr_eDP1_m8ram_1026
Owner:         m8ram
Created:       October 17 2015, 01:26:19 PM
Modified:      October 17 2015, 01:26:19 PM
Type:          display
Enabled:       Yes
Embedded:      Yes
Model:         W65 67SZ
Vendor:        Notebook
Serial:        unknown
Seat:          seat0
Scope:         temp
Colorspace:    rgb
Device ID:     xrandr-eDP1
Profile 1:     icc-91705aaf5e9551623cfc173bf86e4bf4
               /home/m8ram/.local/share/icc/edid-80bedfd52d6cdc6b9c1a32cfdf8fdc98.icc
Profile 2:     icc-0947b6ece917a5d18aeb21a96aff86e6
               /var/lib/gdm/.local/share/icc/edid-80bedfd52d6cdc6b9c1a32cfdf8fdc98.icc
Metadata:      XRANDR_name=eDP1
Metadata:      OutputPriority=primary
Metadata:      OwnerCmdline=/usr/libexec/gnome-settings-daemon 
Metadata:      OutputEdidMd5=80bedfd52d6cdc6b9c1a32cfdf8fdc98

Then used these device IDs to start gcm-calibrate:
gcm-calibrate -d xrandr-eDP1

I first tried xrandr-eDP34 but that didn't work.

This appears to be a different but very similar tool for calibration so I don't know why control center launches something else.

colomgr is part of colord-1.2.10-2.fc22.x86_64
gcm-calibrate is part of gnome-color-manager-3.16.0-1.fc22.x86_64.

Unfortunately it doesn't work on my desktop.  colormgr lists only one device (only one screen to be precise, i does list my printer).
And that device throws the same "failed to calibrate: failed to match display" error that using the first device on my laptop threw.

Then I tried the same procedure on a different laptop.
I first tried to use the color management application that starts automatically when I plug in the device and encountered the same crash as described in this bug report.
Then when I tried the approach using gcm-calibrate I noticed that argyllcms and gnome-color-manager were not even installed. (and vte-profile and vte291 which these depend on)
On the second laptop the gcm-calibrate was also successful and colormgr also lists two entries for the built in screen.

Hope this helps someone.

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.