Bug 372450 - colord-kde 0.5 does not show any monitor
Summary: colord-kde 0.5 does not show any monitor
Status: RESOLVED FIXED
Alias: None
Product: colord-kde
Classification: Plasma
Component: Systems Settings Module (KCM) (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Daniel Nicoletti
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-13 23:24 UTC by darkbasic
Modified: 2022-11-11 15:38 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
kded5 (4.74 KB, text/plain)
2016-11-17 18:15 UTC, darkbasic
Details
log (262.04 KB, text/plain)
2016-11-18 12:57 UTC, darkbasic
Details
kded5.log (23.07 KB, text/plain)
2016-12-14 21:47 UTC, darkbasic
Details

Note You need to log in before you can comment on or make changes to this bug.
Description darkbasic 2016-11-13 23:24:43 UTC
OS is Archlinux and I'm using latest version of colord-kde on latest version of kf5/Plasma. I think colord has some issues with DP-MST monitors, because when my two Dell U2515H are attached it doesn't recognize any monitor at all in my laptop: I just see "sysfs-(null)" in the KCM. Today I tried it with a TV using an HDMI adapter and it did recognize it. I don't know if the problem with DP-MST is in colord-kde (hardly) or upstream in colord. Can you help me? I really don't know how to debug it because I really don't know colord.
Comment 1 darkbasic 2016-11-15 19:57:03 UTC
Issue is definitely in colord-kde: https://lists.freedesktop.org/archives/colord/2016-November/000310.html
Comment 2 Daniel Nicoletti 2016-11-17 16:52:47 UTC
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 :(
Comment 3 darkbasic 2016-11-17 18:15:25 UTC
Created attachment 102278 [details]
kded5

Here it is.
Comment 4 Daniel Nicoletti 2016-11-17 18:43:58 UTC
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
Comment 5 darkbasic 2016-11-18 12:57:06 UTC
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".
Comment 6 darkbasic 2016-12-06 16:55:30 UTC
Any news on this?
Comment 7 Daniel Nicoletti 2016-12-06 17:00:48 UTC
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...
Comment 8 darkbasic 2016-12-06 17:13:26 UTC
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.
Comment 9 Daniel Nicoletti 2016-12-09 02:50:15 UTC
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.
Comment 10 darkbasic 2016-12-14 21:47:40 UTC
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.
Comment 11 Tom Kijas 2017-11-03 16:51:02 UTC
One year without answer...
Comment 12 Justin Zobel 2022-11-10 08:52:23 UTC
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!
Comment 13 darkbasic 2022-11-11 15:38:09 UTC
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