Cannot select ICC profile

Bug #853056 reported by Laryllan
148
This bug affects 30 people
Affects Status Importance Assigned to Milestone
gnome-color-manager (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I installed gnome-color manager and started it using the icon shown in system settings.
I am told that there are no devices found supporting color management.

What I would expect is:
A dialog where I can import an ICC profile and apply it to my display.

Recently I found that I can import ICC profiles using the command line tool gcm-viewer, but even using this tool I cannot apply any profile to my display.

The gnome-color-manager up to 11.04 did exactly what I wanted.

I added a screenshot of the color tool.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gnome-color-manager 3.1.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Sun Sep 18 09:39:29 2011
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64+mac (20110901)
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-color-manager
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Laryllan (laryllan) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-color-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
muzah (sylvain-lesne) wrote :

My NEC EA231WMi is not found in this color management utility.
GPU nVidia G210 and nVidia 280.13 driver with dvi plug.

Revision history for this message
Maxime Normand (maxime-normand) wrote :

Anybody tested this again with the final release of 11.10 ? This is the only thing preventing me from upgrading to Oneiric.

Revision history for this message
Laryllan (laryllan) wrote :

I believe this will not be fixed any time soon, as it's not a fault in Ubuntu.
The new Gnome 3 settings don't provide this functionality as of now.

As a workaround, you can do the following:
1. install argyll color management suite
2. create a file containing the following:
#!/bin/bash
dispwin /path/to/your/icc/profile.icc
3. make the file executable
4. add the newly created skript to your start programs

Revision history for this message
Maxime Normand (maxime-normand) wrote :

Thanks a lot Laryllan, your suggestion seems to works, when I check with dispwin -V it says the profile is loaded, kind of hard to tell with the naked eye but I'm gonna trust it's true ;)

Revision history for this message
Simon Hirscher (codethief) wrote :

I can confirm this for 11.10 final (@Maxime Normand). Up to 11.04 everything worked perfectly.
As Laryllan pointed out it seems like the color management dialogue we're used to isn't available in Gnome 3 settings anymore. Also, I can't find it among the applications the Gnome3 shell and Unity list.

Revision history for this message
Simon Hirscher (codethief) wrote :

(Does anyone know how to access it via console?)

Revision history for this message
Simon Hirscher (codethief) wrote :

Excuse the spamming.
I suppose it hasn't got much to do with this bug here but I just tried Laryllan's workaround and it doesn't work for me:

simon@philosoph:~$ ./colorprofile.sh
XRandR 1.2 is faulty - falling back to older extensions
Dispwin: Error - File '/home/simon/.color/icc/hueyPRO ThinkPad Display 1920x1080.icc' is not a valid ICC profile or Argyll .cal file

However, this the color profile which I generated and use on Windows. gcm-viewer lists it, too, without any complaints.

Revision history for this message
robertofsweden (robertofsweden) wrote :

Simon:
Try saving the .icc filename without spaces.

Revision history for this message
Neil Woolford (neil-neilwoolford) wrote :

What seems odd to me is that System-Settings > Colour lists all devices and appears to be functional on my laptop but not my desktop machine. Both have been upgraded from 10.04 to 10.10.

Revision history for this message
Neil Woolford (neil-neilwoolford) wrote :

Sorry, typo. Should read; "Both have been upgraded from 11.04 to 11.10."

Revision history for this message
Neil Woolford (neil-neilwoolford) wrote :

Laryllan's dispwin workaround in post #5 worked for me too.

Argyll was already installed, as I would have expected. Whether this is the case on a new install rather than an upgrade I wouldn't know.

The problem isn't broken colour management per se, rather a problem with automatic recognition of hardware by the gnome-colour-manager or its new front end wrapper.

I'd reckon some device recognition data or routines have been omitted or somehow disabled in the current oneiric system.

Revision history for this message
robert shearer (bdaggg) wrote :

Running pre-alph 12.04 and the bug is still present.
Using the nouveau driver seems to work fine and the display is detected and icc profiles can be loaded through Gnome colour manager.
However, once the nvidia drivers are enabled the colour manager reports 'no devices found' even though the nvidia x-server settings application shows the correct monitor.

