9

Whenever I open any software through Terminal I get following errors and eventually the software opens

dconf-WARNING **: failed to commit changes to dconf: The connection is closed

(gedit:3609): dconf-WARNING **: failed to commit changes to dconf: The connection is closed

(gedit:3609): dconf-WARNING **: failed to commit changes to dconf: The connection is closed
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)

What can be the possible issue?

6

I had the same problem, in my case I was running "sudo gedit" from a user account; therefore when it tried to save dconf changes it realized that the user was not root, and thus it raised those errors. I solved it by running gedit as a "root":

sudo -i

gedit &

where sudo -i will login into a user acount.

  • 1
    thx. that hint solved my problem. (so i had to log in via su - myotheruser instead of su myotheruser.) – comonad May 3 '15 at 10:45
4

This has got on my nerves for a long time. I finally solved it using gksudo -l <command>, which runs the command in a login shell - similarly to XAVI's answer but without the need to type in the command after sudo.

2

You may want to check if the following folders are owned by root:

~/.cache/dconf
~/.dbus

If they are, try deleting them. According to other sources I found, they should be owned by yourself, but if you have run graphical programs with sudo they might have been created by root instead. Deleting them is apparently safe, as they are automatically recreated as necessary, but maybe back them up first.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.