Quote:
Originally Posted by h68
--
The workaround works perfectly!
Thank you very much.
PS : For the people being emotional on Wayland vs X11. Your comments are a waste of time. What we want is Calibre working correctly under Wayland nothing more, nothing less.
|
You're welcome, but a recent enough Calibre version should properly detect `QT_QPA_PLATFORM=xcb`, if not, that's a bug on its own, make sure you're up to date, I was able to remove the workaround on my system a few months ago.
> It's not just the lack of NVIDIA support
This has changed recently.
Nvidia has decided to properly support Wayland starting with 2021 releases. They even have a TODO list for the remaining issues -
https://forums.developer.nvidia.com/...release/214275
> All those features get tacked on randomnly using "protocol extensions". These extensions are published in an immature "beta" state and often go through multiple revisions over years
> There are dozens of different server side "compositors" aka implementations, each of which have their own bugs and idiosyncracies in how they implement the protocol and its myriad extensions.
Wayland ecosystem is developing rapidly now that Nvidia stopped constantly throwing obstacles at people.
Which protocol or compositor bug is preventing Calibre from implementing a native Wayland backend?
If there are any left, what's preventing Calibre from having an experimental backend for now, for those that would still prefer to leave XWayland behind at the cost of the affected feature?
> And yet it is being foisted on us.
That is absolutely true and needs to be taken into account - all the major Desktop Environments and more(Plasma, GNOME, Budgie, ...) are dropping X support in the foreseeable future, so Calibre *WILL* be stuck on XWayland and its associated issues on a Wayland system.
Distributions are dropping X support too, albeit more slowly than the DEs and other software.