Manjaro 21.2.5, when using “sudo -i thunar” or “sudo -i mouspad” there are rows and rows of errors in the terminal and the programs will not accept/save any settings changes. Any ideas why or where to start looking? Some rights misconfiguration?
Is sudo -i even the “proper” way to do that? Ever since the disappearing of gksu, it is the only thing that has worked well for me.
I tried pkexec and it works with some apps and not others. Guess I could just use nano. Still, usually sudo -i program has worked fine before. What is the reason it’s not good to do it that way? Sure is easier.
Edit: it also spits out the same errors, like:
thunar: (thunar:1409): thunar-WARNING **: 02:53:28.611: Name 'org.xfce.FileManager' lost on the message dbus.
mousepad: dconf-WARNING **: 03:41:59.081: failed to commit changes to dconf: Error spawning command line “dbus-launch --autolaunch=683002ba193d4cd992097c2a2b84d88e --binary-syntax --close-stderr”: Child process exited with code 1
I can live with using nano, though it is very cumbersome and clunky compared to mousepad.
So if I want to delete a bunch of files and folders in “/usr/share/backgrounds” for example, the only good way to do it is by typing “sudo rm /blah/blah/blah” all day instead of just sudo -i thunar > select bunch-o-stuff > delete?
I know, “Why would you want to delete stuff in the first place?”
Just because I hate hundreds of megabytes of clutter and bloat from completely unused things in general, and leftovers from uninstalled programs (firefox, thunderbird, pidgin, viewnior), etc. and I’m just trying to learn/get better at Linux in general.
You can do that - but not only are you asking for problems as the files removed is part of a package - they will reappear when the package is updated. You will also get weird package manager errors if you decide to remove a package where you have removed files manually beforehand.
Never modify /usr tree by hand
The only way to remove such files is to copy the files you want to keep to ~/.local/share/backgrounds - then uninstall the package providing the files.
Doing it the way you describe will only cause frustration when the files reappear after an update.