Package: libqt5dbus5 Version: 5.12.5+dfsg-9 Severity: normal Dear Maintainer,
while debugging another crash with valgrind, I noticed errors of invalid access in the thread used by QDBus. It seems the event loop is still expecting input on a socket, whose socket notifier should have been deleted and unregistered. Note that this is not directly related to the other crash, or at least I don't know how it could be (if anything, it should cause a deadlock). The backtrace is here:
binwJOEX1RwcK.bin
Description: Binary data
Do you have any ideas why this could be?
Regards
Jiri Palecek
-- System Information:
Debian Release: 10.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1,
'experimental')
Architecture: i386 (i686)
Foreign Architectures: amd64
Kernel: Linux 5.5.0-rc5-686-pae (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ (charmap=ISO-8859-2), LANGUAGE=cs_CZ
(charmap=ISO-8859-2)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages libqt5dbus5 depends on:
ii libc6 2.29-8
ii libdbus-1-3 1.12.16-2
ii libqt5core5a [qtbase-abi-5-12-5] 5.12.5+dfsg-9
ii libstdc++6 10-20200222-1
libqt5dbus5 recommends no packages.
libqt5dbus5 suggests no packages.
-- no debconf information
