Bug 459100 - System Settings are crashed after opened Startup and Shutdown
Summary: System Settings are crashed after opened Startup and Shutdown
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: 5.25.5
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2022-09-14 13:51 UTC by ysugamura
Modified: 2022-11-11 05:21 UTC (History)
2 users (show)

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


Attachments
New crash information added by DrKonqi (5.49 KB, text/plain)
2022-10-12 09:39 UTC, vortex
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ysugamura 2022-09-14 13:51:09 UTC
Application: systemsettings (5.25.5)

Qt Version: 5.15.5
Frameworks Version: 5.97.0
Operating System: Linux 5.19.7-1-default aarch64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.25.5 [KCrashBackend]

-- Information about the crash:
I simply oepned "system settings" - "Startup and Shutdown" and then crashed. I cannot open the window.

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings), signal: Segmentation fault

[KCrash Handler]
#4  QV4::Heap::Base::mark (markStack=0xfffff13291e8, this=0x32) at ../../include/QtQml/5.15.5/QtQml/private/../../../../../../src/qml/memory/qv4heap_p.h:190
#5  QV4::Managed::mark (markStack=0xfffff13291e8, this=0xffff8c0f33e0) at /usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-1.3.aarch64/src/qml/jsruntime/qv4managed_p.h:204
#6  QV4::MemoryManager::collectFromJSStack (this=this@entry=0xaaaaeebd0be0, markStack=markStack@entry=0xfffff13291e8) at /usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-1.3.aarch64/src/qml/memory/qv4mm.cpp:1222
#7  0x0000ffffa6681edc in QV4::MemoryManager::collectRoots (this=this@entry=0xaaaaeebd0be0, markStack=markStack@entry=0xfffff13291e8) at /usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-1.3.aarch64/src/qml/memory/qv4mm.cpp:879
#8  0x0000ffffa6682170 in QV4::MemoryManager::mark (this=this@entry=0xaaaaeebd0be0) at /usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-1.3.aarch64/src/qml/memory/qv4mm.cpp:919
#9  0x0000ffffa6683d30 in QV4::MemoryManager::runGC (this=0xaaaaeebd0be0) at /usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-1.3.aarch64/src/qml/memory/qv4mm.cpp:1053
#10 0x0000ffffa6685b50 in QV4::MemoryManager::allocate (size=128, allocator=0xaaaaeebd0bf0, this=0xaaaaeebd0be0) at ../../include/QtQml/5.15.5/QtQml/private/../../../../../../src/qml/memory/qv4mm_p.h:328
#11 QV4::MemoryManager::allocData (this=0xaaaaeebd0be0, size=size@entry=128) at /usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-1.3.aarch64/src/qml/memory/qv4mm.cpp:806
#12 0x0000ffffa6713a38 in QV4::MemoryManager::allocManaged<QV4::SimpleArrayData> (ic=0xffff7e7f0500, size=128, this=<optimized out>) at ../../include/QtQml/5.15.5/QtQml/private/../../../../../../src/qml/memory/qv4mm_p.h:167
#13 QV4::MemoryManager::allocManaged<QV4::SimpleArrayData> (ic=0xffff8c0f34b0, size=104, this=<optimized out>) at ../../include/QtQml/5.15.5/QtQml/private/../../../../../../src/qml/memory/qv4mm_p.h:177
#14 QV4::MemoryManager::allocManaged<QV4::SimpleArrayData> (size=104, this=<optimized out>) at ../../include/QtQml/5.15.5/QtQml/private/../../../../../../src/qml/memory/qv4mm_p.h:185
#15 QV4::ArrayData::realloc (o=o@entry=0xffff8c0f3498, newType=newType@entry=QV4::Heap::ArrayData::Simple, requested=requested@entry=2, enforceAttributes=enforceAttributes@entry=false) at /usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-1.3.aarch64/src/qml/jsruntime/qv4arraydata.cpp:130
#16 0x0000ffffa6715c3c in QV4::Object::arrayReserve (n=2, this=0xffff8c0f3498) at /usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-1.3.aarch64/src/qml/jsruntime/qv4object_p.h:281
#17 QV4::ArrayCtor::virtualCallAsConstructor (f=<optimized out>, argv=0xffff8c0f3490, argc=<optimized out>, newTarget=0xffff8c0f3458) at /usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-1.3.aarch64/src/qml/jsruntime/qv4arrayobject.cpp:79
#18 0x0000ffffa671a3ec in QV4::FunctionObject::callAsConstructor (newTarget=0x0, argc=<optimized out>, argv=<optimized out>, this=<optimized out>) at /usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-1.3.aarch64/src/qml/jsruntime/qv4functionobject_p.h:196
#19 createObjectFromCtorOrArray (scope=..., ctor=..., ctor@entry=..., useLen=useLen@entry=true, len=<optimized out>) at /usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-1.3.aarch64/src/qml/jsruntime/qv4arrayobject.cpp:180
#20 0x0000ffffa671d16c in QV4::ArrayPrototype::method_from (builtin=<optimized out>, thisObject=<optimized out>, argv=<optimized out>, argc=<optimized out>) at /usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-1.3.aarch64/src/qml/jsruntime/qv4arrayobject.cpp:290
#21 0x0000ffffa67aa13c in QV4::FunctionObject::call (argc=1, argv=0xffff8c0f3420, thisObject=0xffff8c0f3408, this=0xfffff13295b8) at /usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-1.3.aarch64/src/qml/jsruntime/qv4functionobject_p.h:202
#22 QV4::Runtime::CallPropertyLookup::call (engine=0xaaaaee74da90, base=..., index=<optimized out>, argv=0xffff8c0f3420, argc=1) at /usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-1.3.aarch64/src/qml/jsruntime/qv4runtime.cpp:1460
#23 0x0000ffffa1b45108 in ?? ()
#24 0x0000ffffa672e0a4 in QV4::Function::call (this=<optimized out>, thisObject=<optimized out>, argv=<optimized out>, argc=<optimized out>, context=<optimized out>) at /usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-1.3.aarch64/src/qml/jsruntime/qv4function.cpp:69
#25 0x0000ffffa672e0a4 in QV4::Function::call (this=<optimized out>, thisObject=<optimized out>, argv=<optimized out>, argc=<optimized out>, context=<optimized out>) at /usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-1.3.aarch64/src/qml/jsruntime/qv4function.cpp:69
#26 0x0000aaaaee74da90 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
[Inferior 1 (process 5650) detached]

Reported using DrKonqi
Comment 1 Nate Graham 2022-09-14 17:04:25 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!
Comment 2 Bug Janitor Service 2022-09-29 04:48:38 UTC
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!
Comment 3 vortex 2022-10-12 09:39:53 UTC
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
Comment 4 Bug Janitor Service 2022-10-27 05:05:07 UTC
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!
Comment 5 Bug Janitor Service 2022-11-11 05:21:46 UTC
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!