On 11/5/06, Jim McCloskey <[EMAIL PROTECTED]> wrote:
Kelly Clowers" <[EMAIL PROTECTED]> wrote:
|> I have something like this in my ~/.bash_profile
|> (because I start X manually, and I want dbus on before X starts ):
|>
|> if test -z "$DBUS_SESSION_BUS_ADDRESS" ; then
|> ## if not found, la
Kelly Clowers" <[EMAIL PROTECTED]> wrote:
|> I have something like this in my ~/.bash_profile
|> (because I start X manually, and I want dbus on before X starts ):
|>
|> if test -z "$DBUS_SESSION_BUS_ADDRESS" ; then
|> ## if not found, launch a new one
|> eval $(dbus-launch --sh-syntax)
Kelly Clowers" <[EMAIL PROTECTED]> wrote:
|> I have something like this in my ~/.bash_profile
|> (because I start X manually, and I want dbus on before X starts ):
|>
|> if test -z "$DBUS_SESSION_BUS_ADDRESS" ; then
|> ## if not found, launch a new one
|> eval $(dbus-launch --sh-syntax)
On 11/4/06, Jim McCloskey <[EMAIL PROTECTED]> wrote:
Following a recent upgrade (sorry, I can't be more precise), I'm
getting the dbus error:
Unable to determine the address of the message bus
from a number of applications at start-up, including at least:
f-spot (which fails to start as a
Following a recent upgrade (sorry, I can't be more precise), I'm
getting the dbus error:
Unable to determine the address of the message bus
from a number of applications at start-up, including at least:
f-spot (which fails to start as a consequence)
rhythmbox
epiphany-browser
I'm not su
5 matches
Mail list logo