[Expired for gconf (Ubuntu) because there has been no activity for 60
days.]
** Changed in: gconf (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/367169
[Expired for dbus (Ubuntu) because there has been no activity for 60
days.]
** Changed in: dbus (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/367169
I just updated my 10.04 LTS 64-bit laptop 30mins ago and now suddenly
am getting these errors from thunderbird, gedit etc. Removing ~/.dbus
and letting it regenerate at no effect. To summarize:
% ssh -X host gedit
generates a stream of GConf errors,
host% gedit
(that is run locally on
@mazerj
Instead of removing ~/.dbus try changing the ownership of that directory
(and sub directories/files) to your self:
$ sudo chown -R username:username ~/.dbus/
When you removed the directory, it might have been regenerated with some as
root for some reason (which might help with
I actually tried that first, with no luck.
/jamie
On 10/28/2010 01:32 PM, Keith Buel wrote:
@mazerj
Instead of removing ~/.dbus try changing the ownership of that directory
(and sub directories/files) to your self:
$ sudo chown -Rusername:username ~/.dbus/
When you removed the
This occurs for me on 10.04.1, several server machines and a couple of Ubuntu
desktops, acting as remote (ssh-into these machines) and local (ssh from these
machines). So far, on all 10.04.1 machines from fresh install, and all updates
from previous versions (some sequentially from 7.04, some
I just ran in to this today on a fresh Ubunutu Server 10.04.1 AMD64 install
fully patched.
Both my ~/.dbus directory and ~/.esd_auth were owned by root:root for some
reason.
I had not seen the thing about .esd_auth reported so I just wanted to
let you know. Maybe that will point to the
I am getting this same issue with a clean install of 10.04.
ssh -c blowfish -CX u...@server thunderbird
results in the following information in a pop-up window ...
Failed to contact configuration server; some possible causes are that you need
to enable TCP/IP networking for ORBit, or you have
I was affected by this bug, and I can confirm that on the remote machine
the ~/.dbus directory was owned by root. By changing the owner to
myself the problem is solved.
For some reason some people got the ~/.dbus ownership unwillingly
changed, can't tell in which package, but this is certainly a
Today, 9.10, same bug, same problem. Can we raise the priority ?
--
GConf Error: Failed to contact configuration server; durring ssh X11 forwarding
https://bugs.launchpad.net/bugs/367169
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is a very frustrating bug. I am using a 9.10 client connecting to
a 9.04 server. Every week or so I will get this error. Both systems
are fully patched.
--
GConf Error: Failed to contact configuration server; durring ssh X11 forwarding
https://bugs.launchpad.net/bugs/367169
You received
One thing to check and did the trick for me:
Remove .dbus directory in the $HOME.
--
GConf Error: Failed to contact configuration server; durring ssh X11 forwarding
https://bugs.launchpad.net/bugs/367169
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug may be coming in a few incarnations but it seems to be a bug
with the DBUS system on Jaunty
The original error reported doesn't go away with the latest updates and
is actually being reported on quite a bit of other GNOME programs when
trying to display back to the Jaunty Host.
I have
A little further investigation revealed the following. This issue
doesn't appear to be taking place when running commands remotely from
Intrepid displaying on Jaunty and from Jaunty displaying on Intrepid but
when running Jaunty-Jaunty bug appears.
Also,
If you try running on a host host1
Not a D-Bus issue
** Changed in: dbus (Ubuntu)
Status: New = Invalid
--
GConf Error: Failed to contact configuration server; durring ssh X11 forwarding
https://bugs.launchpad.net/bugs/367169
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Sorry for reopening this, but just because it may or not be a bug in
GConf, it is still most certainly a bug in Ubuntu. Flag it SSH, DBus,
GConf, or whatever, but X tunnelling in Ubuntu is flat out broken. If
the GConf team decides its not their bug, can it get forwarded to the
appropriate team?
I posted a solution for this issue and probably this gonna solve your
problem too:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/336660
--
GConf Error: Failed to contact configuration server; durring ssh X11 forwarding
https://bugs.launchpad.net/bugs/367169
You received this bug
I also face this problem when i use root to login(i am boring to type sudo
everytime).
But if i use another user to login, and use sudo gedit, everything looks fine.
--
GConf Error: Failed to contact configuration server; durring ssh X11 forwarding
https://bugs.launchpad.net/bugs/367169
You
There are three cause the gconfd not making connection. 1. is a stale
slot, 2. that ORBit-2 does can not communicate over tcp/ip protocal and
3 there are multiple gconfd daemons running.
1. Test that there are no stale slots. The above responces give several
ways to do this. Each of the above
I can confirm same problem in my Janunty box and fixed it in the same
way. One interesting thing is that I have 10 identical machines running
Jaunty. Only the machines I have updated packages, from Internet after
installation by synaptic, shows this problem. But the machines that I
have the
I had the same problem, and fixed it the same way. I'm running
Intrepid.
--
GConf Error: Failed to contact configuration server; durring ssh X11 forwarding
https://bugs.launchpad.net/bugs/367169
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I can confirm that this problem is new to Jaunty. Broke after the dist-
upgrade. File permissions were wet to root, changed them back to me and
dbus functions work over ssh tunnels again.
--
GConf Error: Failed to contact configuration server; durring ssh X11 forwarding
I had the same problem, was fixed according to Keith's instructions on
changing the owner. I agree that this problem shouldn't be happening
with such fundamental system components like dbus and gconf.
--
GConf Error: Failed to contact configuration server; durring ssh X11 forwarding
Whether or not this is a bug with gconf, I would still consider this a
bug. Something is changing/setting the permissions of those files,
which inhibits basic functionality.
I don't think that a basic user should have to know that they need to
change the permissions back to their own in the
I had the same problem and setting the right owner on ~/.dbus solved the
problem for me. The issue is therefore resolved, except that gconf/dbus
perhaps should say aloud what is wrong by themselves.
--
GConf Error: Failed to contact configuration server; durring ssh X11 forwarding
The issue is resolved and wasn't bug in gconf. Therefore invalid.
** Changed in: gconf (Ubuntu)
Status: Incomplete = Invalid
--
GConf Error: Failed to contact configuration server; durring ssh X11 forwarding
https://bugs.launchpad.net/bugs/367169
You received this bug notification
Thanks very much for reporting this all the files were owned by root and
changing them to my user name solved the problem.
--
GConf Error: Failed to contact configuration server; durring ssh X11 forwarding
https://bugs.launchpad.net/bugs/367169
You received this bug notification because you are
I looked into this more and did some research. There was a file in
~/.dbus/session-bus that was owned by root. I changed the ownership
to me and the error went away, and the program popped up. Below is what
I did:
ke...@mediabox:~$ gedit
GConf Error: Failed to contact configuration server;
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Also, please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will greatly aid us in tracking down your problem and resolving
this bug.
**
Yes it is reproducible.
I'm not sure if I have found exactly when it happens, but its basically happens
i'd say 90% of the time. I've restarted the server many times, and one time it
worked and I was able to bring up gedit, and basically every other app without
issue.
I'm not really sure
30 matches
Mail list logo
