*** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY After adding 6 quick tile with all custom (ie not loading a layout) to the custom quick tiles, prevented the editor from opening. Super+T would simply flash windows and then fail to load the editor. Removing all the settings from the kwinrc file and a reboot seemed to fix it. I noticed that when adjusting the quicktiling orientation, the "width" and "height" are using an untruncated float, resulting in an unnecessary number of decimal places used for these dimensions. Unsure if this is causing issues, but if the rounding isn't controlled, there might be overlapping in positions with a large number of 'randomly' placed tiles. Eg. here's a layout with a default loaded, and then manually adjusted width: ``` tiles={"layoutDirection":"horizontal","tiles":[{"layoutDirection":"vertical","tiles":[{"height":0.5},{"height":0.5}],"width":0.43359375},{"width":0.56640625}]} ``` STEPS TO REPRODUCE 1. Super + T - add 6 plus custom quick tile locations by splitting vertically or horizontally. On a dual monitor setup I had 6 on each screen 2. Adjust the orientation so that they are "messy" all with different dimensions. 3. After exiting the editor, and then editing the tiles by dragging the window edges resulted in the editor no longer toggling. OBSERVED RESULT A flickering of open windows, and then nothing. The custom quick tile editor no longer opened. EXPECTED RESULT Any custom tiling orientation should be safely saved and reloaded, without prohibiting the editor from opening. A limit on the number of tiles would be reasonable for stability. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.5.5 KDE Frameworks Version: 6.22.0 Qt Version: 6.10.1 Kernel Version: 6.18.5-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 32 GiB of RAM (31.3 GiB usable) Graphics Processor: NVIDIA GeForce RTX 2060 ADDITIONAL INFORMATION
Thanks for the crash report. As the message at the top of the summary says, if something crashed, we need a backtrace of it so we can figure out what's going on. Can you please attach a backtrace of the crash using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl ? Thanks.
(In reply to TraceyC from comment #1) > Thanks for the crash report. As the message at the top of the summary says, > if something crashed, we need a backtrace of it so we can figure out what's > going on. Can you please attach a backtrace of the crash using the > coredumpctl command-line program, as detailed in > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl ? > > Thanks. I don't have any coredump entries from kwin or a tiling-editor from today. I do have one from systemsettings but I'm unsure what the actually process is that's tied to the tiling manager. See below: $ sudo coredumpctl gdb 104311 PID: 104311 (systemsettings) UID: 1000 (adrian) GID: 1000 (adrian) Signal: 6 (ABRT) Timestamp: Fri 2026-01-16 01:10:37 EST (18h ago) Command Line: /usr/bin/systemsettings Executable: /usr/bin/systemsettings Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-systemsettings@3093795bf22d407c900aa64bebb14cf6.service Unit: user@1000.service User Unit: app-systemsettings@3093795bf22d407c900aa64bebb14cf6.service Slice: user-1000.slice Owner UID: 1000 (adrian) Boot ID: 99e5667dcdee421a9025292bb7e37c22 Machine ID: d2d77e3fcb0d41dc99d8f797473d5574 Hostname: red-october-arch Storage: /var/lib/systemd/coredump/core.systemsettings.1000.99e5667dcdee421a9025292bb7e37c22.104311.1768543837000000.zst (present) Size on Disk: 11M Message: Process 104311 (systemsettings) of user 1000 dumped core. Stack trace of thread 104311: #0 0x00007f780489890c n/a (libc.so.6 + 0x9890c) #1 0x00007f780483e3a0 raise (libc.so.6 + 0x3e3a0) #2 0x00007f7807d63e57 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x7e57) #3 0x00007f780483e4d0 n/a (libc.so.6 + 0x3e4d0) #4 0x00007f780489890c n/a (libc.so.6 + 0x9890c) #5 0x00007f780483e3a0 raise (libc.so.6 + 0x3e3a0) #6 0x00007f780482557a abort (libc.so.6 + 0x2557a) #7 0x00007f78050934a4 n/a (libQt6Core.so.6 + 0x934a4) #8 0x00007f7805094268 _ZNK14QMessageLogger5fatalEPKcz (libQt6Core.so.6 + 0x94268) #9 0x00007f7805091992 _Z11qt_assert_xPKcS0_S0_i (libQt6Core.so.6 + 0x91992) #10 0x00007f77f5c2e5f0 _ZN9QtPrivate16assertObjectTypeIN6Darkly13ScrollBarDataEEEvP7QObject (darkly6.so + 0x4e5f0) #11 0x00007f77f5c2e507 _ZN9QtPrivate11FunctorCallISt16integer_sequenceImJEENS_4ListIJEEEvMN6Darkly13ScrollBarDataEFvvEE4callES8_PS6_PPv (darkly6.so + 0x4e507) #12 0x00007f77f5c2e466 _ZN9QtPrivate15FunctionPointerIMN6Darkly13ScrollBarDataEFvvEE4callINS_4ListIJEEEvEEvS4_PS2_PPv (darkly6.so + 0x4e466) #13 0x00007f77f5c2e3b3 _ZN9QtPrivate15QCallableObjectIMN6Darkly13ScrollBarDataEFvvENS_4ListIJEEEvE4implEiPNS_15QSlotObjectBaseEP7QObjectPPvPb (darkly6.so + 0x4e3b3) #14 0x00007f78051d734f n/a (libQt6Core.so.6 + 0x1d734f) #15 0x00007f7805308417 _ZN25QAbstractAnimationPrivate8setStateEN18QAbstractAnimation5StateE (libQt6Core.so.6 + 0x308417) #16 0x00007f780531b7eb n/a (libQt6Core.so.6 + 0x31b7eb) #17 0x00007f78051d734f n/a (libQt6Core.so.6 + 0x1d734f) #18 0x00007f78051c3851 _ZN7QObjectD2Ev (libQt6Core.so.6 + 0x1c3851) #19 0x00007f77f5c05408 _ZN6Darkly13AnimationDataD2Ev (darkly6.so + 0x25408) #20 0x00007f77f5c05666 _ZN6Darkly11GenericDataD2Ev (darkly6.so + 0x25666) #21 0x00007f77f5c056bc _ZN6Darkly15WidgetStateDataD2Ev (darkly6.so + 0x256bc) #22 0x00007f77f5c074e2 _ZN6Darkly13ScrollBarDataD2Ev (darkly6.so + 0x274e2) #23 0x00007f77f5c074fe _ZN6Darkly13ScrollBarDataD0Ev (darkly6.so + 0x274fe) #24 0x00007f78051c489c _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x1c489c) #25 0x00007f78063021c0 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0x1021c0) #26 0x00007f780516a958 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x16a958) #27 0x00007f780516ad30 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt6Core.so.6 + 0x16ad30) #28 0x00007f780544ae18 n/a (libQt6Core.so.6 + 0x44ae18) #29 0x00007f78042b9f8d n/a (libglib-2.0.so.0 + 0x5ef8d) #30 0x00007f78042bb657 n/a (libglib-2.0.so.0 + 0x60657) #31 0x00007f78042bb865 g_main_context_iteration (libglib-2.0.so.0 + 0x60865) #32 0x00007f7805448152 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x448152) #33 0x00007f7805175786 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x175786) #34 0x00007f780516f3f1 _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x16f3f1) #35 0x00005641d491e4a0 n/a (/usr/bin/systemsettings + 0x154a0) #36 0x00007f7804827635 n/a (libc.so.6 + 0x27635) #37 0x00007f78048276e9 __libc_start_main (libc.so.6 + 0x276e9) #38 0x00005641d491f0c5 n/a (/usr/bin/systemsettings + 0x160c5) Stack trace of thread 104317: #0 0x00007f780489f002 n/a (libc.so.6 + 0x9f002) #1 0x00007f780489316c n/a (libc.so.6 + 0x9316c) #2 0x00007f78048937dc n/a (libc.so.6 + 0x937dc) #3 0x00007f7804895e9e pthread_cond_wait (libc.so.6 + 0x95e9e) #4 0x00007f7805333e69 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x333e69) #5 0x00007f7803562d49 n/a (libQt6WaylandClient.so.6 + 0x6bd49) #6 0x00007f780532f899 n/a (libQt6Core.so.6 + 0x32f899) #7 0x00007f780489698b n/a (libc.so.6 + 0x9698b) #8 0x00007f780491a9cc n/a (libc.so.6 + 0x11a9cc) Stack trace of thread 104318: #0 0x00007f780489f002 n/a (libc.so.6 + 0x9f002) #1 0x00007f780489316c n/a (libc.so.6 + 0x9316c) #2 0x00007f78048931b4 n/a (libc.so.6 + 0x931b4) #3 0x00007f780490d4ae __poll (libc.so.6 + 0x10d4ae) #4 0x00007f7803562db5 n/a (libQt6WaylandClient.so.6 + 0x6bdb5) #5 0x00007f780532f899 n/a (libQt6Core.so.6 + 0x32f899) #6 0x00007f780489698b n/a (libc.so.6 + 0x9698b) #7 0x00007f780491a9cc n/a (libc.so.6 + 0x11a9cc) Stack trace of thread 104328: #0 0x00007f780489f002 n/a (libc.so.6 + 0x9f002) #1 0x00007f780489316c n/a (libc.so.6 + 0x9316c) #2 0x00007f78048931b4 n/a (libc.so.6 + 0x931b4) #3 0x00007f780490d9f6 ppoll (libc.so.6 + 0x10d9f6) #4 0x00007f78042bb784 n/a (libglib-2.0.so.0 + 0x60784) #5 0x00007f78042bba17 g_main_loop_run (libglib-2.0.so.0 + 0x60a17) #6 0x00007f77fefb32e4 n/a (libgio-2.0.so.0 + 0x11a2e4) #7 0x00007f78042f28bc n/a (libglib-2.0.so.0 + 0x978bc) #8 0x00007f780489698b n/a (libc.so.6 + 0x9698b) #9 0x00007f780491a9cc n/a (libc.so.6 + 0x11a9cc) Stack trace of thread 104325: #0 0x00007f780489f002 n/a (libc.so.6 + 0x9f002) #1 0x00007f780489316c n/a (libc.so.6 + 0x9316c) #2 0x00007f78048931b4 n/a (libc.so.6 + 0x931b4) #3 0x00007f780490d9f6 ppoll (libc.so.6 + 0x10d9f6) #4 0x00007f78042bb784 n/a (libglib-2.0.so.0 + 0x60784) #5 0x00007f78042bb865 g_main_context_iteration (libglib-2.0.so.0 + 0x60865) #6 0x00007f7805448152 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x448152) #7 0x00007f7805175786 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x175786) #8 0x00007f780529041e _ZN7QThread4execEv (libQt6Core.so.6 + 0x29041e) #9 0x00007f78079a1302 n/a (libQt6Quick.so.6 + 0x3a1302) #10 0x00007f780532f899 n/a (libQt6Core.so.6 + 0x32f899) #11 0x00007f780489698b n/a (libc.so.6 + 0x9698b) #12 0x00007f780491a9cc n/a (libc.so.6 + 0x11a9cc) Stack trace of thread 104316: #0 0x00007f780489f002 n/a (libc.so.6 + 0x9f002) #1 0x00007f780489316c n/a (libc.so.6 + 0x9316c) #2 0x00007f78048931b4 n/a (libc.so.6 + 0x931b4) #3 0x00007f780490d9f6 ppoll (libc.so.6 + 0x10d9f6) #4 0x00007f78042bb784 n/a (libglib-2.0.so.0 + 0x60784) #5 0x00007f78042bb865 g_main_context_iteration (libglib-2.0.so.0 + 0x60865) #6 0x00007f7805448152 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x448152) #7 0x00007f7805175786 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x175786) #8 0x00007f780529041e _ZN7QThread4execEv (libQt6Core.so.6 + 0x29041e) #9 0x00007f7804f7603e n/a (libQt6DBus.so.6 + 0x3703e) #10 0x00007f780532f899 n/a (libQt6Core.so.6 + 0x32f899) #11 0x00007f780489698b n/a (libc.so.6 + 0x9698b) #12 0x00007f780491a9cc n/a (libc.so.6 + 0x11a9cc) Stack trace of thread 104329: #0 0x00007f780489f002 n/a (libc.so.6 + 0x9f002) #1 0x00007f780489316c n/a (libc.so.6 + 0x9316c) #2 0x00007f78048937dc n/a (libc.so.6 + 0x937dc) #3 0x00007f78048960a8 pthread_cond_timedwait (libc.so.6 + 0x960a8) #4 0x00007f7805333dc5 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x333dc5) #5 0x00007f780528ee69 n/a (libQt6Core.so.6 + 0x28ee69) #6 0x00007f780532f899 n/a (libQt6Core.so.6 + 0x32f899) #7 0x00007f780489698b n/a (libc.so.6 + 0x9698b) #8 0x00007f780491a9cc n/a (libc.so.6 + 0x11a9cc) Stack trace of thread 104342: #0 0x00007f780489f002 n/a (libc.so.6 + 0x9f002) #1 0x00007f780489316c n/a (libc.so.6 + 0x9316c) #2 0x00007f78048937dc n/a (libc.so.6 + 0x937dc) #3 0x00007f78048960a8 pthread_cond_timedwait (libc.so.6 + 0x960a8) #4 0x00007f7805333dc5 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x333dc5) #5 0x00007f780528ee69 n/a (libQt6Core.so.6 + 0x28ee69) #6 0x00007f780532f899 n/a (libQt6Core.so.6 + 0x32f899) #7 0x00007f780489698b n/a (libc.so.6 + 0x9698b) #8 0x00007f780491a9cc n/a (libc.so.6 + 0x11a9cc) Stack trace of thread 104332: #0 0x00007f780489f002 n/a (libc.so.6 + 0x9f002) #1 0x00007f780489316c n/a (libc.so.6 + 0x9316c) #2 0x00007f78048937dc n/a (libc.so.6 + 0x937dc) #3 0x00007f78048960a8 pthread_cond_timedwait (libc.so.6 + 0x960a8) #4 0x00007f7805333dc5 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x333dc5) #5 0x00007f780528ee69 n/a (libQt6Core.so.6 + 0x28ee69) #6 0x00007f780532f899 n/a (libQt6Core.so.6 + 0x32f899) #7 0x00007f780489698b n/a (libc.so.6 + 0x9698b) #8 0x00007f780491a9cc n/a (libc.so.6 + 0x11a9cc) Stack trace of thread 104330: #0 0x00007f780489f002 n/a (libc.so.6 + 0x9f002) #1 0x00007f780489316c n/a (libc.so.6 + 0x9316c) #2 0x00007f78048937dc n/a (libc.so.6 + 0x937dc) #3 0x00007f78048960a8 pthread_cond_timedwait (libc.so.6 + 0x960a8) #4 0x00007f7805333dc5 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x333dc5) #5 0x00007f780528ee69 n/a (libQt6Core.so.6 + 0x28ee69) #6 0x00007f780532f899 n/a (libQt6Core.so.6 + 0x32f899) #7 0x00007f780489698b n/a (libc.so.6 + 0x9698b) #8 0x00007f780491a9cc n/a (libc.so.6 + 0x11a9cc) Stack trace of thread 104331: #0 0x00007f780489f002 n/a (libc.so.6 + 0x9f002) #1 0x00007f780489316c n/a (libc.so.6 + 0x9316c) #2 0x00007f78048937dc n/a (libc.so.6 + 0x937dc) #3 0x00007f78048960a8 pthread_cond_timedwait (libc.so.6 + 0x960a8) #4 0x00007f7805333dc5 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x333dc5) #5 0x00007f780528ee69 n/a (libQt6Core.so.6 + 0x28ee69) #6 0x00007f780532f899 n/a (libQt6Core.so.6 + 0x32f899) #7 0x00007f780489698b n/a (libc.so.6 + 0x9698b) #8 0x00007f780491a9cc n/a (libc.so.6 + 0x11a9cc) Stack trace of thread 104327: #0 0x00007f780489f002 n/a (libc.so.6 + 0x9f002) #1 0x00007f780489316c n/a (libc.so.6 + 0x9316c) #2 0x00007f78048931b4 n/a (libc.so.6 + 0x931b4) #3 0x00007f780490d9f6 ppoll (libc.so.6 + 0x10d9f6) #4 0x00007f78042bb784 n/a (libglib-2.0.so.0 + 0x60784) #5 0x00007f78042bb865 g_main_context_iteration (libglib-2.0.so.0 + 0x60865) #6 0x00007f78042bb8b2 n/a (libglib-2.0.so.0 + 0x608b2) #7 0x00007f78042f28bc n/a (libglib-2.0.so.0 + 0x978bc) #8 0x00007f780489698b n/a (libc.so.6 + 0x9698b) #9 0x00007f780491a9cc n/a (libc.so.6 + 0x11a9cc) Stack trace of thread 104341: #0 0x00007f780489f002 n/a (libc.so.6 + 0x9f002) #1 0x00007f780489316c n/a (libc.so.6 + 0x9316c) #2 0x00007f78048931b4 n/a (libc.so.6 + 0x931b4) #3 0x00007f780490d9f6 ppoll (libc.so.6 + 0x10d9f6) #4 0x00007f78042bb784 n/a (libglib-2.0.so.0 + 0x60784) #5 0x00007f78042bb865 g_main_context_iteration (libglib-2.0.so.0 + 0x60865) #6 0x00007f7805448152 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x448152) #7 0x00007f7805175786 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x175786) #8 0x00007f780529041e _ZN7QThread4execEv (libQt6Core.so.6 + 0x29041e) #9 0x00007f780532f899 n/a (libQt6Core.so.6 + 0x32f899) #10 0x00007f780489698b n/a (libc.so.6 + 0x9698b) #11 0x00007f780491a9cc n/a (libc.so.6 + 0x11a9cc) Stack trace of thread 104326: #0 0x00007f780491872d syscall (libc.so.6 + 0x11872d) #1 0x00007f78042ea82e g_cond_wait (libglib-2.0.so.0 + 0x8f82e) #2 0x00007f78042811cd n/a (libglib-2.0.so.0 + 0x261cd) #3 0x00007f78042f3487 n/a (libglib-2.0.so.0 + 0x98487) #4 0x00007f78042f28bc n/a (libglib-2.0.so.0 + 0x978bc) #5 0x00007f780489698b n/a (libc.so.6 + 0x9698b) #6 0x00007f780491a9cc n/a (libc.so.6 + 0x11a9cc) ELF object binary architecture: AMD x86-64 GNU gdb (GDB) 17.1 Copyright (C) 2025 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <https://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/bin/systemsettings... (No debugging symbols found in /usr/bin/systemsettings) ⚠️ warning: Can't open file /usr/lib/libheif.so.1.21.1 during file-backed mapping note processing ⚠️ warning: Can't open file /home/adrian/.cache/systemsettings/qmlcache/37ccc02acc6219e0b126b054c3559b37493c4d73.qmlc (deleted) during file-backed mapping note processing ⚠️ warning: Can't open file /home/adrian/.cache/systemsettings/qmlcache/735e97095127438c34ee937448862d538da4e7ef.qmlc (deleted) during file-backed mapping note processing ⚠️ warning: Can't open file /memfd:JSGCHeap:QtQml (deleted) during file-backed mapping note processing ⚠️ warning: File /usr/lib/qt6/plugins/styles/darkly6.so doesn't match build-id from core-file during file-backed mapping processing ⚠️ warning: Can't open file /memfd:kwin-dmabuf-feedback-table (deleted) during file-backed mapping note processing ⚠️ warning: Can't open file /usr/lib/libnvidia-egl-gbm.so.1.1.2 during file-backed mapping note processing [New LWP 104311] [New LWP 104317] [New LWP 104318] [New LWP 104328] [New LWP 104325] [New LWP 104316] [New LWP 104329] [New LWP 104342] [New LWP 104332] [New LWP 104330] [New LWP 104331] [New LWP 104327] [New LWP 104341] [New LWP 104326] ⚠️ warning: Build-id of /usr/lib/libnvidia-egl-gbm.so.1 does not match core file. ⚠️ warning: Build-id of /usr/lib/qt6/plugins/styles/darkly6.so does not match core file. ⚠️ warning: Build-id of /usr/lib/libheif.so.1 does not match core file. ⚠️ warning: Could not load shared library symbols for 3 libraries, e.g. /usr/lib/libnvidia-egl-gbm.so.1. Use the "info sharedlibrary" command to see the complete listing. Do you need "set solib-search-path" or "set sysroot"? [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". Core was generated by `/usr/bin/systemsettings'. Program terminated with signal SIGABRT, Aborted. #0 0x00007f780489890c in ?? () from /usr/lib/libc.so.6 [Current thread is 1 (Thread 0x7f77feb3a080 (LWP 104311))]
That crash is probably relevant. The way to be sure is to cause the crash again, and see if another coredump for systemsettings is created. Does this happen? Unfortunately the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong: #14 0x00007f78051d734f n/a (libQt6Core.so.6 + 0x1d734f) #35 0x00005641d491e4a0 n/a (/usr/bin/systemsettings + 0x154a0) Could you please install debug packages and attach a new symbolicated backtrace generated by using `coredumpctl gdb` in a terminal window? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl for details about how to do this. Thanks again!
(In reply to TraceyC from comment #3) > That crash is probably relevant. The way to be sure is to cause the crash > again, and see if another coredump for systemsettings is created. Does this > happen? So the behaviour in question doesn't seem to create a coredump file. It seems to be related with HOW I press the hotkey for the custom quick tile settings. If i release T too quickly, the windows all sort of flash, and nothing happens. If i give it a brief moment before releasing (still fractions of a second) then the tiling settings appear. I will work on getting the debug packages installed - i think i removed them without realizing while uninstalling orphaned packages.
Thanks for the additional detail, that's helpful. It seems that rather than a crash, there's a timing issue. Can you add a new set of discrete, numbered steps to detail exactly how you're able to reproduce this? Alternatively, a recording of triggering the bug would also work. I'm not able to immediately trigger this on my system, but timing issues are notoriously difficult to reproduce. I want to make sure I'm doing the exact same thing. Thanks!