Bug 500806 - Plasmashell crashed when waking up from suspend in dual monitor setup
Summary: Plasmashell crashed when waking up from suspend in dual monitor setup
Status: RESOLVED DUPLICATE of bug 499383
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (other bugs)
Version First Reported In: 6.3.0
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-27 10:31 UTC by Benjamin Dedieu
Modified: 2025-02-27 11:16 UTC (History)
1 user (show)

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


Attachments
DrKonqi kcrash report (166.34 KB, text/vnd.kde.kcrash-report)
2025-02-27 10:31 UTC, Benjamin Dedieu
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Benjamin Dedieu 2025-02-27 10:31:29 UTC
Created attachment 178939 [details]
DrKonqi kcrash report

ApplicationNotResponding [ANR]: false
Qt Version: 6.8.2
Frameworks Version: 6.10.0
Operating System: Linux 6.12.11-200.fc41.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora Linux 41 (Forty One)"
DrKonqi: 6.3.0 [CoredumpBackend]

-- Information about the crash:
Nothing special to declare. Just the popup from the Crash manager appeared when I open my PC. 
My setup is two monitors connected via HDMI, one scaled at 200% and the other at 100%.

The crash can be reproduced sometimes.

-- Backtrace: see file attached (because backtrace is too long to be copied here)

---
Note 1 : DrKonqi did not succeed to send the report (maybe because it was too long ? It only printed this error : "Error transferring https://bugs.kde.org/rest/bug?token=261704-ycKaV9F0Ie - server replied: .")
Note 2: DrKonqi did not find plasmashell category in Bugzilla (see "This report was filed against 'kde' because the product 'plasmashell' could not be located in Bugzilla." at the end of the report) , which it should have done.
Comment 1 cwo 2025-02-27 11:16:54 UTC
Thank you for the bug report! This issue is already being tracked; marking as a duplicate.

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