SUMMARY When i set up my quick tiling layout after hitting Meta+T, with a gap (padding) of 0 (desired), after restart/some time, the layout stays but gap reverts to 4. STEPS TO REPRODUCE 1. Set gap to 0 2. Restart PC and/or wait some time 3. Observe gap set to 4 OBSERVED RESULT Gap reverts to default value EXPECTED RESULT Gap is remembered SOFTWARE/OS VERSIONS Operating System: Fedora Linux 42 KDE Plasma Version: 6.4.5 KDE Frameworks Version: 6.18.0 Qt Version: 6.9.2 Kernel Version: 6.16.8-200.fc42.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-7300HQ CPU @ 2.50GHz Memory: 24 GiB of RAM (23.3 GiB usable) Graphics Processor 1: Intel® HD Graphics 630 Graphics Processor 2: NVIDIA GeForce GTX 1050 Ti Manufacturer: ASUSTeK COMPUTER INC. Product Name: FX502VE System Version: 1.0
It did not reset for me after reboot. Do you use virtual desktops a lot? As in delete the old ones and make new ones? The gaps and tiles are different between virtual desktops. So in case you change one to 0, then later delete that VD and make new one, it will open up with the default that is 4. I suppose actionable here would be setting the new default to whatever size has been set last time. Operating System: Fedora Linux 42 KDE Plasma Version: 6.5.80 KDE Frameworks Version: 6.19.0 Qt Version: 6.9.2 Kernel Version: 6.16.8-200.fc42.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 16 GiB of RAM (15.5 GiB usable) Graphics Processor: AMD Radeon RX 6600
I do not create new virutal desktops, i only ever use two. I set the gap to 0 yesterday when i made the report, and right now I checked (rebooted maybe 1-2 between), and they're back to 4 I also checked `~/.config/kwinrc` yesterday to see: ``` [Tiling] padding=0 ``` and today it's: ``` [Tiling] padding=4 ``` more info: I plugged & unplugged from an external montior (over displayport) in that time, which i use as my only screen (i.e. when it's plugged in, laptop's screen turns off). I also used some TV's over HDMI for presenting today, but it reset in the past even with just the 1 monitor I have. I'll try uploading a screenshot of the system setting's display page, if i can figure out attachments on bugs.kde.org.
Created attachment 185453 [details] screenshot of display configuration 2025-10-02
I'm also attaching some logs from KSystemlog which include kwin, in case they're useful: 02/10/2025 15:12 kwin_wayland_wrapper The XKEYBOARD keymap compiler (xkbcomp) reports: 02/10/2025 15:12 kwin_wayland_wrapper > Warning: Could not resolve keysym XF86RefreshRateToggle 02/10/2025 15:12 kwin_wayland_wrapper > Warning: Could not resolve keysym XF86Accessibility 02/10/2025 15:12 kwin_wayland_wrapper > Warning: Could not resolve keysym XF86DoNotDisturb 02/10/2025 15:12 kwin_wayland_wrapper Errors from xkbcomp are not fatal to the X server 02/10/2025 15:12 kwin_wayland_wrapper The XKEYBOARD keymap compiler (xkbcomp) reports: 02/10/2025 15:12 kwin_wayland_wrapper > Warning: Unsupported maximum keycode 708, clipping. 02/10/2025 15:12 kwin_wayland_wrapper > X11 cannot support keycodes above 255. 02/10/2025 15:12 kwin_wayland_wrapper > Warning: Could not resolve keysym XF86RefreshRateToggle 02/10/2025 15:12 kwin_wayland_wrapper > Warning: Could not resolve keysym XF86Accessibility 02/10/2025 15:12 kwin_wayland_wrapper > Warning: Could not resolve keysym XF86DoNotDisturb 02/10/2025 15:12 kwin_wayland_wrapper Errors from xkbcomp are not fatal to the X server 02/10/2025 15:13 kwin_wayland kf.plasma.quick: trying to show an empty dialog 02/10/2025 15:13 kwin_wayland This plugin does not support setting window masks 02/10/2025 15:13 kwin_wayland This plugin does not support setting window masks 02/10/2025 15:13 kwin_wayland kf.plasma.quick: trying to show an empty dialog 02/10/2025 15:13 kwin_wayland This plugin does not support setting window masks 02/10/2025 15:13 kwin_wayland This plugin does not support setting window masks 02/10/2025 15:13 kwin_wayland This plugin does not support setting window masks 02/10/2025 15:13 kwin_wayland This plugin does not support setting window masks 02/10/2025 15:13 kwin_wayland This plugin does not support setting window masks 02/10/2025 15:13 kwin_wayland file:///home/nex/.local/share/kwin/scripts/kzones/contents/ui/main.qml:9:1: QML Dialog: Binding loop detected for property "height": file:///home/nex/.local/share/kwin/scripts/kzones/contents/ui/main.qml:42:5 02/10/2025 15:13 kwin_wayland This plugin does not support setting window masks 02/10/2025 15:13 kwin_wayland This plugin does not support setting window masks 02/10/2025 15:29 kwin_wayland kwin_core: XCB error: 3 (BadWindow), sequence: 1060, resource id: 27263128, major code: 129 (SHAPE), minor code: 6 (Input) I should also mention that I am using the KWin script KZones: https://github.com/gerritdevriese/kzones, version 0.9 however, i'm specifically talking about plasma's quick tiling which appears when you do Meta+T, so i don't think that has to do anything with KZones. I don't have the zones overlay or edge snapping in KZones enabled, I only use the Layotus feature (you can define some layouts, drag a window to the top-middle of the screen, and it will suggest tilings. Separate from plasma's tiling afaik)
> more info: I plugged & unplugged from an external montior (over displayport) in that time, which i use as my only screen (i.e. when it's plugged in, laptop's screen turns off). Okay that might explain it, it may think the virtual desktop is new because the monitor has been replugged. It definitely shouldn't, so that's a bug. Need someone with a multimonitor setup, especially with displayport, to test this.
I tried reproducing this but was not able to. Made change a day ago and have rebooted a few times. Still at 0. Operating System: Kubuntu 25.04 KDE Plasma Version: 6.3.4 KDE Frameworks Version: Qt Version: Kernel Version: Linux 6.14.0-33-generic Graphics Platform: KWin (Wayland) Processors: Intel(R) Core(TM) i5-9600K (6) @ 4.60 GHz Memory: 31.16 GiB Graphics Processor: NVIDIA GeForce RTX 2080 Rev. A [Discrete]
i'm using plasma 6.4 - you're on 6.3 and aks is on 6.5. i think it might be an issue in 6.4 only then? i'll wait until 6.5 comes out, and then update this bugreport. thank you for the reproduction attempts.
I updated to plasma 6.4.5 and it seems to no longer be an issue. I'll close it for now and re-open in case I encounter it again. Thank you all for your troubleshooting efforts, and the great work on KDE Plasma! :)
Great to hear, thanks!