SUMMARIZING EDIT: The problem (Calibre or its Editor appears to not run when launched, but uses 10% of CPU in the background (in both Windows 10 22H2 and Windows 11 22H2)) isn't solved, but it looks like it's being caused by the more current AMD graphics drivers or their software (I'm currently on Adrenalin 22.12.2 (12/08/2022), according to Device Manager, that's driver version 31.0.12029.10015 (11/30/2022). I uninstalled them and Windows is running with whatever it defaults to for a driver (no Adrenalin software and Device Manager says version 31.0.12027.7000 released on 10/20/2022). The issue with Calibre no longer seems to happen (a couple of dozen T / ALT-F4 cycles (to ediT a book and quit the editor)). I started noticing this with their previous Adrenalin drivers (Adrenalin 22.11.1, released 11/15/2022). At one point, I had hopes that adding an environment variable to turn off GPU hardware acceleration in QT Web Engine would fix this. But, it doesn't. Ditto for exempting Calibre from Windows Security).
EDIT: SOLVED? I backed everything up and uninstalled Calibre. I then rebooted Windows and re-installed Calibre (easy-peasy). It now seems to run just fine. I have no idea what happened to cause the problem I documented below. But, hopefully, all will remain right with the world.
OP:
This is very weird. Suddenly, I'm having trouble launching Calibre. If I use my desktop shortcut (Windows 11), it doesn't appear to launch (i.e., the program doesn't appear). But, if I check Task Manager, Calibre is furiously churning away and taking up over 10% of my CPU. If I use my shortcut again, the program does pop up (once). If I close the program normally, the window goes away, but that 10% using entry for it in Task Manager stays running. If I end that task, it goes away.
If I open a Terminal (PowerShell) window and run calibre-debug -g, calibre pops up immediately with no issues and in Task Manager show up in an entry for "Command line interface for calibre debugging/development" and is using hardly any resources (which, I believe, is normal). Here's the log while it's running:
Code:
calibre-debug -g pwsh 20:55:03
calibre 6.8 embedded-python: True
Windows-10-10.0.22000-SP0 Windows ('64bit', 'WindowsPE')
('Windows', '10', '10.0.22000')
Python 3.10.1
Windows: ('10', '10.0.22000', 'SP0', 'Multiprocessor Free')
Interface language: None
Successfully initialized third party plugins: DeACSM (0, 0, 16) && DeDRM (10, 0, 3) && Diaps Editing Toolbag (0, 4, 0) && EpubCheck (0, 2, 4) && EpubSplit (3, 5, 0) && Goodreads (1, 7, 1) && KindleUnpack - The Plugin (0, 83, 1) && Kobo Utilities (2, 16, 6) && KoboTouchExtended (3, 6, 3) && Modify ePub (1, 8, 1) && Quality Check (1, 13, 2) && ScrambleEbook (0, 6, 0)
QPA platform: windows
devicePixelRatio: 1.25
logicalDpi: 96.0 x 96.0
physicalDpi: 87.37599999999999 x 87.34567164179104
ApplicationPaletteChange event ignored
Using calibre Qt style: True
[0.00] Starting up...
[0.02] Initializing db...
[0.05] db initialized
[0.05] 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
qt.webengine.QWebEngineView OK
Screens currently in system:
{'depth': 32,
'device_pixel_ratio': 1.25,
'geometry_in_logical_pixels': {'height': 1152, 'width': 2752, 'x': 0, 'y': 0},
'index_in_screens_list': 0,
'manufacturer': '',
'model': '',
'name': '\\\\.\\DISPLAY1',
'serial': '',
'size_in_logical_pixels': {'height': 1152, 'width': 2752},
'virtual_geometry': {'height': 1152, 'width': 2752, 'x': 0, 'y': 0}}
Restoring geometry for: calibre_main_window_geometry
{'frame_geometry': {'height': 1100, 'width': 2648, 'x': 90, 'y': 0},
'full_screened': False,
'geometry': {'height': 1070, 'width': 2648, 'x': 90, 'y': 30},
'maximized': False,
'normal_geometry': {'height': 1070, 'width': 2648, 'x': 90, 'y': 30},
'screen': {'depth': 32,
'device_pixel_ratio': 1.25,
'geometry_in_logical_pixels': {'height': 1152,
'width': 2752,
'x': 0,
'y': 0},
'index_in_screens_list': 0,
'manufacturer': '',
'model': '',
'name': '\\\\.\\DISPLAY1',
'serial': '',
'size_in_logical_pixels': {'height': 1152, 'width': 2752},
'virtual_geometry': {'height': 1152,
'width': 2752,
'x': 0,
'y': 0}}}
Matching screen: {'depth': 32,
'device_pixel_ratio': 1.25,
'geometry_in_logical_pixels': {'height': 1152, 'width': 2752, 'x': 0, 'y': 0},
'index_in_screens_list': 0,
'manufacturer': '',
'model': '',
'name': '\\\\.\\DISPLAY1',
'serial': '',
'size_in_logical_pixels': {'height': 1152, 'width': 2752},
'virtual_geometry': {'height': 1152, 'width': 2752, 'x': 0, 'y': 0}}
Setting widget geometry to: {'height': 1070, 'width': 2648, 'x': 90, 'y': 30}
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 KoboUtilities:set_toolbar_button_tooltip - setting to text='Utilities to use with Kobo ereaders
Driver: KoboTouchExtended'
[0.89] main UI initialized...
[0.89] Started up in 0.89 seconds with 651 books
Starting QuickView
Upon quitting Calibre, here's the remainder of the output:
Code:
Saving geometry for: calibre_main_window_geometry
{'frame_geometry': {'height': 1100, 'width': 2648, 'x': 90, 'y': 0},
'full_screened': False,
'geometry': {'height': 1070, 'width': 2648, 'x': 90, 'y': 30},
'maximized': False,
'normal_geometry': {'height': 1070, 'width': 2648, 'x': 90, 'y': 30},
'screen': {'depth': 32,
'device_pixel_ratio': 1.25,
'geometry_in_logical_pixels': {'height': 1152,
'width': 2752,
'x': 0,
'y': 0},
'index_in_screens_list': 0,
'manufacturer': '',
'model': '',
'name': '\\\\.\\DISPLAY1',
'serial': '',
'size_in_logical_pixels': {'height': 1152, 'width': 2752},
'virtual_geometry': {'height': 1152,
'width': 2752,
'x': 0,
'y': 0}}}
That all looks fine to me.
AFAIK, the only things I've changed since last running Calibre a couple of days ago are an update to my AMD Adrenalin graphics driver and the AMD chipset drivers. I suppose those could cause weird things, but this just seems a bit outside their demesne.
Here's my system:
Code:
Computer: GIGABYTE B550 VISION D-P
CPU: AMD Ryzen 5 5600X (Vermeer, VMR-B0)
3700 MHz (37.00x100.0) @ 3685 MHz (36.92x99.8)
Motherboard: GIGABYTE B550 VISION D-P
BIOS: F15d, 07/20/2022
Chipset: AMD B550 (Promontory PROM19 C)
Memory: 16384 MBytes @ 1597 MHz, 14-14-14-34
- 8192 MB PC25600 DDR4 SDRAM - G.Skill F4-3200C14-8GFX
- 8192 MB PC25600 DDR4 SDRAM - G.Skill F4-3200C14-8GFX
Graphics: AMD Radeon RX 6800 XT
AMD Radeon RX 6800 XT, 16384 MB GDDR6 SDRAM
Drive: KINGSTON SKC3000D2048G, 2000.4 GB, NVMe
Sound: ATI/AMD Navi2x - High Definition Audio Controller
Sound: AMD Family 17h/19h - HD Audio Controller
Network: RealTek Semiconductor RTL8125 Gaming 2.5GbE Family Ethernet Controller
Network: Intel Wi-Fi 6 AX200 160MHz
OS: Microsoft Windows 11 Professional (x64) Build 22000.1098 (21H2)
I can't imagine this is a Calibre issue since I've been running version 6.8 for several weeks now without issue. But, I thought I'd put this here in case anyone else is seeing something like it or has an idea what to do.