Summary: | Discover 5.12.0 always Crashes in QQuickItem::isVisible() following these simple steps | ||
---|---|---|---|
Product: | [Applications] Discover | Reporter: | RYDeN <rydenpf> |
Component: | discover | Assignee: | Aleix Pol <aleixpol> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | andrewcodes, epost.kde, nate, scott |
Priority: | NOR | ||
Version: | 5.12.0 | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | https://commits.kde.org/discover/12138479ca378d4e36fb0e9b6dcc5ecef88ab200 | Version Fixed In: | 5.12.1 |
Sentry Crash Report: | |||
Attachments: | Downloaded updates |
Description
RYDeN
2018-02-08 23:33:13 UTC
Thanks for the PERFECT bug report! Can confirm, this is a 100% crasher Happens for me on Neon with Qt 5.9.3 and Kubuntu with Qt 5.9.1. The backtrace indicates that it's in QQuickItem::isVisible(), which is a known issue. Thread 1 "plasma-discover" received signal SIGSEGV, Segmentation fault. 0x00007ffff723fbd4 in QQuickItem::isVisible() const () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 (gdb) bt #0 0x00007ffff723fbd4 in QQuickItem::isVisible() const () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #1 0x00007ffff723fccd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #2 0x00007ffff724bdd7 in QQuickItemPrivate::deliverKeyEvent(QKeyEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #3 0x00007ffff724c185 in QQuickItem::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x00007ffff554eb9c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #5 0x00007ffff55565a7 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #6 0x00007ffff3f5fdf8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x00007ffff725cdbd in QQuickWindow::sendEvent(QQuickItem*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x00007ffff725d07f in QQuickWindow::keyReleaseEvent(QKeyEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x00007ffff4dec8e5 in QWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #10 0x00007ffff7264e85 in QQuickWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x00007ffff554eb9c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x00007ffff55565a7 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x00007ffff3f5fdf8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x00007ffff4ddcdd8 in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #15 0x00007ffff4de2175 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #16 0x00007ffff4dbb7cb in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #17 0x00007fffe74dd470 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #18 0x00007fffee0ae197 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x00007fffee0ae3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x00007fffee0ae49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x00007ffff3fb56af in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x00007ffff3f5de2a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x00007ffff3f66d64 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x00000000004162a8 in main () *** This bug has been marked as a duplicate of bug 378339 *** Yes, can reproduce. Will look into it. Git commit 12138479ca378d4e36fb0e9b6dcc5ecef88ab200 by Aleix Pol. Committed on 09/02/2018 at 01:24. Pushed by apol into branch 'Plasma/5.12'. Make sure we mark as busy before clearling the list We use this signal to clear the view, we want the currentItem to be clean before the Workarounds QTBUG-65881 M +1 -1 libdiscover/resources/ResourcesProxyModel.cpp https://commits.kde.org/discover/12138479ca378d4e36fb0e9b6dcc5ecef88ab200 *** Bug 390083 has been marked as a duplicate of this bug. *** *** Bug 389910 has been marked as a duplicate of this bug. *** Created attachment 110497 [details]
Downloaded updates
I downloaded the Discover updates on KDE Neon 5.12 Git-stable, and followed the same 9 steps, and the crash is still there. See the attachment (Downloaded updates). Your version won't have that fix yet. I can confirm that this is fixed in KDE Neon with Discover built from source. However, while those Steps To Reproduce no longer cause a crash, the second search now doesn't work. Tracking that in Bug 390191. *** Bug 390196 has been marked as a duplicate of this bug. *** |