-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No such display #13
Comments
Just to make sure: you have a physical monitor connected, right? If so, I'd need to know if ColorManager can find your monitor and in order to know that I'd need relevant dbus-monitor logs. So AFTER running gnome-gamma-tool, what is the output of:
In my case, the reply looks like this:
If you also see the monitor path there, we need to see if ColorManager recognizes it as a display, so take the name you see there and call (replace the name):
and please paste the output here. Without these I can't really know what's going on |
The output of |
Well, yes and no... mutter is supposed to manually tell colord (ColorManager) what devices are connected on startup.. Of course many things can go wrong, like if you kill the colord process and then restart it, the monitors won't be visible. Great design, isn't it? But it's GNOME so we have to lower our expectations to 0 (possibly below 0). Ok, so now I need to know if mutter has the list. So please also show the output of:
If the monitor will be visible there, the solution could be to manually tell colord about that device, but it probably won't be an easy task.. |
|
Now it gets complicated, because the next step'd be to check if mutter has created so called "meta color device".. The optimistic case is that the object exists. In that case, try running: (the id argument is important, it must match)
and then again try running gnome-gamma-tool - if mutter wanted to create the device but for some reason couldn't, this command can create the device. Otherwise it seems the bug must exist somewhere in mutter. To diagnose color-related problems in mutter, you can turn on mutter color logs by executing this command (requires superuser):
Then reboot the system and check color related logs like this:
You should see these lines:
and
In any case, the whole output is what you should include in your bug report against mutter, possibly in https://gitlab.gnome.org/GNOME/mutter/-/issues/ |
Using Fedora38 with GNOME on Wayland
./gnome-gamma-tool.py -g 2.0
returns
No such display, found 0 displays.
The text was updated successfully, but these errors were encountered: