| Summary: | System Settings are crashed after opened Startup and Shutdown | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | ysugamura |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | nate, vortex |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 5.25.5 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
ysugamura
2022-09-14 13:51:09 UTC
Cannot reproduce, no KDE code is implicated in what I can see in the backtrace, and the backtrace is missing debug symbols for the one stack frame that might help. :( If this crash is reproducible, could you please install debug symbols for systemsettings, reproduce it, and attach a new symbolicated backtrace? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Thanks! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Created attachment 152735 [details]
New crash information added by DrKonqi
systemsettings (5.25.5) using Qt 5.15.6
I enabed V3D hardware acceleration and now systemsettings is crashing for me too.
If running on llvmpipe this does not happen.
Maybe it is a bug with the V3D Linux 6.0 kernel driver but I am not sure at this moment.
Additonal packages I added to make V3D work (no boot config.txt changes):
- raspberrypi-firmware-extra-pi4
- Mesa-dri-vc4
Hardware: Raspberry Pi 400
-- Backtrace (Reduced):
#4 QV4::Heap::Base::mark (markStack=0xfffff7d236f8, this=0x36) at ../../include/QtQml/5.15.6/QtQml/private/../../../../../../src/qml/memory/qv4heap_p.h:190
#5 QV4::Managed::mark (markStack=0xfffff7d236f8, this=0xffff91371c80) at /usr/src/debug/libqt5-qtdeclarative-5.15.6+kde20-1.1.aarch64/src/qml/jsruntime/qv4managed_p.h:204
#6 QV4::MemoryManager::collectFromJSStack (this=this@entry=0xaaaaebdc91f0, markStack=markStack@entry=0xfffff7d236f8) at /usr/src/debug/libqt5-qtdeclarative-5.15.6+kde20-1.1.aarch64/src/qml/memory/qv4mm.cpp:1222
#7 0x0000ffffb06e1f5c in QV4::MemoryManager::collectRoots (this=this@entry=0xaaaaebdc91f0, markStack=markStack@entry=0xfffff7d236f8) at /usr/src/debug/libqt5-qtdeclarative-5.15.6+kde20-1.1.aarch64/src/qml/memory/qv4mm.cpp:879
#8 0x0000ffffb06e21f0 in QV4::MemoryManager::mark (this=this@entry=0xaaaaebdc91f0) at /usr/src/debug/libqt5-qtdeclarative-5.15.6+kde20-1.1.aarch64/src/qml/memory/qv4mm.cpp:919
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |