File browsers in various applications freeze for no reason

Hi. I migrated from windows 10 half a year ago and it’s all been great, however recently I encountered a problem that prevents me from using some programs - file browser freezes in them, whether I try to load or save a file. So far I saw this problem only in LMMS and Krita. Everything works fine if I run programs through sudo though, and I have absolutely no idea what could cause this.

I use KDE Plasma and I tried to boot into X11 and Wayland but result is the same in both. If that matters I also recently tried to install second DE (Pantheon) which didn’t work and I removed it, including its remaining packages

Probably “permission” issues if you aren’t having any problems when you use “sudo”. Unlike windows, Linux is an operating system that gives utmost importance to security and doesn’t allow you or anybody (even if you are the one that installed it) to easily access/modify certain folders and files (most of them actually) in your computer.

In any case, if you don’t really have any problem runing apps as superuser, just go ahead and do that. If they are “safe” apps, it will be just fine.

You should never have to run your user applications with sudo. You will create a whole lot of issues for your system.

Your problem may be caused by you having run programs as root before and you have some permission issues in your home directory.

In short, running user applications as root is a bad practice.

3 Likes

Is there a way to fix consequences of running gui apps through root? I looked through some files in ~/.local/share/ and they seem to still belong to my user account

Check with this command: find $HOME ! -user $USER
It should not give any output.

No output

1 Like

Or maybe some files should be writable by the user and they are not.
Try find $HOME -perm 400 or find $HOME -perm 444

A small update, I forced Krita to use gnome file browser through environment variables:
XDG_CURRENT_DESKTOP=GNOME QT_QPA_PLATFORMTHEME=gtk3
and it works without freezing, but that’s more of a temporal solution. Maybe something is wrong with KDE’s file browser