[Fluxbox-users] [fluxbox-users] fluxbox with dbus session freezes.

[Javier Vasquez]

Hi,

I don't use d-bus much, since I don't use desktop environments and I
tend to use light and configured things like autofs, fluxbox itself
and the like.

On my x86-64 machine running under arch-linux, I tried starting dbus
sessions prior to executing fluxbox as follows:

dbuslaunch="`which dbus-launch 2>/dev/null`"
if [ -n "$dbuslaunch" ] && [ -x "$dbuslaunch" ] && [ -z
"$DBUS_SESSION_BUS_ADDRESS" ]; then
eval `$dbuslaunch --sh-syntax --exit-with-session`
fi
exec startfluxbox

And it starts OK... Problem is if I leave X to do something in the
console, and come back to X, fluxbox is already frozen. Also some
times if I don't do that, eventyually fluxbox freezes, but I can't
associate any event triggering this eventual freeze, perhaps just more
than a minute or so of time. I didn't expect any of this to happen...

I opted for not starting the dbus session, though my expectation is to
enable it back when possible so things like pcmanfm work OK...

Has anyone experienced the same?

Thanks,

[Javier Vasquez]

Post by Javier Vasquez
Hi,
I don't use d-bus much, since I don't use desktop environments and I
tend to use light and configured things like autofs, fluxbox itself
and the like.
On my x86-64 machine running under arch-linux, I tried starting dbus
dbuslaunch="`which dbus-launch 2>/dev/null`"
if [ -n "$dbuslaunch" ] && [ -x "$dbuslaunch" ] && [ -z
"$DBUS_SESSION_BUS_ADDRESS" ]; then
 eval `$dbuslaunch --sh-syntax --exit-with-session`
fi
exec startfluxbox
And it starts OK...  Problem is if I leave X to do something in the
console, and come back to X, fluxbox is already frozen.  Also some
times if I don't do that, eventyually fluxbox freezes, but I can't
associate any event triggering this eventual freeze, perhaps just more
than a minute or so of time.  I didn't expect any of this to happen...
I opted for not starting the dbus session, though my expectation is to
enable it back when possible so things like pcmanfm work OK...
Has anyone experienced the same?

Narrower:

Problem comes when executing commands in the same TTY where X was
called through startx...