can't use double click in kde

[allaf]

I cant' use the 'double click' setting in kde config.

Didn't think such bugs were still possible, I think I'm giving up on kde, seriously.

The video speaks for itself I believe :

[Teunis]

I'm not able to open the video on this site nor in Youtube so I might be missing some info.

Yet, I can set the mouse in System Settings to Double Click and get the advertised results.
(and then quickly return to my favourite Single Click )
In other words, you have a localised problem...

[claydoh]

Have you anywhere at any time run System Settings or other tool with sudo to edit or change any local user setting? (not system level settings) The inability of user config changes to stick is a classic sign of incorrect permissions on the file(s). Check permissions on your ~/.config/kdeglobals file, to see if it owned by root instead of your user, and that it is writeable. This is the file that stores the setting for the single/double click option, among other things.

[LinkBot]

The first thing...

https://forum.kde.org/viewtopic.php?f=14&t=38828

Examine if the problem is local

To determinate if a problem is caused by your configuration or is due to a bug/fault in your system (such as an incomplete upgrade), you can try to reproduce it with a clean system. The easiest way is to create a new user:

1. Create a new user.
2. Log in using the new user. Do you experience the same problem here as well?

[allaf]

Yes the problem is cause by the config of my user, it works with a new user.

Turns out I have no permission on the file... Don't know how it happened.

-rw------- 1 root root 2477 nov.   1 21:15 /home/myuser/.config/kdeglobals

Thanks for your help.

[Snowhog]

Open a console and ensure you are in your users home directory. Then type:

sudo chown -R myuser:myuser *

where myuser is your login username.

This will change the ownership on all directories/files within your home directory to you, which is what they all are supposed to be. Then logout/reboot/log in. Things should now work as they are supposed to,

[kubicle]

sudo chown -R myuser:myuser *

Using globbing (*) is often ambiguous, and this one is a potential dotglob trap.

If the "dotglob" shell option is not enabled in bash (and it isn't by default) "*" does not match hidden dotfiles/directories (files and directories that begin with "."), which means this command will skip all these files and directories in the users $HOME (unless the user has set the "dotglob" shell option to "on", of course, or uses a shell with different [default] behavior).

It's nearly always better to set the target explicitly (this also prevents any accidents when not in the correct target directory), for example:

sudo chown -R myuser:myuser $HOME

[allaf]

Actually I have the exact same problem with file assiciation now.
It works with a new user but not mine, but I don't know wich file to change.

[Teunis]

It'll be a file in your /home so that's why Snowhog gave the command:

sudo chown -R myuser:myuser *

chow will Change User, -R means Recursive, together with the wildcard * i.e. all files and directories in the tree.

kubicle commented this wildcard that he calls 'globbing' can be ambiguous and suggests using:

sudo chown -R myuser:myuser $HOME

I believe $HOME should be ~/ so:

sudo chown -R myuser:myuser ~/

[allaf]

Yeah, but I already did that. Didn't work

[kubicle]

I believe $HOME should be ~/ so:

Either is fine, you can literally use "$HOME" as well

[kubicle]

Yeah, but I already did that. Didn't work

Then the problem is likely not ownership related, but could be caused by something else.
Just to make sure, you can run:

find ~ ! -writable -exec ls -l '{}' \+

This command will list all files/folders in your $HOME that are not writable for your user (which may indicate a problem), you can post the output here if you can't decipher it yourself.

[Teunis]

Thanks for the lesson kubicle, I should have tried it before spouting off

[allaf]

Then the problem is likely not ownership related, but could be caused by something else.
Just to make sure, you can run:

find ~ ! -writable -exec ls -l '{}' \+

This command will list all files/folders in your $HOME that are not writable for your user (which may indicate a problem), you can post the output here if you can't decipher it yourself.

No, nothing comes up expect unrelated files.

Does anyone know which file I have to edit to change my file association settings manually ?

[kubicle]

Does anyone know which file I have to edit to change my file association settings manually ?

I think user settings for file associations are stored in ~/.local/share/applications/mimeapps.list (or ~/.config/mimeapps.list, see EDIT), but rather than editing that file I'd probably try to use the command xdg-mime (see 'man xdg-mime' for details) to set a file association to see if that works (and if it doesn't, there might be a relevant error message that might point to the problem).

EDIT: Actually, it seems mimeapps.list could also be in ~/.config/ and ~/.local/share/ location is deprecated (which could be part of the problem) [https://wiki.archlinux.org/index.php...t_applications]

Do you have mimeapps.list in either location and do they change when you edit file associations in kde?