Created attachment 163781 [details] Image showing behaviour of panels STEPS TO REPRODUCE 1. Create multiple panels on the same side of the screen 2. Limit the panels to occupy a specific area, in that they don't overlap OBSERVED RESULT Second panel begins at the highest point of the first panel EXPECTED RESULT Both panels start at the same height, e.g. at the bottom of the screen SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.1 ADDITIONAL INFORMATION The issue does not appear in the X11 session.
The issue seems to specifically affect the default panel in conjunction with others, or perhaps just a panel created before 5.90.0. I created 2 new panels and the issue no longer appears.
I'm guessing one panel is center-aligned and the other one (the one that appears at the wrong height) is left or right-aligned, correct? I can reproduce that.
*** Bug 478176 has been marked as a duplicate of this bug. ***
*** Bug 479757 has been marked as a duplicate of this bug. ***
*** Bug 481749 has been marked as a duplicate of this bug. ***
*** Bug 482212 has been marked as a duplicate of this bug. ***
(In reply to Nate Graham from comment #2) > I'm guessing one panel is center-aligned and the other one (the one that > appears at the wrong height) is left or right-aligned, correct? I can > reproduce that. Correct. I'm on the Artix testing 6.0.0 builds, and it's still occurring with a default panel and any others added after are out of alignment.
Created attachment 166463 [details] Panel mis-alignment with 6.0.0 build
I also can reproduce this bug, but I don't need to have a center aligned panel. I am currently on KDE neon user edition with plasma 6.0.0 and I can replicate this bug even creating two empty panels one left aligned and one right aligned.
I can replicate this bug as well. Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.8-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5625U with Radeon Graphics Memory: 14.5 GiB of RAM Graphics Processor: AMD Radeon Graphics
Same problem here. Additionally, with multiple screens, moving the panel to another monitor and then back fixes the issue until reboot. After that, the panel shows up on a different screen, while in configuration it still says it is on the screen its supposed to be on. Operating System: Garuda Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.8-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6650 XT
I have the same issue. It also happens even if the first panel is not center-aligned, and on all four edges of the screen. Operating System: EndeavourOS KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.8-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor Memory: 31,3 GiB of RAM Graphics Processor: AMD Radeon RX 6700 XT Product Name: X570 Phantom Gaming 4
*** Bug 482781 has been marked as a duplicate of this bug. ***
*** Bug 483126 has been marked as a duplicate of this bug. ***
Any news? its been more than a month
CPU: 16-core AMD Ryzen 9 5950X (-MT MCP-) speed/min/max: 2481/2200/5980 MHz Kernel: 6.8.7-artix1-1 x86_64 Up: 7m Mem: 5.42/62.7 GiB (8.6%) Storage: 5.05 TiB (20.5% used) Procs: 528 Shell: Bash inxi: 3.3.34 [john@quokka ~]$ inxi -F System: Host: quokka Kernel: 6.8.7-artix1-1 arch: x86_64 bits: 64 Desktop: KDE Plasma v: 6.0.4 Distro: Artix Linux Machine: Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required> Mobo: ASUSTeK model: TUF GAMING X570-PRO (WI-FI) v: Rev X.0x serial: <superuser required> UEFI: American Megatrends v: 4602 date: 02/23/2023 CPU: Info: 16-core model: AMD Ryzen 9 5950X bits: 64 type: MT MCP cache: L2: 8 MiB Speed (MHz): avg: 2537 min/max: 2200/5980 cores: 1: 2200 2: 4000 3: 2200 4: 2200 5: 2200 6: 2200 7: 2200 8: 2200 9: 4000 10: 2200 11: 2200 12: 2200 13: 2200 14: 2200 15: 2200 16: 2200 17: 4000 18: 4000 19: 2200 20: 2200 21: 3998 22: 2200 23: 2200 24: 2200 25: 2200 26: 2200 27: 2200 28: 2200 29: 2200 30: 2200 31: 2200 32: 4000 Graphics: Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT] driver: amdgpu v: kernel Device-2: Logitech C922 Pro Stream Webcam driver: snd-usb-audio,uvcvideo type: USB Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 23.2.6 compositor: kwin_wayland driver: X: loaded: amdgpu unloaded: modesetting,radeon failed: fbdev,vesa dri: radeonsi gpu: amdgpu resolution: 1: 1920x1080 2: 1920x1080 API: EGL v: 1.5 drivers: radeonsi,swrast platforms: wayland,x11,surfaceless,device API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.0.5-arch1.1 renderer: AMD Radeon RX 6700 XT (radeonsi navi22 LLVM 17.0.6 DRM 3.57 6.8.7-artix1-1) API: Vulkan v: 1.3.279 drivers: radv,llvmpipe surfaces: xcb,xlib,wayland Audio: Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel Device-2: AMD Starship/Matisse HD Audio driver: snd_hda_intel Device-3: Logitech C922 Pro Stream Webcam driver: snd-usb-audio,uvcvideo type: USB API: ALSA v: k6.8.7-artix1-1 status: kernel-api Server-1: PulseAudio v: 17.0 status: active Network: Device-1: Broadcom BCM4360 802.11ac Dual Band Wireless Network Adapter driver: wl IF: wlan0 state: up mac: b8:09:8a:44:8a:35 Device-2: Intel Ethernet I225-V driver: igc IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 04:42:1a:e7:72:ed Bluetooth: Device-1: Apple Bluetooth Host Controller driver: btusb type: USB Report: rfkill ID: hci0 state: up address: see --recommends Drives: Local Storage: total: 5.05 TiB used: 1.03 TiB (20.5%) ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 980 500GB size: 465.76 GiB ID-2: /dev/nvme1n1 model: AGAMMIXS70B-2T-CS size: 1.86 TiB ID-3: /dev/sda vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB ID-4: /dev/sdb vendor: Western Digital model: WD2003FZEX-00SRLA0 size: 1.82 TiB Partition: ID-1: / size: 425.39 GiB used: 36.18 GiB (8.5%) fs: ext4 dev: /dev/nvme0n1p3 ID-2: /boot/efi size: 511 MiB used: 296 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 ID-3: /home size: 1.83 TiB used: 1021.91 GiB (54.5%) fs: ext4 dev: /dev/nvme1n1p1 Swap: ID-1: swap-1 type: partition size: 32 GiB used: 0 KiB (0.0%) dev: /dev/nvme0n1p2 Sensors: System Temperatures: cpu: 40.8 C mobo: N/A gpu: amdgpu temp: 55.0 C Fan Speeds (rpm): N/A gpu: amdgpu fan: 0 Info: Memory: total: 64 GiB note: est. available: 62.7 GiB used: 5.4 GiB (8.6%) Processes: 528 Uptime: 7m Shell: Bash inxi: 3.3.34 Updated to Arch Linux's KDE 6.0.4 and this behavior is still occurring.
I can also reproduce this bug on OpenSUSE Tumbleweed, Plasma 6.0.4, Frameworks 6.1.0, Wayland session. It only seems to occur when the 'Always Visible' option is set for at least one panel. If both panels use any other setting (Auto-Hide, Dodge Windows, or Windows Go Below) the bug does not occur outside of edit mode, even if both panels are visible at once. In edit mode the panels are still offset, but that does not impact actual use. There is no difference in behavior when using the 'custom' width option vs 'fit content'.
*** Bug 486518 has been marked as a duplicate of this bug. ***
Quick update: this only occurs in a Wayland session. In X11, it works as expected on the same build info below. (In reply to John 'JT' Lamb from comment #16) > CPU: 16-core AMD Ryzen 9 5950X (-MT MCP-) speed/min/max: 2481/2200/5980 MHz > Kernel: 6.8.7-artix1-1 x86_64 Up: 7m Mem: 5.42/62.7 GiB (8.6%) > Storage: 5.05 TiB (20.5% used) Procs: 528 Shell: Bash inxi: 3.3.34 > [john@quokka ~]$ inxi -F > System: > Host: quokka Kernel: 6.8.7-artix1-1 arch: x86_64 bits: 64 > Desktop: KDE Plasma v: 6.0.4 Distro: Artix Linux > Machine: > Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required> > Mobo: ASUSTeK model: TUF GAMING X570-PRO (WI-FI) v: Rev X.0x > serial: <superuser required> UEFI: American Megatrends v: 4602 > date: 02/23/2023 > CPU: > Info: 16-core model: AMD Ryzen 9 5950X bits: 64 type: MT MCP cache: > L2: 8 MiB > Speed (MHz): avg: 2537 min/max: 2200/5980 cores: 1: 2200 2: 4000 3: 2200 > 4: 2200 5: 2200 6: 2200 7: 2200 8: 2200 9: 4000 10: 2200 11: 2200 12: > 2200 > 13: 2200 14: 2200 15: 2200 16: 2200 17: 4000 18: 4000 19: 2200 20: 2200 > 21: 3998 22: 2200 23: 2200 24: 2200 25: 2200 26: 2200 27: 2200 28: 2200 > 29: 2200 30: 2200 31: 2200 32: 4000 > Graphics: > Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT] > driver: amdgpu v: kernel > Device-2: Logitech C922 Pro Stream Webcam driver: snd-usb-audio,uvcvideo > type: USB > Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 23.2.6 > compositor: kwin_wayland driver: X: loaded: amdgpu > unloaded: modesetting,radeon failed: fbdev,vesa dri: radeonsi gpu: amdgpu > resolution: 1: 1920x1080 2: 1920x1080 > API: EGL v: 1.5 drivers: radeonsi,swrast > platforms: wayland,x11,surfaceless,device > API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.0.5-arch1.1 > renderer: AMD Radeon RX 6700 XT (radeonsi navi22 LLVM 17.0.6 DRM 3.57 > 6.8.7-artix1-1) > API: Vulkan v: 1.3.279 drivers: radv,llvmpipe surfaces: xcb,xlib,wayland > Audio: > Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel > Device-2: AMD Starship/Matisse HD Audio driver: snd_hda_intel > Device-3: Logitech C922 Pro Stream Webcam driver: snd-usb-audio,uvcvideo > type: USB > API: ALSA v: k6.8.7-artix1-1 status: kernel-api > Server-1: PulseAudio v: 17.0 status: active > Network: > Device-1: Broadcom BCM4360 802.11ac Dual Band Wireless Network Adapter > driver: wl > IF: wlan0 state: up mac: b8:09:8a:44:8a:35 > Device-2: Intel Ethernet I225-V driver: igc > IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 04:42:1a:e7:72:ed > Bluetooth: > Device-1: Apple Bluetooth Host Controller driver: btusb type: USB > Report: rfkill ID: hci0 state: up address: see --recommends > Drives: > Local Storage: total: 5.05 TiB used: 1.03 TiB (20.5%) > ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 980 500GB size: 465.76 GiB > ID-2: /dev/nvme1n1 model: AGAMMIXS70B-2T-CS size: 1.86 TiB > ID-3: /dev/sda vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB > ID-4: /dev/sdb vendor: Western Digital model: WD2003FZEX-00SRLA0 > size: 1.82 TiB > Partition: > ID-1: / size: 425.39 GiB used: 36.18 GiB (8.5%) fs: ext4 dev: > /dev/nvme0n1p3 > ID-2: /boot/efi size: 511 MiB used: 296 KiB (0.1%) fs: vfat > dev: /dev/nvme0n1p1 > ID-3: /home size: 1.83 TiB used: 1021.91 GiB (54.5%) fs: ext4 > dev: /dev/nvme1n1p1 > Swap: > ID-1: swap-1 type: partition size: 32 GiB used: 0 KiB (0.0%) > dev: /dev/nvme0n1p2 > Sensors: > System Temperatures: cpu: 40.8 C mobo: N/A gpu: amdgpu temp: 55.0 C > Fan Speeds (rpm): N/A gpu: amdgpu fan: 0 > Info: > Memory: total: 64 GiB note: est. available: 62.7 GiB used: 5.4 GiB (8.6%) > Processes: 528 Uptime: 7m Shell: Bash inxi: 3.3.34 > > Updated to Arch Linux's KDE 6.0.4 and this behavior is still occurring.
Indeed.
I an am also experiencing the bug after release on Fedora 40.
Same for me on Fedora 40 - Wayland - Nvidia.
Just installed plasma 6.1 beta (6.0.90 Archlinux wayland) and the bug still exists
Yes, it don't have to be center aligned you just cant have two panels in same line for example at top left and top right corners at same time in same line.
One possible workaround is to create a single panel, separate it into sections with panel spacers, and use [Panel Colorizer](https://discuss.kde.org/t/panel-colorizer-for-plasma-6/10675) to make the panel background transparent and add background colors to specific sections. It can be made to look similar enough to how it should be, though not 100%.
Same hardware configuration as before. KDE Plasma Version: 6.1.90 KDE Frameworks Version: 6.6.0 Qt Version: 6.8.0 Kernel Version: 6.11.1-arch1-1-znver3 (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor Memory: 62.7 GB of RAM Graphics Processor: AMD Radeon RX 6700 XT Three seperate panels (left, center, and right). All align perfectly with X11 .. Wayland they are staggered under each other;'s height eating up a lot of vertical space.
Created attachment 175047 [details] Screenshot demonstrating that this bug affects left-aligned panels too I am running into this with left-aligned panels too.
I only reproduce this bug if one or both of the panels is set to Always Visible. If both panels are set to Dodge Windows or set one of them to Auto Hide or Windows Go Below the bug doesn't occur and they both snap to the sides as expected.
I believe I saw Nate Graham post a comment in one of the recent(ish) TWiK posts that this issue was related to Wayland and missing parts in Wayland. Is there any update on this bug and any motion from Wayland?
*** Bug 500143 has been marked as a duplicate of this bug. ***
*** Bug 500668 has been marked as a duplicate of this bug. ***
I was also able to reproduce the bug described in 500668 which has two panels, one left and one right. There was no center panel. The two panels were able to share the bottom part of the screen, the problem there was that notifications and widgets aren't able to get very close. Visually there's a large margin above the bottom panels.
I just tested this issue again and it is still reproducible in KDE Plasma Wayland version 6.3.1. Panels aligned on the same screen edge still can't share the edge. Please change the name back to the previous name. This issue is not about notification position.
*** Bug 500698 has been marked as a duplicate of this bug. ***
*** Bug 500083 has been marked as a duplicate of this bug. ***
Created attachment 179228 [details] sway-with-plasmashell-panels-positioned-correct Today I was trying to fix this issue because its so annoying no one was trying to solve it i wasnt able to solve it yet, though. I found up that it looks like the issue is not related to plasmashell; looks like it's related to kwin's implementation of the layer-shell protocol. I'm not sure, but I think it's that KWin doesn't handle the exclusiveZone correctly. shortly what i did: 1- i cloned kde-builder and i ran kde-builder workspace to build plasma, then i logged in to plasma development (wayland) session 2- i cloned https://github.com/wmww/gtk-layer-shell/ and fiddled around gtk-layer-demo 3- then i created 3 panels (on the left side of the screen, all of them are fit content; one is top, one is bottom, and one is center aligned). 4- i logged out and then logged into Sway and ran `plasmashell` command in Sway. 5- The panels were correctly positioned (included in the attachment) 6- i have started to try to read and understand the code/logic behind the panels and layer-shell implementation in kwin
Created attachment 179229 [details] kwin-with-plasmashell-panels-positioned-wrong
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/5304
Git commit 11523d82d672c8af8a7aeb5388d1000227503f64 by Niccolò Venerandi. Committed on 11/03/2025 at 15:33. Pushed by niccolove into branch 'master'. Only make thickest visible panel reserve space for each edge All other panels will ignore exclusive spaces on edges; this allows to have multiple panels on the same screen edge, all touching the screen edge instead of stacking. This was the status quo previous to the introduction of layershells; it's not perfect (as it allows for panels to intersect without a clear way to decide which one should be shown above) but it's an improvement to the status quo. Related: bug 500668 M +6 -2 shell/panelview.cpp M +18 -24 shell/shellcorona.cpp M +1 -0 shell/shellcorona.h https://invent.kde.org/plasma/plasma-workspace/-/commit/11523d82d672c8af8a7aeb5388d1000227503f64
I've tried migrating from 1 panel to my original desire of 2 panels because it's been a month since this fix went in. Unfortunately, after I did that and even after rebooting, the issue is still able to be reproduced. I have `plasma-desktop` version 6.3.4. I've looked at the schedule for Plasma releases and seen that 6.4 is coming in 2 months, which is very far away. If this issue's fix will only be deployed with Plasma 6.4, that's months of this bug still. Is there a possibility that the fix can be backported to the 6.3.x series so that we don't have to wait multiple more months to get proper multi-panel behavior? Thank you for reading.