Closed imax9000 closed 2 months ago
Where do I start figuring out why?
What distro and desktop are you using?
Where do I start figuring out why?
What distro and desktop are you using?
KDE neon, based on Ubuntu 22.04. With KDE 6.0 running on Wayland.
% dpkg -l | grep colord
ii colord 1.4.6-1 amd64 system service to manage device colour profiles -- system daemon
ii colord-data 1.4.6-1 all system service to manage device colour profiles -- data files
ii colord-kde 24.08.0-0zneon+22.04+jammy+release+build1 amd64 Color management for KDE
ii libcolord2:amd64 1.4.6-1 amd64 system service to manage device colour profiles -- runtime
strace
it is then?
sigh I've had different plans for today...
I think you'll need to open an issue against colord-kde in the KDE project I'm afraid, I'm only familiar with colord and the GNOME integration.
What does colord-kde have to do with the lack of troubleshooting tools in colord?
What does colord-kde have to do with the lack of troubleshooting tools in colord?
colord-kde creates the display devices. Does it work if you use GNOME?
What does colord-kde have to do with the lack of troubleshooting tools in colord?
colord-kde creates the display devices. Does it work if you use GNOME?
Hm, good to know. Is this fact documented anywhere? Is it referenced in the man page?
sigh I guess it's straight up not implemented.
kded6[14308]: colord: X11 not detect disabling
But don't get me wrong: I opened this issue not to figure out what's wrong on my particular machine. I opened it to figure out what tools does colord
provide for doing even basic troubleshooting, and there seems to be none at all, not even a description of what it is and isn't responsible for.
If not for your last comment, I, an ordinary user, would have to spend many hours reading strace
dumps and your source code just to understand that colord
doesn't do any device detection on its own and I need to look elsewhere. It is already frustrating that I needed to contact you for that and wait for 4 days. It would be orders of magnitude more frustrating if I had already wasted many hours of my life on an ultimately pointless exercise of reading your code.
So you just want me to feel bad about not having those specific tools or manpage sections? I'm not really sure what you want me to do; users are not supposed to debug anything, it's supposed to just work. Maybe try GNOME -- that should just work.
I can't possibly be responsible for the KDE integration as I don't even use KDE and it's not something we really support at Red Hat. I think you need to file a bug in the KDE project now.
I don't care how you feel (sorry). I want a service that is running on my machine to provide tools for introspection and troubleshooting.
No software in the known universe "just works". All software sucks and fails all the time. If I wanted to use something that either works or doesn't and I have no way to fix it - I'd be still running Windows with Cygwin on top.
Yes, the bug for the lack of support on Wayland is definitely going to be for KDE, not for you.
Absence of troubleshooting tools in colord
is still a problem thought, and it's not related to any other software project.
Consider this: if a basic verbose logging was present that would point me to colord-kde
not creating a device inside colord
- I wouldn't even have to bother you at all, and would go straight to colord-kde
I don't care how you feel
Then I can no longer help I'm afraid.
colord 1.4.6 doesn't detect my laptop's display. Where do I start figuring out why?
colormgr get-devices
is only listing a network printer.journalctl -u colord
shows only generic start/stop messages.man colord
doesn't exist.Is there anything I can do short of
strace
ing the daemon while it's running under systemd?