Quote:
Originally Posted by gbm
Yes you do want to run the calibre binary from the calibre website. My system has Python 3.12.3 installed but runs calibre with no problems.
Spoiler:
Code:
~$ calibre-debug -g
calibre 7.16 embedded-python: True
Linux-6.8.0-40-generic-x86_64-with-glibc2.39 Linux ('64bit', 'ELF')
('Linux', '6.8.0-40-generic', '#40-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 5 10:34:03 UTC 2024')
Python 3.11.5
Interface language: None
EXE path: /opt/calibre/bin/calibre-debug
Successfully initialized third party plugins: ACSM Input (0, 1, 0) && DeDRM (10, 0, 9) && ACSM Input Plugin GUI Extension (0, 1, 0) && Baen (1, 1, 0) && Barnes & Noble (1, 5, 6) && Diaps Editing Toolbag (0, 4, 0) && EpubMerge (3, 1, 0) && EpubSplit (3, 8, 0) && Goodreads (1, 8, 2) && Hyphenate This! (0, 1, 3) && Set KFX metadata (from KFX Output) (2, 9, 0) && KFX Output (2, 9, 0) && KePub Metadata Reader (3, 4, 3) && KePub Metadata Writer (3, 4, 3) && KePub Output (3, 6, 11) && KindleUnpack - The Plugin (0, 83, 1) && Kobo Books (1, 10, 2) && Kobo Utilities (2, 17, 1) && Modify ePub (1, 8, 4) && Quality Check (1, 13, 14)
QPA platform: xcb
devicePixelRatio: 1.0
logicalDpi: 96.0 x 96.0
physicalDpi: 92.53889943074003 x 92.67567567567568
ApplicationPaletteChange event ignored
Using calibre Qt style: True
[0.00] Starting up...
[0.00] Showing splash screen...
[0.07] splash screen shown
[0.07] Initializing db...
[0.31] db initialized
[0.31] Constructing main UI...
DEBUG: 0.0 Kobo Utilities Configuration - CreateNewCustomColumn is supported
DEBUG: 0.0 KoboUtilites::action.py - loading translations
DEBUG: 0.0 KoboUtilites::dialogs.py - loading translations
DEBUG: 0.0 KoboUtilites::action.py - loading translations
ACSM Input: GUI Plugin Genesis!
qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile
[1.22] GUI main window shown
EpubMerge: DEBUG: 2024-08-09 13:18:43,914: calibre_plugins.epubmerge.epubmerge_plugin(156): macmenuhack file_path:/home/cocadog/.config/calibre/plugins/fanficfare_macmenuhack.txt
DEBUG: 0.7 No Kobo Touch, Glo or Mini appears to be connected
DEBUG: 0.7 rebuild_menus - self.supports_ratings=None, self.supports_tiles=None
DEBUG: 0.7 KoboUtilities:set_toolbar_button_tooltip - start: text='None'
DEBUG: 0.7 device_driver_name - could not load extended driver. Exception= No module named 'calibre_plugins.kobotouch_extended'
DEBUG: 0.7 KoboUtilities:set_toolbar_button_tooltip - setting to text='Utilities to use with Kobo ereaders
Driver: KoboTouch'
DEBUG: 0.7 device_driver_name - could not load extended driver. Exception= No module named 'calibre_plugins.kobotouch_extended'
[1.29] main UI initialized...
[1.29] Hiding splash screen
[1.53] splash screen hidden
[1.53] Started up in 1.53 seconds with 3787 books
Note that the calibre binary has its own version of python.
bernie |
Well that's horrific, glad I'm building from source to maintain a sane system. Sure is a good thing ConfigParser has had the exact same interface as SafeConfigParser
since Python 3.2 (it's probably an alias from that point on, I don't know exactly how they implemented it) while Calibre has packaged at least 3.8 since it first switched to Python 3 almost exactly four years ago (in the leadup to 5.0.0); Kobo Utilities can update the four lines using the deprecated name without affecting anyone who's not using ancient software.