dbus, hal over xdmcp?

Joe Marcus Clarke marcus at marcuscom.com
Tue Jun 16 20:21:30 UTC 2009


On Tue, 2009-06-16 at 10:57 +0100, Anton Shterenlikht wrote:
> On Sat, May 02, 2009 at 05:56:53PM -0400, Joe Marcus Clarke wrote:
> > On Thu, 2009-04-30 at 15:27 +0100, Anton Shterenlikht wrote:
> > > On Thu, Apr 30, 2009 at 09:08:39AM -0500, Robert Noland wrote:
> > > > On Thu, 2009-04-30 at 03:34 -0400, Joe Marcus Clarke wrote:
> > > > > On Tue, 2009-04-28 at 14:30 +0100, Anton Shterenlikht wrote:
> > > > > > On Fri, Apr 24, 2009 at 01:38:58PM -0400, Joe Marcus Clarke wrote:
> > > > > > > On Fri, 2009-04-24 at 12:27 +0100, Anton Shterenlikht wrote:
> > > > > > > > I've read the dbus and hald man pages but I'm still confused.
> > > > > > > > 
> > > > > > > > In a configuration where xserver connects to clients via XDMCP
> > > > > > > > where do I need to run dbus and hald, or more specifically, on what
> > > > > > > > computer do I need to have in /etc/rc.conf these two lines: 
> > > > > > > > 
> > > > > > > > dbus_enable="YES"
> > > > > > > > hald_enable="YES"
> > > > > > > > 
> > > > > > > > 
> > > > > > > > a. only on the machine which runs xserver?
> > > > > > > > b. only on the machine which runs the clients?
> > > > > > > > c. on both the xserver and clients machines?
> > > > > > > > 
> > > > 
> > > > As far as keyboard and mouse are concerned these are client side
> > > > devices.  The server itself can be run headless, though it has been a
> > > > very long time since I've done anything like that...  You might need hal
> > > > on the server side for things like auto-mounting server side cd's or
> > > > whatever, but not for kbd/mouse.
> > > 
> > > I understand this refers to hal, isn't it?
> > > 
> > > But dbus is about interprocess communication, and the processes are
> > > run on a remote box. So should I run dbus daemon on the remote box
> > > as well, or instead of, the xserver box?
> > 
> > You need to run on both.  The process address space is still on the
> > XDMCP server, so the system daemon must be running there.  The clients
> > have mice and keyboards so they need dbus and hald.  You will also need
> > to start your dbus-enabled processes with dbus-launch, or start your
> > local X session with dbus-launch so that a session bus is running.  This
> > session bus will also be running on the XDMCP server.
> 
> Both hal and dbus daemons are running on both the X server and XDMCP server.
> And I launch the session with:
> 
> %head $HOME/.xsession
> dbus-launch --exit-with-session mwm
> 
> Still on the XDMCP server I just see:
> 
> # ps ax | grep dbus
>   594  ??  Is     0:00.02 /usr/local/bin/dbus-daemon --system
> 98706  ??  S      0:00.04 dbus-launch --exit-with-session mwm
> 98709  ??  S      0:00.00 dbus-launch --exit-with-session mwm
> 98710  ??  Ss     0:00.00 /usr/local/bin/dbus-daemon --fork --print-pid 7 --pri
> 98712  p0  R+     0:00.00 grep dbus
> #
> 
> and on the X server I just see black screen. I can move the mouse, but
> nothing happens with any clicks.
> 
> If I start the session with no dbus-launch, I can use mwm fine, but no
> dbus.
> 
> What else can I check?

You could try leaving out --exit-with-session.  Of course, there may be
a problem with your dbus installation.  This should just work.

Joe

-- 
PGP Key : http://www.marcuscom.com/pgp.asc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-gnome/attachments/20090616/d5c48996/attachment.pgp


More information about the freebsd-gnome mailing list