Missing option for single click

Hi,

I cannot set single click for for opening files or folders in Dolphin.

I’m using Linux Mint 22.2 with Cinnamon desktop.

When I open KDE’s systemsettings it’s barely populated and there’s no option to select single or double click.

The same problem happens in Kate in the filesystem browser plugin.

Aby ideas how about how to enable single click in Dolphin without installing KDE plasma desktop?

Solved. I had to install “qt5ct” which allowed me to change some global settings for Qt applications including the option to single click on items.

2 Likes

I would suggest that plenty of bugs are to be expected - almost a feature of installing a Plasma desktop on a Cinnamon distribution.

Your best action is likely to backup your data and do a nice clean install of a proper KDE Plasma distribution, rather than continue fighting with Frankenstein’s monster!

Thanks for the advice but the problem has been resolved so, no, there’s no continuous fighting here :grin:
I have been using KDE and later Plasma desktop since 2003 (OpenSuse Leap) until recently and I do like Plasma 5 and most KDE applications but I don’t like where Plasma 6 is heading.
I particularly don’t like Nate Graham’s stance about X11 (e.g. he wrote that he won’t fix bugs related to X11 anymore).

Oh, I think that @ngraham responded in a far more nuanced fashion than that - it seems extremism and over-reactions are pretty much the norm.

1 Like

Maybe, but after having read this, I’m not optimistic…

pointieststick.comSLASH2025/06/21/about-plasmas-x11-session

(replace SLASH with /, somehow I’m not allowed to write a link…)

or search with the following string:

Adventures in Linux and KDE About Plasma’s X11 session

1 Like

A few years isn’t much at my age… And I do have a rose colored spectacles for all the amazing features of x11…

So many problems that I have could be very easily solved if I was using it.

But wayland, despite being limited, gives me just about everything I need except for mouse gestures…

So there is space for optimism, in many ways Wayland already sucks less than x11 did. Give it a few more years…

I have to use KiCad at work. Wayland doesn’t work well with KiCad.

These problems exist because Wayland’s design omits basic functionality that desktop applications for X11, Windows and macOS have relied on for decades-things like being able to position windows or warp the mouse cursor. This functionality was omitted by design, not oversight.

The fragmentation doesn’t help either. GNOME interprets protocols one way, KDE another way, and smaller compositors yet another way. As application developers, we can’t depend on a consistent implementation of various Wayland protocols and experimental extensions. Linux is already a small section of the KiCad userbase. Further fragmentation by window manager creates an unsustainable support burden. Most frustrating is that we can’t fix these problems ourselves. The issues live in Wayland protocols, window managers, and compositors. These are not things that we, as application developers, can code around or patch.

We are not the only application facing these challenges and we hope that the Wayland ecosystem will mature and develop a more balanced, consistent approach that allows applications to function effectively. But we are not there yet.

www.kicad.orgSLASHblog/2025/06/KiCad-and-Wayland-Support/

replace SLASH with / or search with the string:

kicad blog KiCad and Wayland Support