Bug 416615 - krunner randomly crashes on Alt + F2
Summary: krunner randomly crashes on Alt + F2
Status: RESOLVED DUPLICATE of bug 414805
Alias: None
Product: krunner
Classification: Plasma
Component: general (show other bugs)
Version: 5.17.5
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Kai Uwe Broulik
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2020-01-22 15:12 UTC by Unknown
Modified: 2021-02-08 19:13 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
New crash information added by DrKonqi (102.16 KB, text/plain)
2020-01-22 15:12 UTC, Unknown 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Unknown 2020-01-22 15:12:51 UTC 
Application: krunner (5.17.5)

Qt Version: 5.14.0
Frameworks Version: 5.66.0
Operating System: Linux 5.4.11-arch1-1 x86_64
Distribution: "Arch Linux"

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

I had my monitors off and my KDE session locked. The computer was *not* suspended or hibernating.

I turned on my monitors, logged in and hit Alt + F2 to start krunner. It immediately crashed without showing a GUI.

The crash can be reproduced sometimes.

-- Backtrace (Reduced):
#6  0x00007f5444cd2bbc in QXcbIntegration::createPlatformOpenGLContext(QOpenGLContext*) const () at /usr/lib/libQt5XcbQpa.so.5
#7  0x00007f544a30c11e in QOpenGLContext::create() () at /usr/lib/libQt5Gui.so.5
#8  0x00007f544b8210ec in  () at /usr/lib/libQt5Quick.so.5
#9  0x00007f544b822fc4 in  () at /usr/lib/libQt5Quick.so.5
#10 0x00007f544b8273d7 in  () at /usr/lib/libQt5Quick.so.5


Possible duplicates by query: bug 416549, bug 416379, bug 416228, bug 416113, bug 416024.

Reported using DrKonqi
Comment 1 Unknown 2020-01-22 15:12:51 UTC 
Created attachment 125303 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Nate Graham 2020-01-22 22:08:57 UTC 

*** This bug has been marked as a duplicate of bug 416228 ***
Comment 3 Nate Graham 2021-02-08 19:13:58 UTC 

*** This bug has been marked as a duplicate of bug 414805 ***