Bug 477204 - plasmashell crash after waking up from standby
Summary: plasmashell crash after waking up from standby
Status: RESOLVED DUPLICATE of bug 476847
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (show other bugs)
Version: 5.27.80
Platform: Other Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi, qt6
Depends on:
Blocks:
 
Reported: 2023-11-18 19:41 UTC by Enrico
Modified: 2023-11-22 14:42 UTC (History)
1 user (show)

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


Attachments
New crash information added by DrKonqi (88.27 KB, text/plain)
2023-11-18 19:42 UTC, Enrico
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Enrico 2023-11-18 19:41:59 UTC
Application: plasmashell (5.27.80)

Qt Version: 6.6.0
Frameworks Version: 5.245.0
Operating System: Linux 6.5.11-1 x86_64
Windowing System: Wayland
Distribution: KaOS (2023)
DrKonqi: 5.27.80 [CoredumpBackend]

-- Information about the crash:
Hello, plasmashell crashes everytime I wake up the computer from the standby. I can reproduce it everytime.
Now I'm on KaOS with Plasma 6, but I can reproduce it on Neon Unstable, too.

The crash can be reproduced every time.

-- Backtrace (Reduced):
#5  0x00007f670a629c5d in PlasmaQuick::ContainmentView::containment() const () at /usr/lib/libKF6PlasmaQuick.so.6
[...]
#8  0x00007f6708007312 in QWindow::visibleChanged(bool) () at /usr/lib/libQt6Gui.so.6
#9  0x00007f670800c07a in QWindow::setVisible(bool) () at /usr/lib/libQt6Gui.so.6
#10 0x00007f670800c4a7 in QWindowPrivate::destroy() () at /usr/lib/libQt6Gui.so.6
#11 0x00007f670800c69f in QWindow::~QWindow() () at /usr/lib/libQt6Gui.so.6


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

Reported using DrKonqi
Comment 1 Enrico 2023-11-18 19:42:00 UTC
Created attachment 163276 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Bharadwaj Raju 2023-11-22 14:42:57 UTC
*** This bug has been marked as a duplicate of bug 476847 ***