Bug 417129 - Random crash on alt-f2
Summary: Random crash 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
Keywords: drkonqi
Depends on:
Reported: 2020-02-04 08:07 UTC by charly ghislain
Modified: 2021-02-08 19:13 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

New crash information added by DrKonqi (66.38 KB, text/plain)
2020-02-04 08:08 UTC, charly ghislain

Note You need to log in before you can comment on or make changes to this bug.
Description charly ghislain 2020-02-04 08:07:59 UTC
Application: krunner (5.17.5)

Qt Version: 5.14.1
Frameworks Version: 5.66.0
Operating System: Linux 5.4.15-arch1-1 x86_64
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:
I pressed ALT+F2

Then kwin crash.

I run on an laptop with two video chips. Im running on the dedicated nvidia chip while experncing this bug although it may not be related.

The crash can be reproduced sometimes.

-- Backtrace (Reduced):
#6  0x00007fec80a5ea84 in QScreen::handle() const () at /usr/lib/libQt5Gui.so.5
#7  0x00007fec7b451bbc in QXcbIntegration::createPlatformOpenGLContext(QOpenGLContext*) const () at /usr/lib/libQt5XcbQpa.so.5
#8  0x00007fec80a7835e in QOpenGLContext::create() () at /usr/lib/libQt5Gui.so.5
#9  0x00007fec81f904cc in  () at /usr/lib/libQt5Quick.so.5
#10 0x00007fec81f923a4 in  () at /usr/lib/libQt5Quick.so.5

The reporter indicates this bug may be a duplicate of or related to bug 416228.

Possible duplicates by query: bug 416615, bug 416228, bug 414709, bug 411787, bug 410376.

Reported using DrKonqi
Comment 1 charly ghislain 2020-02-04 08:08:00 UTC
Created attachment 125653 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Nate Graham 2020-02-05 20:58:14 UTC

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

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