I've noticed on more than one OS including Garuda that after a period of time dialog boxes do not popup where they should and are much larger than they should be. For example when I connect my phone and the devices one opens it's in the center of the screen instead of the upper right corner and much larger than it should be. I click on shutdown Or Switch and it's dialog box opens in the right spot on the screen but much larger than it should be. Same with clicking the Application Launcher as the devices dialog. When I'm copying or movie files / folders the indicator only show on the main virtual desktop instead of all of them like it should. ``` ╭─cccp@CCCP in ~ ╰─λ garuda-inxi System: Kernel: 6.10.10-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1 clocksource: tsc avail: hpet,acpi_pm parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=85940f0b-f078-457f-89a1-1f9d08a9eeb7 rw rootflags=subvol=@ quiet loglevel=3 ibt=off Desktop: KDE Plasma v: 6.1.5 tk: Qt v: N/A info: frameworks v: 6.6.0 wm: kwin_wayland with: krunner vt: 1 dm: SDDM Distro: Garuda base: Arch Linux Machine: Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required> Mobo: ASUSTeK model: TUF GAMING B550-PLUS WIFI II v: Rev X.0x serial: <superuser required> part-nu: SKU uuid: <superuser required> UEFI: American Megatrends v: 3607 date: 03/22/2024 Battery: Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard K360 serial: <filter> charge: 100% (should be ignored) rechargeable: yes status: discharging CPU: Info: model: AMD Ryzen 7 5700X bits: 64 type: MT MCP arch: Zen 3+ gen: 4 level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25) model-id: 0x21 (33) stepping: 2 microcode: 0xA20120E Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 32 MiB desc: 1x32 MiB Speed (MHz): avg: 3483 high: 3593 min/max: 2200/4662 boost: enabled scaling: driver: acpi-cpufreq governor: performance cores: 1: 3400 2: 3593 3: 3400 4: 3592 5: 3400 6: 3400 7: 3400 8: 3591 9: 3593 10: 3400 11: 3400 12: 3593 13: 3400 14: 3587 15: 3592 16: 3400 bogomips: 108599 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 Vulnerabilities: <filter> Graphics: Device-1: NVIDIA GA106 [GeForce RTX 3060 Lite Hash Rate] vendor: ASUSTeK driver: nvidia v: 560.35.03 alternate: nouveau,nvidia_drm non-free: 550.xx+ status: current (as of 2024-06; EOL~2026-12-xx) arch: Ampere code: GAxxx process: TSMC n7 (7nm) built: 2020-2023 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: none off: DP-1 empty: DP-2,DP-3,HDMI-A-1 bus-ID: 0a:00.0 chip-ID: 10de:2504 class-ID: 0300 Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.2 compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting alternate: fbdev,nouveau,nv,vesa gpu: nvidia display-ID: 0 Monitor-1: DP-1 res: 2560x1440 size: N/A modes: N/A API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2 drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia x11: drv: nvidia inactive: device-1 API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 560.35.03 glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 3060/PCIe/SSE2 memory: 11.72 GiB display-ID: :1.0 API: Vulkan v: 1.3.295 layers: 7 device: 0 type: discrete-gpu name: NVIDIA GeForce RTX 3060 driver: nvidia v: 560.35.03 device-ID: 10de:2504 surfaces: xcb,xlib,wayland Audio: Device-1: NVIDIA GA106 High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 0a:00.1 chip-ID: 10de:228e class-ID: 0403 Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 0c:00.4 chip-ID: 1022:1487 class-ID: 0403 API: ALSA v: k6.10.10-zen1-1-zen status: kernel-api with: aoss type: oss-emulator tools: N/A Server-1: PipeWire v: 1.2.3 status: active with: 1: pipewire-pulse status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl Network: Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 07:00.0 chip-ID: 8086:2723 class-ID: 0280 IF: wlp7s0 state: down mac: <filter> Device-2: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 port: f000 bus-ID: 09:00.0 chip-ID: 10ec:8125 class-ID: 0200 IF: enp9s0 state: up speed: 1000 Mbps duplex: full mac: <filter> Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant Bluetooth: Device-1: IMC Networks Wireless_Device driver: btusb v: 0.8 type: USB rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-5:3 chip-ID: 13d3:3563 class-ID: e001 serial: <filter> Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2 lmp-v: 11 status: discoverable: no pairing: no class-ID: 6c0104 Device-2: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-7.4:12 chip-ID: 8087:0029 class-ID: e001 Report: ID: hci1 rfk-id: 2 state: up address: <filter> bt-v: 5.2 lmp-v: 11 status: discoverable: no pairing: no class-ID: 6c0104 Drives: Local Storage: total: 34.11 TiB used: 18.9 TiB (55.4%) SMART Message: Unable to run smartctl. Root privileges required. ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Crucial model: CT1000T500SSD8 size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter> fw-rev: P8CR002 temp: 32.9 C scheme: GPT ID-2: /dev/nvme1n1 maj-min: 259:4 vendor: Crucial model: CT500P3SSD8 size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter> fw-rev: P9CR30A temp: 30.9 C scheme: GPT ID-3: /dev/sda maj-min: 8:0 vendor: Seagate model: Expansion HDD size: 14.55 TiB block-size: physical: 4096 B logical: 512 B type: USB rev: 3.2 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter> fw-rev: 1801 scheme: GPT ID-4: /dev/sdb maj-min: 8:16 vendor: Seagate model: Expansion HDD size: 10.91 TiB block-size: physical: 4096 B logical: 512 B type: USB rev: 3.2 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter> fw-rev: 0003 scheme: GPT ID-5: /dev/sdc maj-min: 8:32 vendor: Seagate model: Expansion HDD size: 7.28 TiB block-size: physical: 4096 B logical: 512 B type: USB rev: 3.2 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter> fw-rev: 1801 scheme: GPT Partition: ID-1: / raw-size: 698.41 GiB size: 698.41 GiB (100.00%) used: 20.4 GiB (2.9%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3 ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 182.4 MiB (60.9%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1 ID-3: /home raw-size: 698.41 GiB size: 698.41 GiB (100.00%) used: 20.4 GiB (2.9%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3 ID-4: /var/log raw-size: 698.41 GiB size: 698.41 GiB (100.00%) used: 20.4 GiB (2.9%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3 ID-5: /var/tmp raw-size: 698.41 GiB size: 698.41 GiB (100.00%) used: 20.4 GiB (2.9%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3 Swap: Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no ID-1: swap-1 type: zram size: 46.96 GiB used: 0 KiB (0.0%) priority: 100 comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 16 dev: /dev/zram0 Sensors: System Temperatures: cpu: 38.1 C mobo: N/A Fan Speeds (rpm): N/A Info: Memory: total: 48 GiB available: 46.96 GiB used: 7.58 GiB (16.1%) Processes: 442 Power: uptime: 2h 46m states: freeze,mem,disk suspend: deep avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume image: 18.73 GiB services: org_kde_powerdevil, power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical tool: systemctl Packages: pm: pacman pkgs: 1911 libs: 542 tools: octopi,pacseek,paru,pikaur,yay Compilers: clang: 18.1.8 gcc: 14.2.1 Shell: garuda-inxi default: fish v: 3.7.1 running-in: konsole inxi: 3.3.35 Garuda (2.6.26-1): System install date: 2024-09-19 Last full system update: 2024-09-20 Is partially upgraded: No Relevant software: snapper NetworkManager dracut nvidia-dkms Windows dual boot: No/Undetected Failed units: ``` Plasma 6.1.5 KDE Frameworks 6.6.0 Kernel 6.10.10 Zen Wayland https://i.imgur.com/wMnxtny.jpeg https://i.imgur.com/bDrJCdR.jpeg https://i.imgur.com/v6pmp6F.jpeg
The screenshots show that you have a heavily customized Plasma setup, and I suspect one of those customizations is causing this — for example, window rules. Can you create a new clean user account and see if the problem happens there? If it does not, this indicates there's a strong change one of the customizations is to blame. In that case, please try to figure out which one it is.
Pretty sure it's theme related and not customization related. I suspect this cause I had Garuda, RebornOs, and CachyOS installed and in Cachy this did not happen. The only difference is that in Reborn and Garuda I installed Utterly-Sweet Global Themen then switched to Vivid -Magna-Dark and I had the issue before switching to Magna. In Cachy I only install Vivid-Magna-Dark and never got the issue. As a test I just installed another copy of Garuda and set it up like I normally do, but this time I left the default theme and only changed the icons and cursors and it's behaving as it should so far. The only thing I am running into and I've seen before is trying to add my two desktop widgets. I try to drag them to the desktop and I get red stop symbol and the screen blinks off for a second and then comes back. When I've seen it in the past for some reason it just corrected itself.
OK I finished running my test and it looks to be in part to resizing various components. All was looking good til I stretched system settings a little and went into Configure Special Application Settings and set it to use the size I had stretched System Settings to. Once I did that the dialog boxes became like you see in the screenshots I posted. I went back in removed the custom size and the dialog boxes went back to normal. Seems odd that that would cause the issue, but I have to go by what I observed.
I had a feeling this was caused by a broken window rule. Solution: fix your window rule. :)
I have slightly stretched both System Settings and Desktop Folder Settings and set them to their particular Virtual Desktop, set their custom size, and their custom position from Plasma 5.0 and even in Plasma 6.0 and this was not happening. This is something new since 6.1. That tells me something is linked that wasn't before. That needs a looking into.
https://forum.garudalinux.org/t/dialog-boxes-in-wrong-location-and-wrong-size/39357
Actually NOT resolved and is a bug.
So you're saying you had a window rule that behaved in a certain way, and then after upgrading to Plasma 6.1, it behaved in a different way? Is that right?
Yes. Maybe it's better if I do a video to show what is exactly happening. That way we both can avoid misunderstanding due to language differences. Give me til this time tomorrow to get one made for you. Thanks
OK just set size, virtual desktop, and position and it did what you see in my above screenshots. If remove the window rules the boxes go back to being where they are suppose to be. Applications menu upper left corner, devices popup back in the upper right corner, and the drop down for shutdown or switch goes back to being only twice as wide as the lock screen text. Also if I add the size, position, virtual desktop if I plug in a flash drive the devices dialog box only opens on the desktop that I have the system settings panel assigned to as well as the copy / move dialog instead of them being on all desktops like they normally are.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. 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. Closing as RESOLVED WORKSFORME.
This is marked resolved. Something about workframe? I see nothing explaining what was causing the issue, nor what steps were involved to fix the issue. I'd like to know that I can once again be able to assign say system settings to only my main virtual desktop and not have the copy / move dialog only available on that virtual desktop because of assigning system settings to open only on that desktop, or if a assign a custom size to system settings / desktop & wallpaper application launcher won't be made larger and or moved to the center of the screen along with other system dialog boxes. Thanks
The problem remains the same: you've got a broken window rule that's too broad in scope, or not applying the right properties.
On a feature that with without issue until plasma 6 or 6.1, and happens in at least Garuda, Arch, Reborn, CachyOS, BigLinux? You may be right but it's still something under the hood causing it. See the new screenshot with explanation below it. https://i.imgur.com/rtKkaXe.png Now if I actually applied those the dialog boxes would go haywire. All I'm getting at is the settings are nothing different than I have always done.
I did a fresh install of RebornOS and ran a couple of test. I narrowed the issue down to setting Desktop & Wallpaper to a custom size specific desktop, and specific position. The above described behavior seen to be cause only by this Plasma component being set this way.
I did a fresh install of RebornOS and ran a couple of test. I narrowed the issue down to rightclicking the desktop selecting Desktop & Wallpaper and setting it to a custom size, a specific desktop, and a specific position under More, Configure Special Application Settings. The above described behavior seems to be caused only by this Plasma component being set this way. Sorry for the repost but I noticed on the forum that the post above this one needed to be edited and there is no editing here. I hope that gives you a better understanding of what is going on.