Plasma-desktop 6.5.6-1 breaks panel widget dragging in edit mode

Is anyone else having a problem with the panel after updating to plasma-desktop 6.5.6-1?

On plasma-desktop 6.5.5-1, when I right-click a panel and then click Show Panel Configuration, hovering the mouse over a panel item shows the drag handle, so the item can be repositioned in the panel as desired.

See the screenshot below for what I mean:

The behavior shown in the screenshot is the expected one.

However, after updating to plasma-desktop 6.5.6-1, this is no longer possible.

Steps I used to reproduce the problem

Recently, I went to https://manjaro.org/products/download/x86 and downloaded the latest stable KDE Plasma ISO.

After downloading it, I created a bootable USB drive using Manjaro’s own Image Writer.

Then I formatted my computer and installed the system.

As soon as the installation finished and the system booted for the first time, I tested the panel editing functionality, and it was working correctly.

Then I installed all pending updates using the Pamac GUI.

Among those updates was plasma-desktop 6.5.6-1.

After installing all updates, including plasma-desktop 6.5.6-1, the ability to drag widgets/items in the panel stops working.

However, if I add plasma-desktop 6.5.6-1 to Pamac’s ignore list, the panel continues to work normally as expected.

Based on the tests I’ve done, the problem occurs in both Wayland and X11.

Information about my environment

=== System Version ===
   ~  lsb_release -a  :check_mark:
LSB Version: n/a
Distributor ID: ManjaroLinux
Description: Manjaro Linux
Release: 26.0.4
Codename: Anh-Linh  :check_mark:
=== Kernel ===
   ~  uname -a  :check_mark:
Linux user-b450mgaming 6.18.18-1-MANJARO #1 SMP PREEMPT_DYNAMIC Fri, 13 Mar 2026 18:47:36 +0000 x86_64 GNU/Linux
=== Graphical Interface ===
   ~  echo “Plasma: $(plasmashell --version)”  :check_mark:
QThreadStorage: entry 7 destroyed before end of thread 0x55aa3e6f4e20
QThreadStorage: entry 2 destroyed before end of thread 0x55aa3e6f4e20
QThreadStorage: entry 1 destroyed before end of thread 0x55aa3e6f4e20
Plasma: plasmashell 6.5.6
KDE Services:
   ~  echo “Session: $XDG_SESSION_DESKTOP”  :check_mark:
Session: KDE
   ~  echo “Desktop: $XDG_CURRENT_DESKTOP”  :check_mark:
Desktop: KDE
=== Hardware ===
   ~  inxi -Fxxxza --no-host  :check_mark:
