So, I can’t say that it didn’t work entirely, but something weird with Tiles Editor happend after my recent upgrades to both fedora 41 and plasma 6.2.2. I’m not entirely sure when this happend because of extended time between my last boot with the recent hurricanes.
I noticed this issue when attempting to use the shortcut Meta+T. I noticed that only one of my panels flickered and nothing else happened. I was perplexed since I had been happily using tiles by holding shift and placing windows as desired. I could also resized the windows and the layout would update and I could close and open/place new windows as desired.
My only issue was when attempting bring up the editor itself.
The issue could’ve been present before I noticed it. But here some things I checked before resolving this for myself.
1.) Made sure that there were no conflicting shortcuts.
2.) Rebooting, updating, and starting new session.
3.) Parsing logs
4.) Restoring many settings to defaults but not all
Nothing seemed to help, so I created a new user.
This made it very evident that the issue was with my user and/or some config issue.
The solution for me was to reset the global theme to a default and reboot for good measure.
I think it could be an issue with the tiling configuration that have become corrupt, and as a result the tile editor would crash, but some tile operations can still succeed.
If this happens again, you can try to edit the file ~/.config/kwinrc and remove all the sections that start with [Tiling] to reset the tiling configuration.
Thank you for reaching out. This led me to the actual resolution. I deleted the sections in the config file as you mentioned. I noticed way more entries for tiling than I have now, so it was probably needed.
However, I have still had this weird behavior when using the shortcut key
Meta+T
I started looking at things I’ve changed in the past and I believe the kicker for me was the keyboard key repeat delay. I’m impatient and dial some of these things down, apparently, to my own demise. I noticed that if I spammed Ctrl+T fast enough or a couple times in a row, it would launch. It’s like the application menu shortcut of just Meta is instantly competing especially when the key repeat latency is low. I had it at something like 300ms. Changing to the default of 600ms seems to be a must for me.
The odd thing to me is that I didn’t recently change the keyrepeat until now. So when I reset the global theme to something like the fedora default, the issue was seemingly resolved until I started diverting from the default. I only ever set the key repeat a long time ago… anyway that setting seems to act different under some conditions. Nonetheless, the key repeat delay setting seems to be the consist fix for me.
There was work in Plasma 6.2 to improve the behaviour of “modifier only shortcuts”, especially for layout changes using things like ALT+SHIFT. This may had bad interaction with low latency key repeats, though the threshold for modifier-only triggering is something like 200ms IIRC - so the change between 600ms and 300ms shouldn’t impact that system I’ll investigate.
Looking at the source, the tiles editor doesn’t have any logging at any point.
If you look at the KWin logs, you might see errors from the QML renderer when it tries to run the tile editor - and that may actually be the problem. On my Plasma 6.3.2 installation, there are some QML warnings that show up:
$ journalctl --user --unit plasma-kwin_wayland.service -f | grep -v 'maliit-keyboard'
Mar 02 12:11:03 vesho kwin_wayland[3357]: file:///usr/share/kwin/effects/tileseditor/qml/main.qml:153:13: QML SpinBox: Binding loop detected for property "implicitWidth":
qrc:/qt/qml/org/kde/plasma/components/SpinBox.qml:20:5
Mar 02 12:11:03 vesho kwin_wayland[3357]: file:///usr/share/kwin/effects/tileseditor/qml/main.qml:153:13: QML SpinBox: Binding loop detected for property "implicitWidth":
qrc:/qt/qml/org/kde/plasma/components/SpinBox.qml:20:5
(I’m grepping away the maliit-keyboard logs, because it is pretty noisy).
