I do not provide support for people using distro provided packages. If you are using a distro provided package, uninstall it and install the official calibre binary from calibre - Download for Linux and if you can reproduce the bug with that, re-open the ticket. Of course, if you are already using the official binary, apologies and feel free to re-open the ticket immediately
status invalid
So I’ve think that could be better if the flatpak version is the only available when searching for calibre on the software stores, since in this version all works ok.
Some people prefer to use distro packages rather than flatpaks or developers’ binaries. As long as someone is willing to maintain RPM packages in Fedora’s repos, it doesn’t make any sense to request for their removal. Just make sure you are installing the one you prefer to use before hitting the install button.
Idk about other DEs, but on Fedora KDE Discover shows a “sources” menu so you could pick the source of the package you’re downloading (flatpak or native or snap if you have that)
Also, contact the Fedora maintainer on Bugzilla and point them to the upstream discussion in order to figure out if there is a solution to apply to the Fedora (downstream) package.
If it is a bug which doesn’t affect me or not producable on my machine, I am happy to use the RPM version and don’t want it to get removed from the repos. If it as a bug which makes the application unusable for everyone, it is better to report it to the package maintainer so it gets fixed.
I agree 100%. As much as possible I use exclusively the rpm version of everything. I only have about 3 flatpak packages installed and that is only because they are not available in rpm form.
Flatpaks are great for their intended purpose, but it seems many are migrating from the rpm versions provided by their distro to the flatpaks. Each flatpak is mostly provided by a 3rd party and thus they are migrating from a vanilla distro to a hodgepodge of flatpaks from multiple sources.
To me this seems a recipe for less security as well as file system bloat and potential conflicts with flatpaks that may not all be packaged exactly the same.