- This topic has 3 replies, 3 voices, and was last updated 7 months, 4 weeks ago by
.
-
Posts
-
I just recently switch to Openmandriva Linux and I keep getting this error when running the Flatpak version of Displaycal. I’ve tried to troubleshoot, but I’m still very new to Linux. The only troubleshooting step that I could find, was to adjust Flatpak’s permissions which didn’t fix the issue.
Has anyone else encountered this?
Likely because that distro is using the newer Wayland compositor instead of the old x11 compositor.
DisplayCAL is just a UI for ArgyllCMS and ArgyllCMS was built to work on x11 and doesn’t really support Wayland.
This is largely because Wayland is newish and doesn’t have a lot of the low level color management support that x11 does and is necessary for a tool like ArgyllCMS to work.
I’ll leave it up to you to research how you might be able to switch to using x11 if you have the energy to do a lot of learning and messing with your system.
The other thing you could try is change everything on the calibration tab in DisplayCAL to “As Measured” and just profile your display without the VLUT calibration step.
Why does it actually need access to low level video APIs like the VCGT?
To load the final correction? Easy to load with the OS utilities as a fallback.
To change stuff while calibrating? Should have been some simple math in the pattern generator.
I fixed the problem by switching to Devuan. Displaycal is in the apt repo in Devuan and it works out of the box. I’m still running Wayland and KDE, so I’m not sure what the issue was in OPM.
As for why it needed access to the VCGT, I don’t know. It wouldn’t even display color patches it just failed immediately and displayed that error message.