System:
Kernel: 6.18.18-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.18-x86_64
root=UUID=1b9528a2-919b-4584-8b25-54e584a46883 rw rootflags=subvol=@
quiet splash resume=UUID=808b28b8-8b3a-4aef-9d8b-9a6b3778dcf9
udev.log_priority=3
Desktop: KDE Plasma v: 6.5.6 tk: Qt v: N/A info: frameworks v: 6.24.0
wm: kwin_wayland vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
Type: Desktop Mobo: Gigabyte model: B450M GAMING v: x.x
serial: uuid: Firmware: UEFI
vendor: American Megatrends v: F41 date: 07/22/2019
CPU:
Info: model: AMD Ryzen 5 3600X bits: 64 type: MT MCP arch: Zen 2 gen: 2
level: v3 note: check built: 2020-22 process: TSMC n7 (7nm)
family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701034
Topology: cpus: 1x dies: 1 clusters: 1 cores: 6 threads: 12 tpc: 2
smt: enabled cache: L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB
desc: 6x512 KiB L3: 32 MiB desc: 2x16 MiB
Speed (MHz): avg: 2065 min/max: 2200/4409 boost: enabled scaling:
driver: acpi-cpufreq governor: schedutil cores: 1: 2065 2: 2065 3: 2065
4: 2065 5: 2065 6: 2065 7: 2065 8: 2065 9: 2065 10: 2065 11: 2065 12: 2065
bogomips: 91034
Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a
ssse3 svm
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: ghostwrite status: Not affected
Type: indirect_target_selection status: Not affected
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: old_microcode status: Not affected
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: untrained return thunk; SMT enabled with STIBP
protection
Type: spec_rstack_overflow mitigation: Safe RET
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; STIBP:
always-on; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds status: Not affected
Type: tsa status: Not affected
Type: tsx_async_abort status: Not affected
Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX
470/480/570/570X/580/580X/590] vendor: ASUSTeK driver: amdgpu v: kernel
arch: GCN-4 code: Arctic Islands process: GF 14nm built: 2016-20 pcie:
gen: 3 speed: 8 GT/s lanes: 16 ports: active: HDMI-A-2 empty: DP-1, DP-2,
DVI-D-1, HDMI-A-1 bus-ID: 0a:00.0 chip-ID: 1002:67df class-ID: 0300
temp: 44.0 C
Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
compositor: kwin_wayland driver: X: loaded: amdgpu unloaded: modesetting
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: 0
Monitor-1: HDMI-A-2 model: LG (GoldStar) 25UM58G serial:
built: 2015 res: mode: 2560x1080 hz: 75 scale: 100% (1) dpi: 97 gamma: 1.2
size: 677x290mm (26.65x11.42") diag: 730mm (28.8") modes: max: 2560x1080
min: 720x400
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
wayland: drv: radeonsi x11: drv: radeonsi
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 26.0.2-arch1.1
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 580 Series (radeonsi
polaris10 ACO DRM 3.64 6.18.18-1-MANJARO) device-ID: 1002:67df
memory: 7.81 GiB unified: no display-ID: :1.0
API: Vulkan v: 1.4.341 layers: 2 device: 0 type: discrete-gpu name: AMD
Radeon RX 580 Series (RADV POLARIS10) driver: mesa radv v: 26.0.2-arch1.1
device-ID: 1002:67df surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdpyinfo,xprop
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere HDMI Audio [Radeon RX
470/480 / 570/580/590] vendor: ASUSTeK driver: snd_hda_intel v: kernel
pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s
bus-ID: 0a:00.1 chip-ID: 1002:aaf0 class-ID: 0403
Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
vendor: Gigabyte 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.18.18-1-MANJARO status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: JACK v: 1.9.22 status: off tools: N/A
Server-3: PipeWire v: 1.6.2 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: Gigabyte driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: f000 bus-ID: 09:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp9s0 state: up speed: 100 Mbps duplex: full mac:
Info: services: NetworkManager,systemd-timesyncd
Drives:
Local Storage: total: 1.59 TiB used: 662.54 GiB (40.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
model: SSD 970 EVO Plus 250GB size: 232.89 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial:
fw-rev: 2B2QEXM7 temp: 33.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital
model: WD10SPZX-21Z10T0 size: 931.51 GiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 5400 serial:
fw-rev: 1A02 scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: Toshiba model: MQ01ABF050
size: 465.76 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 5400 serial: fw-rev: 6L scheme: GPT
Partition:
ID-1: / raw-size: 216.38 GiB size: 216.38 GiB (100.00%)
used: 43.05 GiB (19.9%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3
ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
used: 664 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 216.38 GiB size: 216.38 GiB (100.00%)
used: 43.05 GiB (19.9%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3
ID-4: /var/log raw-size: 216.38 GiB size: 216.38 GiB (100.00%)
used: 43.05 GiB (19.9%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3
Swap:
Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
compressor: zstd max-pool: 20%
ID-1: swap-1 type: partition size: 16 GiB used: 40.3 MiB (0.2%)
priority: -2 dev: /dev/nvme0n1p2 maj-min: 259:2
Sensors:
System Temperatures: cpu: 47.0 C mobo: 31.0 C gpu: amdgpu temp: 44.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 1263
Info:
Memory: total: 16 GiB available: 15.56 GiB used: 8.81 GiB (56.6%)
Processes: 485 Power: uptime: 6d 23h 16m states: freeze,mem,disk
suspend: deep avail: s2idle wakeups: 0 hibernate: platform avail: shutdown,
reboot, suspend, test_resume image: 6.16 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 259 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1354 libs: 354 tools: pamac pm: flatpak pkgs: 0
Compilers: gcc: 15.2.1 Shell: Zsh v: 5.9 running-in: konsole inxi: 3.3.40

Yes, this is quite well known and has been talked about quite a bit recently.

It’s gone with 6.6 - but apart from that, it’s a pretty solid release.

You can have a go at moving things by editing the config and swapping the items manually (numbers list showing the order):

cp ~/.config/plasma-org.kde.plasma.desktop-appletsrc ~/.config/plasma-org.kde.plasma.desktop-appletsrc.backup

Backup because this kind of hack is always a touch risky…

Edit and find AppletOrder to edit the numbers in AppletOrder

systemctl --user restart plasma-plasmashell.service should refresh everything and get the new config loaded.

1 Like

Thanks for the reply.

I tested again on the stable branch.

My current versions are:

  • plasma-desktop 6.5.6-1.1
  • plasma-workspace 6.5.6-2

After updating plasma-desktop and rebooting the system, the problem still persists.

I still cannot reorder the panel widgets/items normally in edit mode after the update.

So, at least in my case, having plasma-workspace 6.5.6-2 does not solve the issue.

Since I created a full system snapshot with Timeshift, I am going to roll back to the point where plasma-desktop was being ignored in Pamac updates and was still on version 6.5.5-1.

For now, I will keep plasma-desktop on version 6.5.5-1 and continue ignoring updates for it in Pamac.

Still, it is useful to know that this is already a known issue, and I appreciate the suggested workaround of manually editing the order in the ~/.config/plasma-org.kde.plasma.desktop-appletsrc file.

I’m waiting for version 6.6 to be released on the stable channel.

Thanks again.

Nobody said 6.5.6-2 would solve the issue.

Thanks for the clarification.

You are right: in this topic, nobody said that plasma-workspace 6.5.6-2 would solve the issue.

Ben only said that the problem is gone with 6.6.

I mentioned plasma-workspace 6.5.6-2 because I had seen a report in another topic saying that it might fix the issue there, so I decided to test it on my system as well.

In my case, on the stable branch, the problem still persists with:

  • plasma-desktop 6.5.6-1.1
  • plasma-workspace 6.5.6-2

So for now, I will stay on plasma-desktop 6.5.5-1 and wait until 6.6 reaches the stable branch.

Thanks again for the clarification.

Same bug here. Cannot drag and move any widget on desktop toolbar/panel. When the mouse is over the widget, the whole panel is detected instead of the widget, so I’m not able to move them.

I tried:

  • Delete current panel and create new from scratch
  • Reset plasma settings
  • Reset kwin settings
  • Reinstall whole plasma environment
  • Create new user and log in
  • Create x11 environment and log in

But still not working.

Has anyone solved it? Maybe a downgrade? Which version?

Welcome to the Manjaro community @gmm96

Downgrades are not recommended as they place your system into an unsupported state. This especially applies to desktop environments such as Plasma, where the previous version may have been built against a different version of Qt or other libraries, causing breakage when the downgraded Plasma can’t find the older versions of the packages it was built with.

Instead, if you really need the movable widgets, I would recommend that you switch to Testing branch, which is currently on Plasma 6.6.3:

mbn info plasma-desktop -q | grep -Ev 'Name|Repository|Packager'
Branch         : archlinux
Version        : 6.6.3-2
Build Date     : Sat 28 Mar 2026 23:48:58 
Branch         : unstable
Version        : 6.6.3-2
Build Date     : Sat 28 Mar 2026 23:48:58 
Branch         : testing
Version        : 6.6.3-2
Build Date     : Sat 28 Mar 2026 23:48:58 
Branch         : stable
Version        : 6.5.6-1.1
Build Date     : Tue 31 Mar 2026 14:19:08 

Switching branches is a simple process (and don’t worry - Testing is quite stable - I’ve been running it trouble-free for nearly 2 years).

To switch to Testing branch:

sudo pacman-mirrors --api --set-branch testing

or, to switch to Unstable branch:

sudo pacman-mirrors --api --set-branch unstable

After you changed the branch, rebuild the mirrorlist and update your packages:

sudo pacman-mirrors --continent && sudo pacman -Syyu
2 Likes

File Path : The configuration is stored in ~/.config/plasma-org.kde.plasma.desktop-appletsrc .

Open that with Kate, then hit F4 to get a terminal pane open too. You can then do:

cd ~/.config
cp ~/.config/plasma-org.kde.plasma.desktop-appletsrc ~/.config/plasma-org.kde.plasma.desktop-appletsrc.bak
kate config

So then it’s open in the editor, CtrlF to filter, type ‘Order’
You should find something like this, plotting the order of the applets enabled.
AppletOrder=56;112;23;

Simple, the middle applet is 112 - move it to the end:
AppletOrder=56;23;112;

CtrlS to save, then in the terminal:
systemctl --user restart plasma-plasmashell.service

If it works, come back and give it a :white_check_mark:

In my case, I also have the problem when I update to the stable version:

  • plasma-desktop 6.5.6-1.1

Therefore, at the moment, the only practical solution I know in the stable version is manually editing the AppletOrder, as described by Ben.

Thank you for adding those test results. They are very helpful.

Currently, I am using version 6.5.5-1 of plasma-desktop and the problem does not occur in this version.