Seeing this messages a lot in my logs when I run digiKam:
ICM Wayland: cannot dial with the colord service: "The name is not activatable"
The last session had some 200 occurences of this message.
Is this something that needs to be reported as a bug?
kinfo:
Operating System: EndeavourOS
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.0
Kernel Version: 6.12.59-1-lts (64-bit)
Graphics Platform: Wayland
Processors: 16 × 13th Gen Intel® Core™ i7-13620H
Memory: 16 GiB of RAM (15.2 GiB usable)
Graphics Processor: Mesa Intel® Graphics
Hello! This is an old thread, I know, but I have the exact same question and cannot find any information about it anywhere, not in this forum nor in the digiKam subreddit.
For the sake of sharing, my kinfo output:
Operating System: openSUSE Tumbleweed 20260313
KDE Plasma Version: 6.6.2
KDE Frameworks Version: 6.23.0
Qt Version: 6.10.2
Kernel Version: 6.19.6-2-default (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz
Memory: 32 GiB of RAM (31.3 GiB usable)
Graphics Processor: AMD Radeon RX 6700 XT
and digikam -v output is digikam 9.0.0
Studying the output of journalctl -f while using digiKam, I can see that the message appears whenever I open an image, whether through the Preview pane or Image Editor. Usually it will send two or three identical messages per image opened.
colord manages color profiles, so I can only guess there is some issue with how digiKam is passing color profile information to it. A short term fix is to just turn off Color Management in Configure digiKam…. I’m an amateur photographer at best so accurate color management isn’t really important to me, but it wouldn’t be an acceptable workaround for professionals.
If it’s a common enough occurrence for other people, then I’d think it’s worth reporting as a bug, but the fact that @semlraug is seemingly the only other person to have noticed it, I wonder if its a system or configuration issue.
Has someone else seen this? Can someone try replicating it?
Well, one step forward, one step back.
Turns out colord wasn’t installed on my system. cannot dial with the colord service: "The name is not activatable" is apparently a slightly cryptic way of saying “No colord available.”
I’m not sure why digiKam was trying to use a service which wasn’t included as part of its dependencies (I guess a question for the package maintainers), but after a quick sudo zypper in colord it’s no longer saying cannot dial with the colord service.
Unfortunately, now it’s saying ICM Wayland: invalid screen number: 0, again two or three times per file previewed/opened. So it’s found colord but now it’s not finding the screen?
Just to give you an idea of how dire this spam is, since installing colord only a few hours ago, journalctl | grep -i "invalid screen number" > shenanigans.txt gives me a text file almost 7,000 lines long, all <DATE> <TIME> <HOSTNAME> digikam[PID]: ICM Wayland: invalid screen number: 0 with the occasional <DATE> <TIME> <HOSTNAME> digikam[PID]: ICM Wayland: invalid screen number: 1 thrown in for fun.
This can’t be working as intended 