You are not logged in.
Pages: 1
trying to start gnome-terminal I get an error saying it can't contact the gconf daemon. I'm guessing this was caused by a recent -Syu I did, but does anyone have any ideas on how to fix?
[home page] -- [code / configs]
"Once you go Arch, you must remain there for life or else Allan will track you down and break you."
-- Bregol
Offline
same here after pacmaned gnome 2.26... only gnome-terminal is affected though
Offline
You will need the dbus session daemon. If it doesn't exist, any dbus-enabled app seems to launch its own daemon nowadays, which doesn't work fine with GConf.
Offline
I have dbus enabled in my rc.conf and it is running:
> ps ax | grep dbus
3948 ? Ss 0:00 /usr/bin/dbus-daemon --system
4254 ? S 0:00 dbus-launch --autolaunch 0fe677b103fb204acd79753349b6f43a --binary-syntax --close-stderr
4255 ? Ss 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
4347 pts/0 S+ 0:00 grep dbus
However, gnome-terminal still crashes.
> gnome-terminal
Failed to contact the GConf daemon; exiting.
Cheers, George
Offline
how is this "dbus session" daemon different from the normal dbus daemon I've been using up 'till now?
[home page] -- [code / configs]
"Once you go Arch, you must remain there for life or else Allan will track you down and break you."
-- Bregol
Offline
Offline
same problem
Sorry for my bad english :-)
Offline
Same problem.
I started another thread earlier; the results were not that helpful
Offline
OK, that explains it. It would also, I presume, explain why nautilus-open-terminal fails to appear in the context menu.
Offline
Yea, same problem here... I tried to install and run gnome-settings-daemon before launching gnome-terminal as suggested on launchpad but to no avail.
The bug that most are complaining about is launching gnome-terminal as root, but I have the same error regardless of whether I try as root or as user. Todays updates help nautilus-open-terminal now it shows up in the menu, but obviously gnome-terminal won't start so its useless.
Offline
The bug that most are complaining about is launching gnome-terminal as root, but I have the same error regardless of whether I try as root or as user. Todays updates help nautilus-open-terminal now it shows up in the menu, but obviously gnome-terminal won't start so its useless.
What I did, was to uninstall gnome-terminal, and then (as root) create the file /usr/bin/gnome-terminal
in which I wrote:
urxvt
(you can put here your terminal of choice)
and then made it executable: chmod +x /usr/bin/gnome-terminal
hope this helps.
Offline
blazercist wrote:The bug that most are complaining about is launching gnome-terminal as root, but I have the same error regardless of whether I try as root or as user. Todays updates help nautilus-open-terminal now it shows up in the menu, but obviously gnome-terminal won't start so its useless.
What I did, was to uninstall gnome-terminal, and then (as root) create the file /usr/bin/gnome-terminal
in which I wrote:
urxvt
(you can put here your terminal of choice)
and then made it executable: chmod +x /usr/bin/gnome-terminal
hope this helps.
<irony>Oh I just did that, but I LOST may features of gnome-terminal, thought they did a downgrade instead an upgrade, now *this* gnome-terminal SUCKS.</irony>
And replies like this .. sucks too..
Offline
and our devs do not know what we can do?
Cancel me not -- for what then shall remain?
Abscissas, some mantissas, modules, modes, A root or two, a torus and a node:
The inverse of my verse, a null domain.
-- Stanislaw Lem, The Cyberiad
Offline
I've got it!
At least, I think that this could be of interest to anybody who is not using the normal gnome-session. I checked around dbus-launch and found out that the environment variables weren't set. I checked the man (woohoo to rtfm) page for dbus-launch, saw that little gem that makes use of the script-outputting feature of dbus-launch to setup the variables properly.
Anyway, for those that want it fast, add this to your startup script. Mine was .xsession, yours could be fluxboxe's or anything in fact.
## test for an existing bus daemon, just to be safe
if test -z "$DBUS_SESSION_BUS_ADDRESS" ; then
## if not found, launch a new one
eval `dbus-launch --sh-syntax --exit-with-session`
fi
This was taken directly from the man page and it is currently working for me, working great!
I don't know if it should be considered a bug in a package, if so which one, but I am fairly certain that a program that needs a service should be able to set it up for itself, unless there is a reason for not doing this.
I hope this helps!
Offline
I've got it!
terminal 2.26?? I've try:
dbus-launch --sh-syntax --exit-with-session
[~] ps ax | grep dbus
1645 ? Ss 0:00 /usr/bin/dbus-daemon --system
1882 ? S 0:00 dbus-launch --autolaunch e96bedf66241d000b3bb1d0d495bc863 --binary-syntax --close-stderr
1883 ? Ss 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
2580 pts/0 S+ 0:00 grep dbus
[~]
but in my case gnome-terminal 2.26 still doesn't work
Sorry for my bad english :-)
Offline
samueldr wrote:I've got it!
terminal 2.26?? I've try:
dbus-launch --sh-syntax --exit-with-session
[~] ps ax | grep dbus 1645 ? Ss 0:00 /usr/bin/dbus-daemon --system 1882 ? S 0:00 dbus-launch --autolaunch e96bedf66241d000b3bb1d0d495bc863 --binary-syntax --close-stderr 1883 ? Ss 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session 2580 pts/0 S+ 0:00 grep dbus [~]
but in my case gnome-terminal 2.26 still doesn't work
I think you made a slight mistake there. The thing is that the environment variables are not set when you "simply launch" dbus. The easiest way to setup the environment properly is to either use the entire block I gave in my last post in your startup scripts (could be ~/.xsession) or issue this command:
eval `dbus-launch --sh-syntax --exit-with-session`
The trick here is to eval the output of dbus-launch. we made it output a script, then we eval it in the current shell environment, thus the variable is set and now gnome-terminal should be able to start.
Hope it helped!
Offline
@samueldr: it works !!!!!!!
I've paste that code in .xinitrc:
.....
## test for an existing bus daemon, just to be safe
if test -z "$DBUS_SESSION_BUS_ADDRESS" ; then
## if not found, launch a new one
eval `dbus-launch --sh-syntax --exit-with-session`
fi
exec openbox-session
.....
thx!!
Sorry for my bad english :-)
Offline
This trick is not working for me (slim, wmii):
$ cat .xinitrc
# test for an existing bus daemon, just to be safe
if test -z "$DBUS_SESSION_BUS_ADDRESS" ; then
## if not found, launch a new one
eval `dbus-launch --sh-syntax --exit-with-session`
fi
exec ck-launch-session wmii
(I have also tried just "exec wmii")
After the restart:
$ export | grep DBUS
declare -x DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-Fbn1FgC9hq,guid=f7dada9dc1dfcedab3e0ff8949ec57d8"
$ ps aux | grep dbus
dbus 5084 0.0 0.0 2140 892 ? Ss 15:08 0:00 /usr/bin/dbus-daemon --system
xxx 5428 0.0 0.0 3160 660 ? S 15:09 0:00 dbus-launch --sh-syntax --exit-with-session
xxx 5429 0.0 0.0 2140 864 ? Ss 15:09 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
xxx 23390 0.0 0.0 5116 832 pts/0 S+ 16:01 0:00 grep dbus
But:
$ gnome-terminal
Failed to contact the GConf daemon; exiting.
Can anybody help me?
Offline
Unfortunately, none of the fixes work, I tried the .xinitrc thing suggested and I tried with exec fusion-icon and exxec ck-launch-session exec fusion-icon.
Downgrading to gnome-terminal 2.24.3-1 worked like a charm.
Thanks for the suggestions and keep em coming, hopefully we'll figure this out.
Last edited by blazercist (2009-04-20 22:59:47)
Offline
I had this same problem. However, none of the solutions provided in this thread worked.
After a bit of trial and error, I found that adding gnome-settings-daemon to my .xinitrc file did the trick. My .xinitrc is as follows:
#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)
# test for an existing bus daemon, just to be safe
if test -z "$DBUS_SESSION_BUS_ADDRESS" ; then
## if not found, launch a new one
eval `dbus-launch --sh-syntax --exit-with-session`
fi
gnome-settings-daemon &
xsetroot -cursor_name left_ptr
exec xmonad
# ...or the Window Manager of your choice
Sorry for the thread bump, but this is one of the few threads that comes up in a Google search. I figured that a working solution should be provided.
Last edited by Hardrive (2009-05-05 00:33:41)
Offline
No problem, actually, I have gnome-settings-daemon in my .xinitrc, so maybe that for those for whom my fix haven't worked, they may need to start it too. I never thought that it would be needed.
Offline
Pages: 1