https://bugs.kde.org/show_bug.cgi?id=466095
--- Comment #17 from Sven Eden <s...@eden-worx.com> --- Created attachment 159511 --> https://bugs.kde.org/attachment.cgi?id=159511&action=edit New crash information added by DrKonqi plasmashell (5.27.5) using Qt 5.15.9 DesktopView::screenToFollow() got called on a NULL pointer in my case. (See trace) Monitor in question reported not having a signal when I turned it on this morning, which was very unusual. Then it came back after 2-3 seconds and I logged into my machine being greeted by the crash reporter. The Montor is an ASUS Predator with AdaptiveSync (G-Sync compatible) running at 2k resolution @144Hz. Just one more thing: Could DrKonqi please tell its audience (me) exactly *WHEN* the crash happened? The laptop was doing work overnight, so it could've been useful to know when this happened. Not in this case, obviously, but in outhers it might. Thanks! -- Backtrace (Reduced): #6 QWeakPointer<QObject>::internalData() const (this=0x58) at /usr/include/qt5/QtCore/qsharedpointer_impl.h:696 #7 QPointer<QScreen>::data() const (this=0x58) at /usr/include/qt5/QtCore/qpointer.h:77 #8 QPointer<QScreen>::operator QScreen*() const (this=0x58) at /usr/include/qt5/QtCore/qpointer.h:83 #9 DesktopView::screenToFollow() const (this=0x0) at /data/portage/portage/kde-plasma/plasma-workspace-5.27.5/work/plasma-workspace-5.27.5/shell/desktopview.cpp:124 #10 0x000055a2a9a685c0 in ShellCorona::screenInvariants() const (this=0x55a2aa4f3670) at /data/portage/portage/kde-plasma/plasma-workspace-5.27.5/work/plasma-workspace-5.27.5/shell/shellcorona.cpp:828 -- You are receiving this mail because: You are watching all bug changes.
