| Summary: | Segmentation fault with shortcuts | ||
|---|---|---|---|
| Product: | [Applications] peruse | Reporter: | wolthera <griffinvalley> |
| Component: | general | Assignee: | Dan Leinir Turthra Jensen <admin> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | crash | CC: | nicolas.fella |
| Priority: | NOR | ||
| Version First Reported In: | master | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | https://codereview.qt-project.org/c/qt/qtdeclarative/+/371842 | Version Fixed/Implemented In: | |
| Sentry Crash Report: | |||
|
Description
wolthera
2021-05-31 16:24:08 UTC
Got the other crash. What is shared between these two is that they're both related to shortcuts as well as both seem to happen once you open a second book after the first one. Slightly different backtrace: Thread 1 (Thread 0x7ffff20c78c0 (LWP 1303170)): #0 0x00007ffff08c8b64 in QQuickShortcutContext::matcher(QObject*, Qt::ShortcutContext) () from /usr/lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5 #1 0x00007ffff683974f in QShortcutMap::find(QKeyEvent*, int) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #2 0x00007ffff683c524 in QShortcutMap::nextState(QKeyEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #3 0x00007ffff683d7c9 in QShortcutMap::tryShortcut(QKeyEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #4 0x00007ffff67eac72 in QWindowSystemInterface::handleShortcutEvent(QWindow*, unsigned long, int, QFlags<Qt::KeyboardModifier>, unsigned int, unsigned int, unsigned int, QString const&, bool, unsigned short) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #5 0x00007ffff680a881 in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #6 0x00007ffff680fb3b in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #7 0x00007ffff67e77ac in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #8 0x00007ffff1cb5d7e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #9 0x00007ffff4c2317d in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x00007ffff4c23400 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x00007ffff4c234a3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x00007ffff6486fe2 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x00007ffff642b1eb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x00007ffff6433394 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x000055555555b92f in PeruseHelpers::init (path=..., app=..., filename=...) at /home/wolthera/Peruse/src/src/common/peruse_helpers.cpp:106 #16 0x0000555555559bb7 in main (argc=1, argv=0x7fffffffe1f8) at /home/wolthera/Peruse/src/src/app/main.cpp:84 (gdb) *** Bug 431943 has been marked as a duplicate of this bug. *** This is an upstream bug in Qt which was fixed with https://codereview.qt-project.org/c/qt/qtdeclarative/+/371842. It will be backported to the KDE patch collection soon; see https://invent.kde.org/qt/qt/qtquickcontrols2/-/merge_requests/3 Thanks so much to Nicolas Fella for discovering this and backporting it! |