Details
-
Bug
-
Resolution: Done
-
P1: Critical
-
5.5.1
-
None
-
Debian GNU/Linux unstable
-
a094af001795c9651b299d700a992150d1aba33a
Description
Forwarded from https://bugs.debian.org/804694:
Applications that are based on Qt can crash with a SIGSEGV.
This happens on owncloud-client and quasselclient, others maybe as well, but not yet stacktraced.
Here is a backtrace for quasselclient.
Program received signal SIGSEGV, Segmentation fault. 0x00007fffe1a6e94f in QXcbWindow::handleClientMessageEvent (this=0x555555da6f80, event=0x7fffd8003e00) at qxcbwindow.cpp:1942 1942 qxcbwindow.cpp: No such file or directory. (gdb) bt #0 0x00007fffe1a6e94f in QXcbWindow::handleClientMessageEvent (this=0x555555da6f80, event=0x7fffd8003e00) at qxcbwindow.cpp:1942 #1 0x00007fffe1a59b2b in QXcbConnection::handleXcbEvent (this=this@entry=0x555555b9bdd0, event=event@entry=0x7fffd8003e00) at qxcbconnection.cpp:1066 #2 0x00007fffe1a5a053 in QXcbConnection::processXcbEvents (this=0x555555b9bdd0) at qxcbconnection.cpp:1502 #3 0x00007ffff2e777f1 in QObject::event (this=0x555555b9bdd0, e=<optimized out>) at kernel/qobject.cpp:1239 #4 0x00007ffff373c9dc in QApplicationPrivate::notify_helper (this=this@entry=0x555555b91110, receiver=receiver@entry=0x555555b9bdd0, e=e@entry=0x7fffd80035b0) at kernel/qapplication.cpp:3716 #5 0x00007ffff3741ea6 in QApplication::notify (this=0x7fffffffdc00, receiver=0x555555b9bdd0, e=0x7fffd80035b0) at kernel/qapplication.cpp:3499 #6 0x00007ffff2e47dbb in QCoreApplication::notifyInternal (this=0x7fffffffdc00, receiver=0x555555b9bdd0, event=event@entry=0x7fffd80035b0) at kernel/qcoreapplication.cpp:965 #7 0x00007ffff2e4a1b6 in QCoreApplication::sendEvent (event=0x7fffd80035b0, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:224 #8 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x555555b8dbf0) at kernel/qcoreapplication.cpp:1593 #9 0x00007ffff2e4a698 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1451 #10 0x00007ffff2e9e163 in postEventSourceDispatch (s=0x555555bc2d50) at kernel/qeventdispatcher_glib.cpp:271 #11 0x00007ffff08bdfe7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x00007ffff08be240 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x00007ffff08be2ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x00007ffff2e9e56f in QEventDispatcherGlib::processEvents (this=0x555555bc2aa0, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #15 0x00007ffff2e4554a in QEventLoop::exec (this=this@entry=0x7fffffffdb60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #16 0x00007ffff2e4d62c in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1229 #17 0x0000555555671736 in main ()
The reporter says this didn't happen with Qt 5.4.
Attachments
Issue Links
- relates to
-
QTBUG-42985 Qt GUI application disappear or crash when no screens are available
- Closed