Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 618709 - dispwin -I ... fails to create a color.jcnf file
dispwin -I ... fails to create a color.jcnf file
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: argyllcms (Show other bugs)
13
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Gwyn Ciesla
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-27 11:04 EDT by Leonard Evens
Modified: 2011-06-01 15:01 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-06-01 15:01:56 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Leonard Evens 2010-07-27 11:04:39 EDT
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.11) Gecko/20100720 Fedora/3.5.11-1.fc12 Firefox/3.5.11

dispwin -I  XXX

is supposed to create the file
.config/color.jcnf
which contains the information about where the profile is stored.
Without that, when one logs out that information is lost.  Normally
dispwin -L
should reload the calibration LUT in X, but it fails to do so because it doesn't know where the .icc file is located.  So one must rerun dispwin -I to reinstall it.

This has been confirmed by at least one other person---see the argyllcms mailing list.

I wonder if the cause is some conflict with the gnome-color-management package.  If I use that and import the .icc file, then the information is loaded in X when logging in.



Reproducible: Always

Steps to Reproduce:
1.run dispwin -I ...
2. run xprop -root | grep ICC | more to verify information is loaded in X.
3.logout
4. login again and run dispwin -L
5. xprop -root | grep ICC should find the information, but it doesn't.
Actual Results:  
See above

Expected Results:  
See above

See above conjecture about conflict with gnome-color-manager.
Comment 1 Leonard Evens 2010-07-27 11:07:18 EDT
The problem is not in argyllcms since code compiled from source at Argyllcms works as expected.
Comment 2 Bug Zapper 2011-06-01 08:43:29 EDT
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 WONTFIX if it remains open with a Fedora 
'version' of '13'.

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 prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 3 Leonard Evens 2011-06-01 14:44:31 EDT
I spoke to the gnome color management developer and discussed ways to deal with the problem.  He also said he was working on a better solutions.   The bug report can be dropped.
Comment 4 Leonard Evens 2011-06-01 14:45:16 EDT
I spoke to the gnome color management developer and discussed ways to deal with the problem.  He also said he was working on a better solutions.   The bug report can be dropped.

Note You need to log in before you can comment on or make changes to this bug.