Inthis case it changes the background colour of gnome-terminal - the change occurs immediately.
However, when I run the commands from a script they don't work.
The overall script runs as sudo, i.e. sudo ./script.sh then I use the sudo -u option to de-elevate back to the regular user. In this case ubuntu as I'm using a Ubuntu 14.04 live CD.
The issue appears to come from the somewhat sanitized environment the sudo command runs in.
Even though the commands were being executed as the ubuntu user, the environment didn't contain the full complement of env variables usually present when using an interactive terminal / shell.
gconftool-2 seems to need access to the DBUS_SESSION_BUS_ADDRESS variable. In this case I was able to pass it a value I copied from another terminal I was running. But if the script ran on another machine, it might need to fetch it dynamically, in which case something like the script below would be necessary.
I am using Ubuntu 14.04 and I want to set the background color of my gnome-terminal using the command line.
From what I can tell gconftool-2 is the way to do this but I cant work out what the command is to do this.
I recently swapped Linux distributions from Elementary OS Luna (ubuntu 12.04 variant) to Ubuntu 12.10, which had Firestorm installed on it. Firestorm ran fine, despite having a universal graphic driver installed (or at least it said 'graphics card - NA'). On Ubuntu 12.10 it now reports I have a graphic card, however I suspect that has nothing to do with the current problem.
I have installed all the ia32 multiarch files, and tried various commands that resolved similar problems, however this error still comes up whenever I try to run it. I am using on a 64 bit version, with support for the i386 architecture.
The terminal responded saying they were on their latest versions, and were set to manual installation. I would prefer to be able to use Firestorm viewer before resorting to a 64 bit OS, unusual why it plays up on 12.10 and not on 12.04. In theory there should be some solution, unless there is something wrong or depricated on the Second Life release, possibly trying to use outdated library functions. It is all I can think of since I have installed nearly every 32bit package relevant.
You are running the Second Life Viewer on a x86_64 platform. The most common problems when launching the Viewer (particularly 'bin/do-not-directly-run-secondlife-bin: not found' and 'error while loading shared libraries') may be solved by installing your Linux distribution's 32-bit compatibility packages.
3a8082e126