Bug 480283 - Plasma crash
Summary: Plasma crash
Status: RESOLVED DUPLICATE of bug 468430
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.27.10
Platform: unspecified Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2024-01-24 18:14 UTC by Krzysztof Cybulski
Modified: 2024-01-29 15:18 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (144.25 KB, text/plain)
2024-01-24 18:14 UTC, Krzysztof Cybulski
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Krzysztof Cybulski 2024-01-24 18:14:23 UTC
Application: plasmashell (5.27.10)

Qt Version: 5.15.12
Frameworks Version: 5.114.0
Operating System: Linux 6.6.6-t2-jammy x86_64
Windowing System: X11
Distribution: KDE neon 5.27
DrKonqi: 5.27.10 [CoredumpBackend]

-- Information about the crash:
Hi, 

I'm unsure when this error occurs, it's shows after I powered my monitors (all 3 of them) and then turn them back on. I don't know if this occurs when monitors of powered down or when powered up.

The reporter is unsure if this crash is reproducible.

-- Backtrace (Reduced):
#6  QWeakPointer<QObject>::internalData (this=0x60) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qsharedpointer_impl.h:702
#7  QPointer<QScreen>::data (this=0x60) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qpointer.h:77
#8  QPointer<QScreen>::operator QScreen* (this=0x60) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qpointer.h:83
#9  DesktopView::screenToFollow (this=0x0) at ./shell/desktopview.cpp:123
#10 0x000056346631e5cf in ShellCorona::screenInvariants (this=0x56346704cdb0) at ./shell/shellcorona.cpp:828


Reported using DrKonqi
Comment 1 Krzysztof Cybulski 2024-01-24 18:14:24 UTC
Created attachment 165196 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Akseli Lahtinen 2024-01-29 15:18:51 UTC

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