Revision history for this message
Forest (foresto) wrote :

In previous releases, gnome-color-manager included the gcm-apply command line tool for activating a color profile. Oneiric includes gnome-color-manager 3.2, which doesn't have gcm-apply. In typical GNOME fashion, there seems to be no documentation on this version. (The most recent manual I found is for 3.0, which still lists gcm-apply as the appropriate tool.)

Revision history for this message
Neil Woolford (neil-neilwoolford) wrote :

After further work I can add that Argyll isn't a default install.

Also I can confirm bdaggg's observation in #14 that removing the nvidia binary (closed) driver from my system allows Gnome Color Manager to function as I would expect.

helix2301 (helix2301)
Changed in gnome-color-manager (Ubuntu):
status: Confirmed → In Progress
status: In Progress → Confirmed
Revision history for this message
Damien Ciabrini (dciabrin) wrote :

I have the same problem, nvidia closed source driver (295.20) apparently prevents my screen from being recognized properly in gnome-control-center, while it's recognized when using the nouveau driver.

I also noticed that the EDID information does not show up in xrandr...:

$ xrandr -q --verbose | head -20
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 320 x 175, current 1920 x 1200, maximum 1920 x 1200
default connected 1920x1200+0+0 (0x161) normal (normal) 0mm x 0mm
 Identifier: 0x160
 Timestamp: 27868
 Subpixel: unknown
 Clones:
 CRTC: 0
 CRTCs: 0
 Transform: 1.000000 0.000000 0.000000
             0.000000 1.000000 0.000000
             0.000000 0.000000 1.000000
            filter:
  1920x1200 (0x161) 115.2MHz *current
        h: width 1920 start 0 end 0 total 1920 skew 0 clock 60.0KHz
        v: height 1200 start 0 end 0 total 1200 clock 50.0Hz
  1920x1080 (0x162) 105.8MHz
        h: width 1920 start 0 end 0 total 1920 skew 0 clock 55.1KHz
        v: height 1080 start 0 end 0 total 1080 clock 51.0Hz
  1680x1050 (0x163) 91.7MHz
        h: width 1680 start 0 end 0 total 1680 skew 0 clock 54.6KHz

...whereas it's correctly recognized in nvidia-settings (Apple Cinema HD) and can be acquired and later decoded with parse-edid:

$ parse-edid < ~/edid.bin
parse-edid: parse-edid version 2.0.0
parse-edid: EDID checksum passed.

 # EDID version 1 revision 3
Section "Monitor"
 # Block type: 2:0 3:ff
 # Block type: 2:0 3:fc
 Identifier "Cinema HD"
 VendorName "APP"
 ModelName "Cinema HD"
 # Block type: 2:0 3:ff
 # Block type: 2:0 3:fc
 # Block type: 2:0 3:0
 # DPMS capabilities: Active off:yes Suspend:no Standby:no

 Mode "1920x1200" # vfreq 59.950Hz, hfreq 74.038kHz
  DotClock 154.000000
  HTimings 1920 1968 2000 2080
  VTimings 1200 1203 1209 1235
  Flags "-HSync" "+VSync"
 EndMode
 # Block type: 2:0 3:ff
 # Block type: 2:0 3:fc
 # Block type: 2:0 3:0
EndSection

I don't know whether it's worth saying, but ICC profiles can be applied via the command-line, although with some warnings:

$ dispwin ~/AppleCinemaHD-20120304.icc
XRandR 1.2 is faulty - falling back to older extensions

Revision history for this message
Fred (eldmannen+launchpad) wrote :

Maybe this is because Nvidia proprietary driver doesn't support XRandR 1.4?
And that XRandR 1.4 unfortunately wasn't merged even for the upcoming Xorg 1.12 release.

Revision history for this message
Graeme Pietersz (fgpietersz) wrote :

 have a similar problem (see bug #881396 which is marked as a duplicate of this) with an HP Probook 4540s with Intel graphics (it has dual radeon intel but I have the radeon turned off in the BIOS settings).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.