So today after a big update, I noticed my pulseaudio centralized output device had vanished. This sucks because pulseaudio's gui tools kinda suck, so it's easy to have one static output device and have all the audio go there.
So I poked around trying to figure out how to add it again. Thankfully pulseaudio's tools all start with pa-. paprefs was what I was looking for.
Yay:
Code:
Error setting value: Configuration server couldn't be contacted: D-BUS error: Unable to store a value at key '/system/pulseaudio/modules/combine/locked', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Yeah, that error message was thoroughly useless.
I tried running gconfd-2 manually (it's in /usr/lib for some reason?), but yeah, it doesn't respond to any --help or -help or -h or anything like that. Ctrl+c doesn't kill it. After digging through
the source code (no github because this is circa January 2013), I found the environment variable GCONF_DEBUG_OUTPUT which sounded interesting. Set it to true (because fuck it, why not?) and tried again.
Aha, turns out ~/.config/gconf/...'s ownership was changed to root:root for some fucking reason. chown'd it, killed gconfd-2 again (again, no ctrl+c doesn't work) and tried again.
Fixed.