Created attachment 182672 [details]
journalctl -f catching some relevant info

as additional info, this happens when upgrading from 6.3.5, on a system with vanilla breeze theme, no extra modifications, just the kora icon theme.

oh, another additional note: when trying to drag and drop files from eg, a flash drive, or any other folder on the system from dolphin into the desktop, it also does nothing, when on 6.3.5, it did opened the menu to copy/move/link etc actions

more additional info: when creating a .desktop for the Trash bin, the bug fixes itself for no reason.

correction: it seems that the drag and drop with the folder widget only works as expected when dragging and dropping from the Trash.desktop icon I made, but for every other regular folder, it doesn't work, as described on this bug report.

this is the code I used to make the Trash.desktop so I can have a "recycle bin" on my desktop:

[Desktop Entry]
Comment=Contains deleted files and folders
Icon=user-trash-full
EmptyIcon=user-trash
Type=Link
URL=trash:/
Name=Trash
OnlyShowIn=KDE;

(In reply to LuneLovehearn from comment #4)
> correction: it seems that the drag and drop with the folder widget only
> works as expected when dragging and dropping from the Trash.desktop icon I
> made, but for every other regular folder, it doesn't work, as described on
> this bug report.
> 
> this is the code I used to make the Trash.desktop so I can have a "recycle
> bin" on my desktop:
> 
> [Desktop Entry]
> Comment=Contains deleted files and folders
> Icon=user-trash-full
> EmptyIcon=user-trash
> Type=Link
> URL=trash:/
> Name=Trash
> OnlyShowIn=KDE;

correction: drag and drop does work with the trash.desktop, from the folder widget into desktop, and from files on desktop into trash.
it also works when dragging files from the desktop into dolphin, but not from dolphin into the desktop, after further testing.

This is a very strange set of symptoms.

Can you create a new clean user account on the same computer, make no customizations, and then still reproduce the bug? Or does it stop happening?

How did you install Plasma on your system?

*** Bug 506190 has been marked as a duplicate of this bug. ***

(In reply to Nate Graham from comment #6)
> This is a very strange set of symptoms.
> 
> Can you create a new clean user account on the same computer, make no
> customizations, and then still reproduce the bug? Or does it stop happening?
> 
> How did you install Plasma on your system?

this is a clean install of arch linux with archinstall. it had plasma 6.3.5 but I just upgraded it to 6.4.1
there are no customizations beyond just using the global menu and a top panel. 
I also used a virtual machine with arch and plasma 6.3.5, with no customizations, and the bug still happens.
the VM has an entire different user.

(In reply to LuneLovehearn from comment #8)
> (In reply to Nate Graham from comment #6)
> > This is a very strange set of symptoms.
> > 
> > Can you create a new clean user account on the same computer, make no
> > customizations, and then still reproduce the bug? Or does it stop happening?
> > 
> > How did you install Plasma on your system?
> 
> this is a clean install of arch linux with archinstall. it had plasma 6.3.5
> but I just upgraded it to 6.4.1
> there are no customizations beyond just using the global menu and a top
> panel. 
> I also used a virtual machine with arch and plasma 6.3.5, with no
> customizations, and the bug still happens.
> the VM has an entire different user.

if you mean a clean user with plasma 6.3.5 and upgrade it to 6.4.1, I can try. If you mean another user after the upgrade, I also can try.

I'm not able to reproduce this with an existing user on git-master or KDE Neon with Plasma 6.4.1, KF 6.15.0, Qt 6.9.0, just as a data point

Can you try with a new user on your upgraded 6.4.1 system? Thanks.

(In reply to TraceyC from comment #10)
> I'm not able to reproduce this with an existing user on git-master or KDE
> Neon with Plasma 6.4.1, KF 6.15.0, Qt 6.9.0, just as a data point
> 
> Can you try with a new user on your upgraded 6.4.1 system? Thanks.

I just made a new user called test, and the bug still happens.

Created attachment 182711 [details]
video showcasing the bug even with a new user

here's a video showcasing the bug, on a clean new user, on vanilla arch upgraded from plasma 6.3.5

(In reply to LuneLovehearn from comment #12)
> Created attachment 182711 [details]
> video showcasing the bug even with a new user
> 
> here's a video showcasing the bug, on a clean new user, on vanilla arch
> upgraded from plasma 6.3.5

as you can see, it not only affects the desktop, but also dolphin to some degree. 
I'll load plasma 6.4.1 on another PC I have and do same testing, while trying to fetch info from journalctl.

I can reproduce on:

* Fedora KDE 42 device with Plasma 6.4.0
* EndeavourOS VM with Plasma 6.4.1
* KDE Neon VM with Plasma 6.4.1

I cannot reproduce on:

* Kubuntu 25.04 VM with Plasma 6.3.5

Copy-pasting to the desktop by using Ctrl+C from Dolphin, clicking on the Desktop, then pressing Ctrl+V, does work.

Thanks!

Created attachment 182716 [details]
footage of the issue

As requested, I made a new user, on a real PC with cachyOS (arch based) with plasma 6.4.1
the issue persists, and this video shows it.

(In reply to John Kizer from comment #14)
> I can reproduce on:
> 
> * Fedora KDE 42 device with Plasma 6.4.0
> * EndeavourOS VM with Plasma 6.4.1
> * KDE Neon VM with Plasma 6.4.1
> 
> I cannot reproduce on:
> 
> * Kubuntu 25.04 VM with Plasma 6.3.5
> 
> Copy-pasting to the desktop by using Ctrl+C from Dolphin, clicking on the
> Desktop, then pressing Ctrl+V, does work.
> 
> Thanks!

I can confirm that copy/cut-paste works when using keyboard shortcuts from dolphin to the desktop. It's the drag and drop not triggering the menu to select copy, paste, etc when using the desktop

the only useful info I could get from the journal is an event related to the mouse/touchpad, that shows up when trying to drag and drop files on the desktop:

```

jun 27 00:42:58 Acer-Aspire-4743 plasmashell[2750]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemtray/contents/ui/items/PlasmoidItem.qml:208: TypeError: Cannot read property 'fullRepresentationItem' of null
jun 27 00:42:58 Acer-Aspire-4743 plasmashell[2750]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemtray/contents/ui/items/PlasmoidItem.qml:201: TypeError: Cannot read property 'compactRepresentationItem' of null
jun 27 00:42:58 Acer-Aspire-4743 plasmashell[2750]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemtray/contents/ui/items/PlasmoidItem.qml:24: TypeError: Cannot read property 'toolTipMainText' of null
jun 27 00:43:26 Acer-Aspire-4743 wpa_supplicant[575]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-72 noise=-95 txrate=1000
jun 27 00:43:37 Acer-Aspire-4743 plasmashell[2750]: cannot grab mouse: no event is currently being delivered
jun 27 00:43:43 Acer-Aspire-4743 plasmashell[2750]: cannot grab mouse: no event is currently being delivered
jun 27 00:43:45 Acer-Aspire-4743 plasmashell[2750]: cannot grab mouse: no event is currently being delivered
jun 27 00:43:46 Acer-Aspire-4743 plasmashell[2750]: cannot grab mouse: no event is currently being delivered
jun 27 00:43:47 Acer-Aspire-4743 wpa_supplicant[575]: wlan0: CTRL-EVENT-BEACON-LOSS
jun 27 00:43:49 Acer-Aspire-4743 systemd[1]: Starting Daily man-db regeneration...
jun 27 00:43:54 Acer-Aspire-4743 plasmashell[2750]: cannot grab mouse: no event is currently being delivered
jun 27 00:43:57 Acer-Aspire-4743 plasmashell[2750]: cannot grab mouse: no event is currently being delivered
jun 27 00:44:13 Acer-Aspire-4743 systemd[1]: man-db.service: Deactivated successfully.
jun 27 00:44:13 Acer-Aspire-4743 systemd[1]: Finished Daily man-db regeneration.
jun 27 00:44:13 Acer-Aspire-4743 systemd[1]: man-db.service: Consumed 5.238s CPU time, 135.1M memory peak.
jun 27 00:44:18 Acer-Aspire-4743 wpa_supplicant[575]: wlan0: CTRL-EVENT-BEACON-LOSS
jun 27 00:44:37 Acer-Aspire-4743 wpa_supplicant[575]: wlan0: CTRL-EVENT-BEACON-LOSS```

(In reply to LuneLovehearn from comment #17)
> the only useful info I could get from the journal is an event related to the
> mouse/touchpad, that shows up when trying to drag and drop files on the
> desktop:
> 
> ```
> 
> jun 27 00:42:58 Acer-Aspire-4743 plasmashell[2750]:
> file:///usr/share/plasma/plasmoids/org.kde.plasma.systemtray/contents/ui/
> items/PlasmoidItem.qml:208: TypeError: Cannot read property
> 'fullRepresentationItem' of null
> jun 27 00:42:58 Acer-Aspire-4743 plasmashell[2750]:
> file:///usr/share/plasma/plasmoids/org.kde.plasma.systemtray/contents/ui/
> items/PlasmoidItem.qml:201: TypeError: Cannot read property
> 'compactRepresentationItem' of null
> jun 27 00:42:58 Acer-Aspire-4743 plasmashell[2750]:
> file:///usr/share/plasma/plasmoids/org.kde.plasma.systemtray/contents/ui/
> items/PlasmoidItem.qml:24: TypeError: Cannot read property 'toolTipMainText'
> of null
> jun 27 00:43:26 Acer-Aspire-4743 wpa_supplicant[575]: wlan0:
> CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-72 noise=-95 txrate=1000
> jun 27 00:43:37 Acer-Aspire-4743 plasmashell[2750]: cannot grab mouse: no
> event is currently being delivered
> jun 27 00:43:43 Acer-Aspire-4743 plasmashell[2750]: cannot grab mouse: no
> event is currently being delivered
> jun 27 00:43:45 Acer-Aspire-4743 plasmashell[2750]: cannot grab mouse: no
> event is currently being delivered
> jun 27 00:43:46 Acer-Aspire-4743 plasmashell[2750]: cannot grab mouse: no
> event is currently being delivered
> jun 27 00:43:47 Acer-Aspire-4743 wpa_supplicant[575]: wlan0:
> CTRL-EVENT-BEACON-LOSS
> jun 27 00:43:49 Acer-Aspire-4743 systemd[1]: Starting Daily man-db
> regeneration...
> jun 27 00:43:54 Acer-Aspire-4743 plasmashell[2750]: cannot grab mouse: no
> event is currently being delivered
> jun 27 00:43:57 Acer-Aspire-4743 plasmashell[2750]: cannot grab mouse: no
> event is currently being delivered
> jun 27 00:44:13 Acer-Aspire-4743 systemd[1]: man-db.service: Deactivated
> successfully.
> jun 27 00:44:13 Acer-Aspire-4743 systemd[1]: Finished Daily man-db
> regeneration.
> jun 27 00:44:13 Acer-Aspire-4743 systemd[1]: man-db.service: Consumed 5.238s
> CPU time, 135.1M memory peak.
> jun 27 00:44:18 Acer-Aspire-4743 wpa_supplicant[575]: wlan0:
> CTRL-EVENT-BEACON-LOSS
> jun 27 00:44:37 Acer-Aspire-4743 wpa_supplicant[575]: wlan0:
> CTRL-EVENT-BEACON-LOSS```

So, it's not just on a VM, but also on bare metal that the bug happens.

Sadly I can't repro this, I get the context menu popup as expected.


Operating System: Fedora Linux 42
KDE Plasma Version: 6.4.80
KDE Frameworks Version: 6.16.0
Qt Version: 6.9.1
Kernel Version: 6.15.4-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 did notice something:

If I move the other icon on the edge of the icon below, it snaps next to it

If I move the other icon on top of the icon below, it asks me for the context menu

I am not sure if this is related, but the hitboxes seem off.

another user is reporting this issue as per this post:
https://www.reddit.com/r/kde/comments/1lme9fy/drag_and_drop_menu_not_showing_when_i_try_to/
the following bug may be a duplicated of this one: https://bugs.kde.org/show_bug.cgi?id=505984

*** Bug 505984 has been marked as a duplicate of this bug. ***

Huh, now I can repro this!

What I did was have dolphin open, changed between activities and tried to drag and drop to desktop. It worked before I started changing activities.

Have the reporters here also changed activities or virtual desktops before trying to do anything with the icons?

Anyhow, will investigate now that I can repro it.

A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kio/-/merge_requests/1923

(In reply to Akseli Lahtinen from comment #23)
> Huh, now I can repro this!
> 
> What I did was have dolphin open, changed between activities and tried to
> drag and drop to desktop. It worked before I started changing activities.
> 
> Have the reporters here also changed activities or virtual desktops before
> trying to do anything with the icons?
> 
> Anyhow, will investigate now that I can repro it.

no, as I don't use activities, I only use the virtual desktops. but on this testing, the vanilla settings were used, only 1 desktop, 1 activity.
making a new user was also used for testing and the bug still happens.

(In reply to LuneLovehearn from comment #25)
> (In reply to Akseli Lahtinen from comment #23)
> > Huh, now I can repro this!
> > 
> > What I did was have dolphin open, changed between activities and tried to
> > drag and drop to desktop. It worked before I started changing activities.
> > 
> > Have the reporters here also changed activities or virtual desktops before
> > trying to do anything with the icons?
> > 
> > Anyhow, will investigate now that I can repro it.
> 
> no, as I don't use activities, I only use the virtual desktops. but on this
> testing, the vanilla settings were used, only 1 desktop, 1 activity.
> making a new user was also used for testing and the bug still happens.

glad that (In reply to Akseli Lahtinen from comment #23)
> Huh, now I can repro this!
> 
> What I did was have dolphin open, changed between activities and tried to
> drag and drop to desktop. It worked before I started changing activities.
> 
> Have the reporters here also changed activities or virtual desktops before
> trying to do anything with the icons?
> 
> Anyhow, will investigate now that I can repro it.

glad you can dig into the bug, and I saw a merge request, hope this gets resolved.

Git commit 2132b6ceb22f9e5890dd76e114215987db7deb5f by Méven Car, on behalf of Akseli Lahtinen.
Committed on 08/07/2025 at 08:48.
Pushed by meven into branch 'master'.

DropJob: Emit popupMenuAboutToShow after setting things up

When adding actions to the popup, we were emitting popupMenuAboutToShow
too early, before we had the actions added. This could cause race
conditions, especially if there are plugin actions for the item.

We need to make sure our popup and its itemProps are done and ready
before emitting the signal. If we emit too early, we sometimes
ended up finishing making up the menu after DropJob::showMenu was
called, which would have nothing in it's m_menus set and thus do
nothing.

M  +1    -2    src/widgets/dropjob.cpp

https://invent.kde.org/frameworks/kio/-/commit/2132b6ceb22f9e5890dd76e114215987db7deb5f

Good job! When the update will be available?

Frameworks 6.17, unless KDE or distros backport it.