Thanks for both messages. No, apparently no other commands were finding the bus either, rb was just the only one I noticed because the gnome-power-management applet was working and I know that throws and error when the dbus session isn't set up right. However, because I was using dbus-launch gnome-session and the applet is launched by the session that's why it worked. But when I ran rb from a terminal to see the output, it wasn't technically launched by the session. Is that right?
Either way, I put the if statement that Jonathan sent out into my startup scripts and all dbus thingies work wonderfully. thanks for the help. John On 6/19/06, James Doc Livingston <[EMAIL PROTECTED]> wrote: > On Mon, 2006-06-19 at 15:33 -0400, John Russell wrote: > > (rhythmbox:31895): Rhythmbox-WARNING **: couldn't connect to session > > bus: Unable to determine the address of the message bus > > > > I get this message all the time and now that 0.9.5 has rb-client which > > uses dbus to control rb, I really need to figure it out. > > That's the message when "dbus_g_bus_get (DBUS_BUS_SESSION, &error);" > returns NULL, and the second half of the message comes directly from > DBus. > > > > So I have both the system and session buses running. So why is it > > that rb still can't find the message bus? > > Do any other DBus-using applications report that? (e.g. dbus-viewer). If > they won't, and Rhythmbox doesn't, then something very odd is going on. > > > Cheers, > > James "Doc" Livingston > -- > Actually, we have scientifically determined that Heisenberg did indeed > sleep exactly here. However, we have no idea whatsoever just how fast > asleep he was. -- Dave Aronson in asr. > > _______________________________________________ > rhythmbox-devel mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/rhythmbox-devel > _______________________________________________ rhythmbox-devel mailing list [email protected] http://mail.gnome.org/mailman/listinfo/rhythmbox-devel
