Bug 372450

Issue is definitely in colord-kde: https://lists.freedesktop.org/archives/colord/2016-November/000310.html

Hi,
please run kded5 by hand and with debug messages on try attaching a monitor to see if there is activity there.
I don't have a DP cable to test this atm :(

Created attachment 102278 [details]
kded5

Here it is.

those are all kscreen output, sadly 0.5 didn't got categorized output, try
export QT_LOGGING_RULES=default.*=true
colord output would be on default loggin

Created attachment 102293 [details]
log

I put export QT_LOGGING_RULES=default.*=true into ~/.bashrc and ~/.bash_profile.

I attached the output of "journalctl -b -0".

Any news on this?

I'm waiting to get time to buy such cable. In the mean time I added categorized logging, so if you compile the git version might give better information on what happened. Unfortunately it's not easy to find this cabe on local stores...

The cable is a standard Mini Displayport Cable (but even a Display Port one would be fine if you have a DP output instead of miniDP). To use MST (Multistream) you have to attach it to a monitor capable of handling MST with a miniDP or DP input and a miniDP or DP output.

I will compile git version and attach logs from kded5 when attaching the external monitor.

ok, I missread and didn't notice the DP-MST part.
So I brought a DP-DP cable and everything was fine.
Then I attached the DVI cabe to the monitor and instead of seing 3 monitors it kept showing 2. Of course there is only 2 monitors but I believe it's the same issue, since you have two identicals monitors it thinks it's the same, I'll investigate further later to see what Gnome Color Manager does.
Best.

Created attachment 102786 [details]
kded5.log

Here is the output of kded5 when attaching the DP cable with colord-kde-git. Sorry if it took so long.

One year without answer...

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

I'm personally not interested in this anymore because Wayland basically dropped any kind of color management, but I've fired up old X11 and it seems to work now:

$ colormgr get-devices

Object Path:   /org/freedesktop/ColorManager/devices/xrandr_Dell_Inc__DELL_U2515H_9X2VY52D02ZL_niko_1000
Owner:         niko
Created:       novembre 11 2022, 03:32:04 PM
Modified:      novembre 11 2022, 03:32:05 PM
Type:          display
Enabled:       Yes
Embedded:      Yes
Model:         DELL U2515H
Vendor:        Dell
Serial:        9X2VY52D02ZL
Scope:         temp
Colorspace:    rgb
Device ID:     xrandr-Dell Inc.-DELL U2515H-9X2VY52D02ZL
Profile 1:     icc-d016234a0d5c7598d9bbc753e4a7f3bd
               /home/niko/.local/share/icc/edid-c9d4bf8ee238c8b7abb434cd496632de.icc
Metadata:      OutputEdidMd5=c9d4bf8ee238c8b7abb434cd496632de
Metadata:      OutputPriority=primary
Metadata:      XRANDR_name=DP-1-8
Metadata:      OwnerCmdline=/usr/bin/kded5 

Object Path:   /org/freedesktop/ColorManager/devices/xrandr_Dell_Inc__DELL_U2515H_9X2VY52D04KL_niko_1000
Owner:         niko
Created:       novembre 11 2022, 03:32:05 PM
Modified:      novembre 11 2022, 03:32:06 PM
Type:          display
Enabled:       Yes
Embedded:      Yes
Model:         DELL U2515H
Vendor:        Dell
Serial:        9X2VY52D04KL
Scope:         temp
Colorspace:    rgb
Device ID:     xrandr-Dell Inc.-DELL U2515H-9X2VY52D04KL
Profile 1:     icc-c2af42e7940daecc556dd891aa572828
               /home/niko/.local/share/icc/edid-7ae9afdc51735aa75676bb90878c22da.icc
Metadata:      OutputEdidMd5=7ae9afdc51735aa75676bb90878c22da
Metadata:      OutputPriority=primary
Metadata:      XRANDR_name=DP-1-1-8
Metadata:      OwnerCmdline=/usr/bin/kded5