SUMMARY Right-click on the desktop -> Configure Desktop and Wallpaper -> Mouse Actions There was exactly one rule defined for the right mouse button - I guess it read open context menu, but I don't remember. I've clicked on the "Add Action" button and interestingly the only entry ("right click") vanished and instead I had comboboxes to choose a mouse button and a desired action. Weird UI? Bug? Anyway, choosing "Scroll desktop" with "Mouse wheel" and hitting apply, there was only this entry now shown. _Finally I closed the window, noticed that I could now scroll with the wheel trough the VDs, but the context menu to configure the desktop does not open anymore._ Also I don't find any option in the System Settings to change this behavior now! Krunner doesn't give me any relevant results when I search for "configure desktop" or "desktop settings". In my opinion it would make sense to put all these settings into System Settings, then it'd be easier to find the settings > The nice thing about KDE is that so much is configurable, > but finding configuration settings is still a challenge in Plasma 6. > For example, the aforementioned setting to scroll virtual desktops > is found in the Desktop Folder Settings application, > but not in the System Settings application under the Virtual Desktop settings. as of https://lwn.net/Articles/963851/ and I'd likely not have the issue with a lost context menu. STEPS TO REPRODUCE 1. Right-click on the desktop -> Configure Desktop and Wallpaper -> Mouse Actions 2. Click on "Add Action" button 3. Add any action for any button, eg as above Switch VDs with Vertical Scroll Wheel 4. Hit apply OBSERVED RESULT -> 2. The only defined right click rule is no longer shown -> 4. Only the rule defined in 3. is shown The desktop context menu is gone. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240229 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Kernel Version: 6.7.6-1-default (64-bit) Graphics Platform: Wayland
I am looking for solutions / workarounds and found :D > In older versions of Plasma it was possible to edit the right-click menu > and remove the Configure Desktop item and its keyboard shortcut. [1] https://userbase.kde.org/Configure_your_desktop
This is how the first lines of `~/.config/plasma-org.kde.plasma.desktop-appletsrc` right now look for me: ``` [ActionPlugins][0] wheel:Vertical;NoModifier=org.kde.switchdesktop [ActionPlugins][0][RightButton;NoModifier] _add panel=true _context=true _display_settings=true _lock_screen=false _logout=false _run_command=false _sep1=true _sep2=true _sep3=true _wallpaper=true add widgets=true configure=true configure shortcuts=false edit mode=true manage activities=true remove=true [ActionPlugins][1] RightButton;NoModifier=org.kde.contextmenu [Containments][2] activityId= formfactor=2 immutability=1 lastScreen=0 location=3 plugin=org.kde.panel wallpaperplugin=org.kde.image ````
I've replaced `wheel:Vertical;NoModifier=org.kde.switchdesktop` by `RightButton;NoModifier=org.kde.contextmenu` and re-logged in and now it the context menu is back. This is a weird bug that this could happen (so easily).
I've tried to reproduce it on Fedora 39 and there the UI is also weird when adding another action, but at least ``` [ActionPlugins][0] RightButton;NoModifier=org.kde.contextmenu wheel:Vertical;NoModifier=org.kde.switchdesktop ```` the last line here is added and does not replace the RightButton action.
I tried it again several times on openSUSE TW: It looks like it can happen randomly that the wrong line is replaced instead that an action is added. There's surely something wrong or racy. (Also, it's not good that the user can so easily remove the context menu by simply removing the corresponding action and loosing the ability to revert it easily.)
I don't know how the right button action could have disappeared, but it's possible you fell victim to this horrible UI (which we know is horrible) and it happened by accident. I can't reproduce the issue myself, but I unfortunately do already know how it works, so I'm probably failing to interact with it like a normal person would. Let's mark this as a duplicate of Bug 404600 and make it better so this kind of thing never happens again. *** This bug has been marked as a duplicate of bug 404600 ***