Anki does not quit properly on Linux

I’m using Anki 24.04.1 on Manjaro Linux(GNOME, Wayland). Anki works ok but does not quit properly after clicking “x”. The window does close but the process remains and a exception was logged in the terminal:

Preparing to run...
Qt warning: QGuiApplication::setDesktopFileName: the specified desktop file name ends with .desktop. For compatibility reasons, the .desktop suffix will be removed. Please specify a desktop file name without .desktop suffix 
2024-06-04 08:27:20,107:INFO:aqt.mediasrv: Serving on http://127.0.0.1:34307
Qt warning: Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/bin/qtwebengine_dictionaries' 
Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/lib/qt6/qtwebengine_dictionaries'
Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/lib/qt6/qtwebengine_dictionaries'
libva error: /usr/lib/dri/i965_drv_video.so init failed
Starting main loop...
Window should have been closed: <aqt.progress.ProgressDialog object at 0x7f1c902be7b0>
2024-06-04 08:27:28,307:WARNING:waitress: unhandled close event
Error in sys.excepthook:
TypeError: 'NoneType' object is not callable

Original exception was:
Traceback (most recent call last):
  File "/usr/lib/python3.12/site-packages/aqt/taskman.py", line 142, in _on_closures_pending
    closure()
  File "/usr/lib/python3.12/site-packages/aqt/taskman.py", line 86, in <lambda>
    lambda future: self.run_on_main(lambda: on_done(future))
                                            ^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/aqt/progress.py", line 239, in do_window_cleanup
    self._busy_cursor_timer.stop()
RuntimeError: wrapped C/C++ object of type QTimer has been deleted
^CIgnored progress func as collection unloaded: <function AnkiQt.onUnixSignal.<locals>.quit at 0x7f1c90256fc0>
^CIgnored progress func as collection unloaded: <function AnkiQt.onUnixSignal.<locals>.quit at 0x7f1c90256fc0>

I installed Anki by a script from AUR (aur/anki), which builds Anki from source.

Thanks! That’s a known issue and a fix is already in the pipeline.

1 Like