[colord-kde] [Bug 328248] colord-kde possibly assigns the profile to the wrong X atom when >1 monitor is connected

2018-05-03 Thread Simon Raffeiner
https://bugs.kde.org/show_bug.cgi?id=328248 --- Comment #13 from Simon Raffeiner <sturmf...@lieberbiber.de> --- I think darktable actually gives higher precedence to colord if it finds both an active colord profile and an X atom for the same display. But it has to support and check both. -

[colord-kde] [Bug 328248] colord-kde possibly assigns the profile to the wrong X atom when >1 monitor is connected

2018-05-03 Thread Simon Raffeiner
https://bugs.kde.org/show_bug.cgi?id=328248 --- Comment #11 from Simon Raffeiner <sturmf...@lieberbiber.de> --- darktable is one of the few applications which actually uses both colord and the X11 atoms. The darktable-cmstest command line utility is often used as a convenient shortcut to

[colord-kde] [Bug 328248] colord-kde possibly assigns the profile to the wrong X atom when >1 monitor is connected

2018-03-22 Thread Simon Raffeiner
https://bugs.kde.org/show_bug.cgi?id=328248 --- Comment #5 from Simon Raffeiner <sturmf...@lieberbiber.de> --- The new patch applies cleanly against the latest colord-kde git master and seems to work perfectly, at least darktable-cmstest reports that both colord and the X atoms now hold th

[colord-kde] [Bug 328248] colord-kde possibly assigns the profile to the wrong X atom when >1 monitor is connected

2018-03-19 Thread Simon Raffeiner
https://bugs.kde.org/show_bug.cgi?id=328248 Simon Raffeiner <sturmf...@lieberbiber.de> changed: What|Removed |Added CC||