2.14 session bus

Paul · 2006-03-19 22:48:33

** (epiphany:3105): WARNING **: Unable to connect to session bus: Unable to determine the address of the message bus

dbus starts up without errors...

WillySilly · 2006-03-20 01:43:52

are you starting up gnome with gdm or startx?

Gullible Jones · 2006-03-20 02:02:04

Replace whatever's in your .xinitrc with this:

exec dbus-launch --exit-with-session /opt/gnome/bin/gnome-session

(Note that it has to be --exit-with-session, not --end-with-session - that's the mistake I made.)

_Gandalf_ · 2006-03-20 08:28:35

Maybe that should be updated in /etc/skel/.xinitrc guys ??
that's my customized one

#!/bin/sh

#
# ~/.xinitrc
#
#Executed by startx (run your window manager from here)
#

#
# Commands to run before the Window Manager
#
# devilspie &

#
# Windows Manager
#
exec dbus-launch --exit-with-session /opt/gnome/bin/gnome-session
# exec fvwm
# exec fvwm-crystal
# exec startxfce4
# exec wmaker
# exec startkde
# exec icewm
# exec blackbox
# exec fluxbox

baze · 2006-03-20 10:51:44

do you have dbus in the daemons array in the rc.conf aswell?
i use hal+dbus for automounting and would like to know if the session dbus is enough for this so i don't need the system one too. or do i need both (system dbus for hal?)?

i was wondering about this for the last days

hehejo_ · 2006-03-20 15:44:47

Hum, I have executed this line via aterm in an Xnest.

ecex dbus-launch --exit-with-session openbox

But dbus-monitor still claims, that it can't connect to the message bus.

What's wrong with this.
prortmap, fam and hal are running.

Paul · 2006-03-20 17:22:25

Hi all, thanks for the replies.

exec dbus-launch --exit-with-session openbox

This works with epiphany, totem, etc.
Is this a work around or the standard way of launching gnome?

Nautilus is very unstable for me, the desktop won't load if the network is connected (blank grey panels, no icons on desktop). Even now as I type this, the desktop has crashed. This is on a fresh install, as well as a full update with Syu.[/code]

henrikbrink · 2006-03-20 18:16:42

Hello

I have the exact same problem with Epiphany, but the fix you described doesn't work.

Any idea how that is possible?

Thanks in advance

henrikbrink · 2006-03-20 18:50:00

I got the idea of trying to run epiphany via dbus-launch also, and it suddenly works. So running:

dbus-launch epiphany

works, but I really dont want to do this every time I have to run a dbus-enabled application.

Any help?

linfan · 2006-03-21 07:44:08

For me it works.

I have the line in my .xinitrc

exec dbus-launch --exit-with-session gnome-session

But the funny thing is I do not have dbus neither hal running and it is not in rc.conf either, as I do not have the slightest notion of what it is. If somebody can explain to me in a very simple way, like "dbus is a program that makes it possible for bla bla and bla bla to work" or "dbus enhances gnome in..." , I might consider using it. Hal is also a daemon I cannot understand. All docs make me confused. I just need to know what these daemons are good for not what they are.

Thankful for further speculations and eventually answers. I guess these deamons are just a needless nuisance and highly experimental. I hope, though, I am wrong.

Regards,

linfan

syntax · 2006-03-21 07:57:00

oh, hal is what is necessary for hotplugging usb disks (automount)?

JGC · 2006-03-21 08:18:26

dbus will replace the old and dirty bonobo stuff GNOME used for a long while for process communication. More and more apps start to switch to DBUS. DBUS can be used in two ways: a system bus, which is used by programs like hal, powermanage or avahi, or the message bus, the thing you start as user so programs have some way to exchange messages. The system bus doesn't have anything to do with the message bus. In fact, the system bus is a message bus used for system processes.

baze · 2006-03-21 09:38:48

for things like automounting you need the system bus and for tools like bmp and gajim you need the message bus. this does mean you need both, the system bus (rc.conf) and the message bus (exec dbus-launch ....), right?
they won't conflict in any way?

henrikbrink · 2006-03-21 10:42:14

Hello again

I just found the solution. It was just some stupidity involving Slim and my brain. Bottom line: The fix works fine.

Thank you

Arch Linux

#1 2006-03-19 22:48:33

2.14 session bus

#2 2006-03-20 01:43:52

Re: 2.14 session bus

#3 2006-03-20 02:02:04

Re: 2.14 session bus

#4 2006-03-20 08:28:35

Re: 2.14 session bus

#5 2006-03-20 10:51:44

Re: 2.14 session bus

#6 2006-03-20 15:44:47

Re: 2.14 session bus

#7 2006-03-20 17:22:25

Re: 2.14 session bus

#8 2006-03-20 18:16:42

Re: 2.14 session bus

#9 2006-03-20 18:50:00

Re: 2.14 session bus

#10 2006-03-21 07:44:08

Re: 2.14 session bus

#11 2006-03-21 07:57:00

Re: 2.14 session bus

#12 2006-03-21 08:18:26

Re: 2.14 session bus

#13 2006-03-21 09:38:48

Re: 2.14 session bus

#14 2006-03-21 10:42:14

Re: 2.14 session bus

Board footer