The story...

I've been having an issue with my prints since 3 months! A strong pink
color cast was on all printed pictures.

I have suspected an issue with a new version of CUPS upgraded at this
time. Working with the CUPS team and doing lot of testing it turns out
it was not a CUPS issue. I got a great help from the CUPS team.

   see Debian bug tracker #763517
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763517

   I've got many private messages to test different things. So not all
   is field above.

Then I thought that a possible culprit was colord. Indeed an upgrade was
done at this time. But after investigation with the colord maintainers
nothing was indicating that colord was reporting some wrong profile.

   see colord bug tracker #86881
   https://bugs.freedesktop.org/show_bug.cgi?id=86881

Then I found *by chance* (to keep it short) that the issue was EoG. The
tools is printing using the *display profile*. And this explains why I
had no issue on another computer where the screen is not profiled.

   see GNOME bugzilla #740994
   https://bugzilla.gnome.org/show_bug.cgi?id=740994

To summarize... I'm even more motivated to finalized my print module for
darktable to avoid those kind of issues!

-- 
  Pascal Obry /  Magny Les Hameaux (78)

  The best way to travel is by means of imagination

  http://v2p.fr.eu.org
  http://www.obry.net

  gpg --keyserver keys.gnupg.net --recv-key F949BD3B


------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
darktable-devel mailing list
darktable-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/darktable-devel

Reply via email to