Bug 468232 - SystemSettings app is crashing in QtQuick after QQuickWidget::resizeEvent
Summary: SystemSettings app is crashing in QtQuick after QQuickWidget::resizeEvent
Status: RESOLVED UNMAINTAINED
Alias: None
Product: systemsettings
Classification: Applications
Component: generic-crash (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
: 452783 (view as bug list)
Depends on:
Blocks:
 
Reported: 2023-04-07 07:35 UTC by Alen
Modified: 2023-04-10 17:35 UTC (History)
3 users (show)

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

Attachments
systemsettings crash (6.31 KB, text/plain)
2023-04-07 07:35 UTC, Alen 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Alen 2023-04-07 07:35:52 UTC 
Created attachment 157917 [details]
systemsettings crash

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Just open the systemsettings app and it will crash.
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 David Edmundson 2023-04-07 12:10:57 UTC 
*** Bug 452783 has been marked as a duplicate of this bug. ***
Comment 2 Nate Graham 2023-04-10 17:35:02 UTC 
I'm afraid Plasma 5.24 is unfortunately no longer eligible for support or maintenance. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one. Please update to Plasma 5.27 as soon as your distro offers it to you. If you need support for Plasma 5.24, please contact your distro, who bears the responsibility of providing support for older releases.

If you can reproduce the issue after upgrading to Plasma 5.27, feel free to re-open this bug report.

Thanks for understanding!