Calibre was broken by Qt5 updates: --- QFactoryLoader::QFactoryLoader() checking directory path "/usr/bin/platforms" ... Cannot load library /usr/lib64/calibre/calibre/plugins/libheadless.so: (/usr/lib64/calibre/calibre/plugins/libheadless.so: symbol _ZN11QFontEngine14bitmapForGlyphEj6QFixedRK10QTransform version Qt_5_PRIVATE_API not defined in file libQt5Gui.so.5 with link time reference) QLibraryPrivate::loadPlugin failed on "/usr/lib64/calibre/calibre/plugins/libheadless.so" : "Cannot load library /usr/lib64/calibre/calibre/plugins/libheadless.so: (/usr/lib64/calibre/calibre/plugins/libheadless.so: symbol _ZN11QFontEngine14bitmapForGlyphEj6QFixedRK10QTransform version Qt_5_PRIVATE_API not defined in file libQt5Gui.so.5 with link time reference)" qt.qpa.plugin: Could not find the Qt platform plugin "headless" in "/usr/lib64/calibre/calibre/plugins" This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: headless (from /usr/lib64/calibre/calibre/plugins), eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb. --- After rebuilding the package bug was gone.
On an up-to-date system (with Qt5), I have just installed calibre to try it. It came from: media/core/release/calibre-3.42.0-2.mga7.x86_64.rpm i.e. has not yet been subject to update since M7. Under Mate: $ calibre $ It not only worked, but without any terminal errors at all; which is extremely rare. @Artem: can you imagine what might be the difference on your system? It looks as if you had calibre already installed, and as you say "was broken by Qt5 updates". Can you identify which? The command: $ rpm -qa --last | less enables you to see most recent updates/installs. Also, please say what desktop you are using.
CC: (none) => lewyssmithSource RPM: (none) => calibre-3.42.0-2.mga7.src.rpm
Sorry for the lack of details in the start message. Minimal step to reproduce subject bug is a command, for example, "ebook-convert file.pdf file.fb2". /usr/bin/ebook-convert binary belongs to calibre package. This is cli util for converting between different formats. This util uses calibre libraries. Which linked with Qt5 libs.
Thanks for the specific example. I re-installed calibre to try it: $ ebook-convert /mnt/common/docs/GuidePratiqueDeLaDefonceuse.pdf tmp/test.fb2 1% Converting input to HTML... InputFormatPlugin: PDF Input running on /mnt/common/docs/GuidePratiqueDeLaDefonceuse.pdf pdftohtml log: Document has copy-protection bit set. Page-1 Page-2 link to page 4 link to page 4 link to page 5 link to page 5 link to page 6 ... 49 link to page 49 link to page 49 Page-3 Page-4 ... Page-53 Document has copy-protection bit set. Parsing all content... 34% Running transforms on e-book... Merging user specified metadata... Detecting structure... Flattening CSS and remapping font sizes... Source base font size is 12.00000pt Removing fake margins... Cleaning up manifest... Trimming unused files from manifest... Creating FB2 Output... 67% Running FB2 Output plugin qt.qpa.plugin: Could not find the Qt platform plugin "headless" in "/usr/lib64/calibre/calibre/plugins" This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: headless (from /usr/lib64/calibre/calibre/plugins), wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb. Aborted (core dumped) --------------------- So this seemed to work well until the end, when it reproduced the last of your original output (+ a crash) from: qt.qpa.plugin: Could not find the Qt platform plugin "headless" in "/usr/lib64/calibre/calibre/plugins" > After rebuilding the package bug was gone Assigning to Stig as the active registered maintainer.
CC: lewyssmith => (none)Assignee: bugsquad => smelror
Advisory ======== A rebuild of calibre was necessary because it was unable to use certain utilities due to a new version of Qt. References ========== https://bugs.mageia.org/show_bug.cgi?id=26110 Files ===== Uploaded to core/updates_testing calibre-3.42.0-3.mga7 from calibre-3.42.0-3.mga7.src.rpm
Assignee: smelror => qa-bugs
Confirmed the ABORT and other messages here. Everything seemed to be working until 67% Running FB2 Output plugin qt.qpa.plugin: Could not find the Qt platform plugin "headless" in "/usr/lib64/calibre/calibre/plugins" Waiting for the mirrors to sync.
CC: (none) => tarazed25
I reported the announcement of the new calibre version 4.0. We should not upgrade to the new version anymore. It is possible that these problems can be avoided. You should be in backports according to <a href="https://bugs.mageia.org/show_bug.cgi?id=25527">Bug 25527</a>. But I can't find it there. Greetings!!
CC: (none) => joselp
Continuation from comment 5. Updated calibre and ran the test. $ ebook-convert TypedPHP.pdf php.fb2 InputFormatPlugin: PDF Input running on /home/lcl/docs/books/TypedPHP.pdf pdftohtml log: Syntax Warning: Invalid Font Weight [...] Rasterizing SVG images... Converting XHTML to FB2 markup... FB2 output written to /home/lcl/docs/books/php.fb2 Output saved to /home/lcl/docs/books/php.fb2 Launched calibre and imported the new ebook, php.fb2 and viewed it without any problem. Read an existing library book OK. Performed a search for books about exoplanet research and found a few from several sources. Selected one and attempted to download it in htm format but that seized up, reporting an error. Had to cancel the sub-window. Not entirely clear how that process works - not certain that it is a regression. Used the menu to convert a book from the shelf to epub 2 format and also deleted a book. In general the application is working well.
Whiteboard: (none) => MGA7-64-OK
Interesting. I used calibre recently to convert some pdf books to epub, and there were no problems that I saw. But now that I think of it, that may have been just before the QT update. Anyway... Validating. Advisory in Comment 4.
Keywords: (none) => validated_updateCC: (none) => andrewsfarm, sysadmin-bugs
It was just the download which gave trouble. The font size stuff might just be some environmental thing - at a guess.
Aachh! font weight
@Stig Thanks for the comment 4 advisory. There is no need to cite this bug number as a 'Reference'; it happens automatically.
Keywords: (none) => advisoryCC: (none) => smelror
(In reply to Lewis Smith from comment #11) > @Stig > Thanks for the comment 4 advisory. There is no need to cite this bug number > as a 'Reference'; it happens automatically. Thanks. Didn't know that :-)
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2020-0033.html
Status: NEW => RESOLVEDResolution: (none) => FIXED