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

https://bugs.kde.org/show_bug.cgi?id=328248 --- Comment #13 from Simon Raffeiner --- 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. -- You

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

https://bugs.kde.org/show_bug.cgi?id=328248 --- Comment #12 from Daniel Nicoletti --- Ok thanks for the info, that aligns up with what I was expecting from GCM. I'm now just curious why darktable doesn't simply ignores the XAtom if it knows about colord... Whatever, I'll

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

https://bugs.kde.org/show_bug.cgi?id=328248 --- Comment #11 from Simon Raffeiner --- 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 check

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

https://bugs.kde.org/show_bug.cgi?id=328248 --- Comment #10 from Daniel Nicoletti --- In fact darktable should be patched to ask colord about what is being used ATM, this would then make is just work on Wayland. Which ATM has no support for color correction as that needs to

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

https://bugs.kde.org/show_bug.cgi?id=328248 --- Comment #9 from Daniel Nicoletti --- It is a question for Gnome because we must behave consistently, the problem is not this being legacy but the fact that enumerating X outputs is just broken this way, might work for you but

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

https://bugs.kde.org/show_bug.cgi?id=328248 --- Comment #8 from h...@gmx.de --- Well, the patch at hand is for the KDE frontend which obviously does nothing for GNOME. The real question is probably more about the usefulness of the additional X atoms. Currently most programs are not using them,

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

https://bugs.kde.org/show_bug.cgi?id=328248 --- Comment #7 from Daniel Nicoletti --- Sorry beeing quite busy lately, but I'd like to ask if this works on Gnome? Last time I discussed this issue with colord author, he said _ICC_PROFILE atoms for outputs were completely broken

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

https://bugs.kde.org/show_bug.cgi?id=328248 Valeriy Malov changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest

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

https://bugs.kde.org/show_bug.cgi?id=328248 Valeriy Malov changed: What|Removed |Added CC||jazzv...@gmail.com -- You

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

https://bugs.kde.org/show_bug.cgi?id=328248 --- Comment #5 from Simon Raffeiner --- 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 the same

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

https://bugs.kde.org/show_bug.cgi?id=328248 h...@gmx.de changed: What|Removed |Added Attachment #83836|0 |1 is obsolete|

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

https://bugs.kde.org/show_bug.cgi?id=328248 Simon Raffeiner changed: What|Removed |Added CC|

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

https://bugs.kde.org/show_bug.cgi?id=328248 cpon changed: What|Removed |Added CC||cpigat...@gmail.com -- You are