Arch Linux

jacko

Member

Registered: 2007-11-23

Posts: 840

audacious 1.4.2 - plugins 1.4.1

I have these installed and up till I changed permissions to let the ~/.config/audacious folder have user privileges instead of root privileges I couldn't get audacious to save any settings, load any presets, or for that matter of fact do anything except load to the default space with the default settings.

My question is, why do I need root privileges to save config files for a program located in my ~/ directory? Seems like the ~/.config folder should have user privileges not root privileges.

Can anyone explain this????

jacko

Member

Registered: 2007-11-23

Posts: 840

Re: audacious 1.4.2 - plugins 1.4.1

on another note, I am forced to use pacman as root, is this why it doesn't install config files to my home directory?

byte

Member

From: Düsseldorf (DE)

Registered: 2006-05-01

Posts: 2,046

Re: audacious 1.4.2 - plugins 1.4.1

You probably started it as root (sudo?) once, no other explanation possible. Arch packages never ever modify stuff in ~.

edit: ever heard of a package manager NOT requiring root privs for installing pkgs? Of course you don't need to be root for operations like, -Qi/o/u/l, -Sl, -Sp, -Ss etc.
Also, a lot of software uses .config to store settings, Xfce comes to mind. So even if you didn't start Audacious as root, there are still more candidates.

Last edited by byte (2007-11-24 15:29:14)

---

1000

jacko

Member

Registered: 2007-11-23

Posts: 840

Re: audacious 1.4.2 - plugins 1.4.1

no I start audacious VIA the icon I dragged and dropped off my main menu to the top menu bar. Now how would that stop audacious from writing files to ~/.config/audacious???

My ~/.config folder has root privileges only, but this makes no sense. Every program I use as my 'username' should be able to write to a config file that it uses for a program that is run as a normal user and not a super user.

Does this not make sense to anyone else???

Last edited by jacko (2007-11-24 15:32:50)

jacko

Member

Registered: 2007-11-23

Posts: 840

Re: audacious 1.4.2 - plugins 1.4.1

I am just trying to understand, I am really new to linux and don't grasp everything all the time.

Just looking for some help, I posted in another thread about my problems and didn't get any replies so I found my own solution.

But it seems weird that I have to create a folder named audacious in a folder named .config in my home directory that only has root privileges just to get a program to save settings on exit.

now I would just like some reasoning. or maybe a better solution.

Last edited by jacko (2007-11-24 15:37:04)

byte

Member

From: Düsseldorf (DE)

Registered: 2006-05-01

Posts: 2,046

Re: audacious 1.4.2 - plugins 1.4.1

> My ~/.config folder has root privileges only, but this makes no sense.

Exactly. That shouldn't be the case, and that's why you run chown -R jacko:users  ~/.config to fix it.

Last edited by byte (2007-11-24 15:51:49)

---

1000

jacko

Member

Registered: 2007-11-23

Posts: 840

Re: audacious 1.4.2 - plugins 1.4.1

well at least that does make some sense, I will change it right now. Thank you!

still odd to wonder why its like that. The only other folder in there was gtk2.0 and that also only has root privileges. Is that ok as is or should I change that as well?

thayer

Fellow

From: Vancouver, BC

Registered: 2007-05-20

Posts: 1,560

Website

Re: audacious 1.4.2 - plugins 1.4.1

Early in the Arch installation phase, you must have launched a GUI application as root which wrote the ~/.config/gtk-2.0 directory.  This in effect has locked down your primary configuration folder (~/.config).  Absolutely no files or folders under /home/jacko/ should be owned by root.

A command like this should set you straight (run as root):

# chown -R jacko:jacko /home/jacko

This will recursively change the ownership of every file within ~/jacko to yourself, ensuring no other root permissions are lingering about...

Last edited by thayer (2007-11-24 18:00:47)

---

thayer williams ~ cinderwick.ca