so, this is interesting:
1. calibre-debug started without a problem despite the original calibre process still being in memory
2. when I closed the window I got a brief shutting down message, the window closed and I now have both calinbre (almost 24 h after shutdown) and calibre-debug -g in memory
3. the original process shows almost 0 CPU and memory usage now, but calibre-debug is still using 8%/10%
#1 made me realise that while the processes are not dying, they seem to be releasing the database lock and I CAN run the server after closing the GUI's window.
Do you have any ideas on why the processes are not unloading or how I could automate killing them as a workaround? Unfortunately, as the processes are staying in memory, waiting for them not to show on 'ps aux' is not working for me
calibre-debug output:
calibre 7.3 embedded-python: True
Linux-5.15.0-91-generic-x86_64-with-glibc2.35 Linux ('64bit', 'ELF')
('Linux', '5.15.0-91-generic', '#101-Ubuntu SMP Tue Nov 14 13:30:08 UTC 2023')
Python 3.11.5
Interface language: None
Successfully initialized third party plugins: Find Duplicates (1, 10, 8)
qt.qpa.xcb: X server does not support XInput 2
qt.qpa.gl: QXcbConnection: Failed to initialize GLX
qt.qpa.gl: Xcb EGL gl-integration initialize failed
QXcbIntegration: Cannot create platform OpenGL context, neither GLX nor EGL are enabled
QPA platform: xcb
devicePixelRatio: 1.0
logicalDpi: 96.0 x 96.0
physicalDpi: 96.0 x 95.9160839160839
Using calibre Qt style: True
[0.00] Starting up...
[0.00] Showing splash screen...
Falling back to using screens root_visual.
[0.98] splash screen shown
[0.98] Initializing db...
[11.16] db initialized
[11.16] Constructing main UI...
[27.16] GUI main window shown
[27.97] main UI initialized...
[27.97] Hiding splash screen
[32.50] splash screen hidden
[32.55] Started up in 32.54 seconds with 13153 books