Hi all, Thanks for tracking this bug. I couldn't reproduce it on Debian unstable with Debian-provided PyQt. But it reliably fails when installing PyQt5 from PyPi.
Based on other reports the key problem is the cleanup of Qt widgets. Some sources suggest to remove all widgets in the right order bottom-up, but for our case just removing the main (and only) window was enough: del app.main_window Here a PR to fix this by adding a more complete cleanup function: https://github.com/borgbase/vorta/pull/877/files If possible, please let me know if this resolves the issue everywhere. Manu > On Dec 28, 2020, at 02:16, Nicholas D Steeves <nstee...@gmail.com> wrote: > > Control: tag -1 confirmed > > Hi Sandro, > > Thank you for the bug report, always appreciated! :-) Reply follows > inline: > > On Fri, Dec 25, 2020 at 10:21:40PM -0500, Sandro Tosi wrote: >> Package: vorta >> Version: 0.7.1-2 >> Severity: normal >> Forwarded: https://github.com/borgbase/vorta/issues/456 >> >> Hello, >> when i close vorta, it SIGEGV. Attached is a gdb run that shows the problem + >> some debugging commands (but i dont really know how useful that may be). >> >> Upstream had this reported at https://github.com/borgbase/vorta/issues/456 >> but >> got closed for lack of updates. It may be due to specific circumstances only >> happening on recent debian systems? >> >> Regards, >> Sandro >> > [snip] > >> $ gdb python3 > [snip] >> >> Thread 1 "python3" received signal SIGSEGV, Segmentation fault. >> 0x00007ffff1ead7e7 in QWidget::~QWidget() () from >> /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 >> (gdb) bt >> #0 0x00007ffff1ead7e7 in QWidget::~QWidget() () at >> /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 >> #1 0x00007ffff21f7e1d in () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 >> #2 0x00007ffff21f7502 in () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 >> #3 0x00007ffff21d7d7b in QSystemTrayIcon::~QSystemTrayIcon() () at >> /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 >> #4 0x00007ffff2521d19 in sipQSystemTrayIcon::~sipQSystemTrayIcon() >> (this=0x13c2ba0, __in_chrg=<optimized out>) at >> ./build-3.9/QtWidgets/sipQtWidgetspart1.cpp:52811 >> #5 0x00007ffff59fdb3e in QObjectPrivate::deleteChildren() () at >> /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 >> #6 0x00007ffff5a08714 in QObject::~QObject() () at >> /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 >> #7 0x00007ffff27115e9 in sipQApplication::~sipQApplication() >> (this=0x121a8f0, __in_chrg=<optimized out>) at >> ./build-3.9/QtWidgets/sipQtWidgetspart9.cpp:17016 >> #8 0x00007ffff5e827ad in cleanup_on_exit(PyObject*, PyObject*) () at >> ../../qpy/QtCore/qpycore_init.cpp:44 >> #9 0x000000000052607e in cfunction_vectorcall_NOARGS (func=<built-in >> function _qtcore_cleanup>, args=<optimized out>, nargsf=<optimized out>, >> kwnames=<optimized out>) at ../Objects/methodobject.c:485 > > I was able to reproduce this with 1. Open vorta from konsole, 2. Run > backup (remote repo via SSH), 3. Backup succeeds, 4. Close vorta from > tray. 5. SIGEGV > > I also noticed some xcb-related debug output in the area of the window > used for updating the state of a backup operation, and I suspect this > may provide a clue about where to look next, and I'll consult the > QT/KDE Team to see if there are any known issues in our PyQt5. > > Merry Christmas and Happy New Year, > Nicholas
