You are not logged in.
Hello guys,
I hope I could describe it clear. Thanks in advance.
The issue: After some Plasma KDE Update, Philips 243V Display can't be detected.
The display shows Arch loading but it goes sleep after I login KDE session.
The Plasma version
$ plasmashell --version
plasmashell 5.27.7Usual display plugging had worked fine till some KDE update was installed. When I plug the HDMI cable to my notebook:
$ journalctl -f | grep --line-buffered kde
Sep 04 23:29:20 thinkpad-notebook kded5[1570]: colord: Checking outputs
Sep 04 23:29:20 thinkpad-notebook kded5[1570]: colord: PNP ID "IVO" Vendor Name ""
Sep 04 23:29:20 thinkpad-notebook kded5[1570]: colord: Adding device id "xrandr-eDP-1"
Sep 04 23:29:20 thinkpad-notebook kded5[1570]: colord: Output Hash "ba364839cfc24064eca321acd05e5b60"
Sep 04 23:29:20 thinkpad-notebook kded5[1570]: colord: Output isLaptop true
Sep 04 23:29:20 thinkpad-notebook kded5[1570]: colord: Failed to register device: "device id 'xrandr-eDP-1' already exists"
Sep 04 23:29:20 thinkpad-notebook kded5[1570]: colord: Found colord device "/org/freedesktop/ColorManager/devices/xrandr_eDP_1_my-user_1000"
Sep 04 23:29:20 thinkpad-notebook kded5[1570]: colord: Failed to locate "xrandr-eDP-1" in the list of known outputs
Sep 04 23:29:20 thinkpad-notebook kded5[1570]: colord: EDID ICC Profile already exists "/home/my-user/.local/share/icc/edid-ba364839cfc24064eca321acd05e5b60.icc"
Sep 04 23:29:21 thinkpad-notebook kded5[1570]: colord: Checking outputs
Sep 04 23:29:21 thinkpad-notebook kded5[1570]: colord: PNP ID "IVO" Vendor Name ""
Sep 04 23:29:21 thinkpad-notebook kded5[1570]: colord: Adding device id "xrandr-eDP-1"
Sep 04 23:29:21 thinkpad-notebook kded5[1570]: colord: Output Hash "ba364839cfc24064eca321acd05e5b60"
Sep 04 23:29:21 thinkpad-notebook kded5[1570]: colord: Output isLaptop true
Sep 04 23:29:21 thinkpad-notebook kded5[1570]: colord: Failed to register device: "device id 'xrandr-eDP-1' already exists"
Sep 04 23:29:21 thinkpad-notebook kded5[1570]: colord: Found colord device "/org/freedesktop/ColorManager/devices/xrandr_eDP_1_my-user_1000"
Sep 04 23:29:21 thinkpad-notebook kded5[1570]: colord: Failed to locate "xrandr-eDP-1" in the list of known outputs
Sep 04 23:29:21 thinkpad-notebook kded5[1570]: colord: EDID ICC Profile already exists "/home/my-user/.local/share/icc/edid-ba364839cfc24064eca321acd05e5b60.icc"I tried to delete the ICC files:
$ pwd
/home/my-user/.local/share/icc
$ ls -la
total 16
drwxr-xr-x 2 my-user my-user 4096 Sep 4 23:14 .
drwxr-xr-x 69 my-user my-user 4096 Sep 9 00:20 ..
-rw-r--r-- 1 my-user my-user 1148 Sep 4 23:14 edid-ba364839cfc24064eca321acd05e5b60.icc
-rw-r--r-- 1 my-user my-user 1328 Sep 4 23:14 edid-c9bdf434a6734b6e7bc228f6bb14b9cb.iccbut anyway they are being renewed each time I plug the display while the issue is persistent.
Also I tried to locate files where "device id 'xrandr-eDP-1'" happens:
$ sudo grep -rE 'xrandr.?[eE][Dd][Pp].?1' ~ /etc /usrbut results don't lead to any config files, it seems it's stored in some binary format elsewhere.
Things I haven't tried:
Create a new user, login into Plasma KDE session and plug the display
Find another display and plug it with the old user
Will do this.
If you have any suggestion, I appreciate your ideas.
Last edited by Just-a-Punk (2023-09-09 19:09:56)
Offline
colord is hardly relevant to detected outputs.
Wipe the kscreen config, https://wiki.archlinux.org/title/KDE#Un … lution_set
Otherwise please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General
it goes sleep after I login KDE session
To be clear: the HDMI output is still active for the DM (eg. SDDM)?
Offline
Things I haven't tried:
Find another display and plug it with the old user
With another one, all goes as expected fine.
To be clear: the HDMI output is still active for the DM (eg. SDDM)?
Yes, I login KDE and the external display goes sleep, I logout KDE and it wakes up again.
Wipe the kscreen config, https://wiki.archlinux.org/title/KDE#Un … lution_set
It has solved my issue.
There were few configuration files in ~/.local/share/kscreen/ from different dates those were probably in some conflict. Wiping all the content has solved the problem.
@seth, thank you friend
[SOLVED]
Last edited by Just-a-Punk (2023-10-06 11:25:49)
Offline