Bug 435770 - Crash when loging out
Summary: Crash when loging out
Status: RESOLVED FIXED
Alias: None
Product: krunner
Classification: Plasma
Component: general (show other bugs)
Version: 5.19.5
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Alexander Lohnau
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2021-04-15 13:20 UTC by John Werner
Modified: 2021-05-19 16:19 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
New crash information added by DrKonqi (2.89 KB, text/plain)
2021-05-19 14:43 UTC, Dmitry
Details

Note You need to log in before you can comment on or make changes to this bug.
Description John Werner 2021-04-15 13:20:55 UTC
Application: krunner (5.19.5)

Qt Version: 5.14.2
Frameworks Version: 5.74.0
Operating System: Linux 5.8.0-49-lowlatency x86_64
Windowing system: X11
Distribution: Ubuntu 20.10

-- Information about the crash:
- What I was doing when the application crashed:

Logging out of KDE session
1. clicked KDE's "start menu" button
2. selected "Leave"
3. selected "Log Out"
4. crash.

This was tried 3 times in the same session with the same result.

- Unusual behavior I noticed:

Open GL drivers disappeared. May be related to recent 'apt dist-upgrade'.

The crash can be reproduced sometimes.

-- Backtrace:
Application: krunner (krunner), signal: Aborted

[KCrash Handler]
#4  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
#5  0x00007fb8920a8864 in __GI_abort () at abort.c:79
#6  0x00007fb8924dbba3 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007fb89403eade in QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#8  0x00007fb89404098e in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#9  0x00007fb89404177b in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#10 0x00007fb892ad77c5 in QWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#11 0x000055c06c41e253 in ?? ()
#12 0x00007fb89323a013 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007fb8926f81ca in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007fb892acc9a1 in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#15 0x00007fb892aa12bb in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#16 0x00007fb88dda235e in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#17 0x00007fb890cc962b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007fb890cc98d8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007fb890cc99a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007fb89274f843 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007fb8926f6a4b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007fb8926fefc6 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x000055c06c41ca70 in ?? ()
#24 0x00007fb8920aacb2 in __libc_start_main (main=0x55c06c41c4a0, argc=1, argv=0x7ffe7d504f38, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffe7d504f28) at ../csu/libc-start.c:314
#25 0x000055c06c41cbce in _start ()
[Inferior 1 (process 214026) detached]

Possible duplicates by query: bug 430419, bug 429344, bug 427384, bug 426250, bug 425662.

Reported using DrKonqi
Comment 1 Nate Graham 2021-04-16 16:40:41 UTC
> QSGRenderLoop::handleContextCreationFailure
Yes this means your graphics drivers are messed up after upgrading and things won't work right until after a reboot.

We have code to work around this (see https://invent.kde.org/frameworks/kdeclarative/-/merge_requests/37), but perhaps KRunner isn't using the init function that goes through that codepath?
Comment 2 Dmitry 2021-05-19 14:43:26 UTC
Created attachment 138565 [details]
New crash information added by DrKonqi

krunner (5.19.5) using Qt 5.14.2

- What I was doing when the application crashed:
Just pressed CTRL+space.
Also, if i am running "krunner" from terminal, this is caues same error.

-- Backtrace (Reduced):
#4  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
#5  0x00007f8814497864 in __GI_abort () at abort.c:79
#6  0x00007f88148caba3 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007f881642dade in QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
[...]
#10 0x00007f8814ec67c5 in QWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
Comment 3 Nate Graham 2021-05-19 16:19:02 UTC
Oh, actually it's that you're using an old version where it's not fixed yet. :)