Repository navigation
Closed as duplicate
Description
What did you do?
I put the window in the background and brought it back to the foreground. I had loaded a database and edited some queries before.
What did you expect to see?
The content that was in there before
What did you see instead?
A crash. I started it in gdb and got this output:
Thread 6 "QDBusConnection" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffea7fc6c0 (LWP 164439)]
0x00007ffff631b897 in QHashData::nextNode(QHashData::Node*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
(gdb) bt
#0 0x00007ffff631b897 in QHashData::nextNode(QHashData::Node*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#1 0x00007ffff284b764 in ??? () at /lib/x86_64-linux-gnu/libQt5DBus.so.5
#2 0x00007ffff284bd3e in ??? () at /lib/x86_64-linux-gnu/libQt5DBus.so.5
#3 0x00007ffff28502c9 in ??? () at /lib/x86_64-linux-gnu/libQt5DBus.so.5
#4 0x00007ffff2850ba0 in ??? () at /lib/x86_64-linux-gnu/libQt5DBus.so.5
#5 0x00007ffff2219899 in dbus_connection_dispatch () at /lib/x86_64-linux-gnu/libdbus-1.so.3
#6 0x00007ffff2850639 in ??? () at /lib/x86_64-linux-gnu/libQt5DBus.so.5
#7 0x00007ffff2850a5f in ??? () at /lib/x86_64-linux-gnu/libQt5DBus.so.5
#8 0x00007ffff651893e in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#9 0x00007ffff651c1a3 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007ffff651c9e3 in QSocketNotifier::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007ffff64dde65 in QCoreApplication::notifyInternal2(QObject*, QEvent*) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007ffff653baad in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007ffff4b04385 in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x00007ffff4b065b7 in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x00007ffff4b06d20 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007ffff653aeed in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007ffff64dc802 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007ffff62dd990 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x00007ffff283c7cb in ??? () at /lib/x86_64-linux-gnu/libQt5DBus.so.5
#20 0x00007ffff62dec21 in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007ffff5c9db7b in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:448
#22 0x00007ffff5d1b7b8 in __GI___clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
I got this crash two times today.
DB4S Version
3.13.0
What OS are you seeing the problem on?
Linux
OS version
LMDE 7
Relevant log output
Version in Package: 3.13.0-1+b1
Version in About: 3.13.99 (Apr 11 2025), Qt Version 5.15.15Prevention against duplicate issues
- I have searched for similar issues
Metadata
Metadata
Assignees
Labels
No labels
Activity
FriedrichFroebel commentedon Jan 15, 2026
How does this differ from your reports in #3267?
Jonny007-MKD commentedon Jan 15, 2026
Well, I did not build it myself this time, and had a major OS update in between. But it's true that I didn't notice my second callstack in #3267. Sorry!