Bug 458600 - Plasma Crash when turning off monitor in multi-monitor setup
Summary: Plasma Crash when turning off monitor in multi-monitor setup
Status: RESOLVED DUPLICATE of bug 458153
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 5.25.4
Platform: Neon Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2022-09-01 15:05 UTC by Tom F
Modified: 2022-09-01 15:10 UTC (History)
2 users (show)

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


Attachments
New crash information added by DrKonqi (82.39 KB, text/plain)
2022-09-01 15:05 UTC, Tom F
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tom F 2022-09-01 15:05:11 UTC
Application: plasmashell (5.25.4)

Qt Version: 5.15.5
Frameworks Version: 5.97.0
Operating System: Linux 5.15.0-46-generic x86_64
Windowing System: X11
Distribution: KDE neon User - 5.25
DrKonqi: 5.25.4 [KCrashBackend]

-- Information about the crash:
If I'm going to be away from my desk I turn off my displays. Upon return I'm informed Plasma has crashed.

The reporter is unsure if this crash is reproducible.

-- Backtrace (Reduced):
#6  0x00007f82f16cd9d5 in QFutureWatcherBase::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007f82f25dce83 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8  0x00007f82f25e5c98 in QApplication::notify(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x00007f82f18a9c6a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f82f18ac571 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5


Reported using DrKonqi
Comment 1 Tom F 2022-09-01 15:05:12 UTC
Created attachment 151763 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Nicolas Fella 2022-09-01 15:10:38 UTC

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