You are not logged in.
I used to use Gnome and recently decided to give Openbox a go, in openbox, I found out that apps like thunar, and gtk apps open very slowly, so naturally, I ran it in terminal, then I discovered the following error messages, and I have verified that they are indeed causing the slow startup of the programs, but I currently do not have a fix for this, I have tried to listen in another location, or adding my user account into the DBUS group.
Thunar: Failed to connect to the D-BUS session bus: Failed to connect to socket /tmp/dbus-oGFFR1H7dB: Connection refused
** (evince:12781): WARNING **: Service registration failed.
** (evince:12781): WARNING **: Failed to connect to socket /tmp/dbus-yca398u02W: Connection refused
Last edited by blu3ness (2008-01-19 09:16:17)
Archlinux on Compaq Presario v5000 laptop
Offline
Same here.
I switched from xfce to openbox and thunar or terminal start really slow.
My error messages are similar:
Thunar: Failed to connect to the D-BUS session bus: Failed to connect to socket /tmp/dbus-MYHPYgGSFA: Connection refused
Terminal: Fehler beim Registrieren des Terminal Services: Failed to connect to socket /tmp/dbus-ciMvqHkFq0: Connection refused
Last edited by Barghest (2008-01-20 19:04:48)
Offline
are both the dbus daemon and the session bus running ?
Last edited by pressh (2008-01-20 19:38:14)
Offline
Is this linked to the permissions the user has?
su
gpasswd -a username optical
gpasswd -a username storage
That might fix it.
Last edited by Jamie (2008-01-20 20:04:22)
flack 2.0.6: menu-driven BASH script to easily tag FLAC files (AUR)
knock-once 1.2: BASH script to easily create/send one-time sequences for knockd (forum/AUR)
Offline
Hi!
The permission are set correctly; I'm member of optical and storage.
Here are the daemons:
DAEMONS=(syslog-ng network netfs crond cups hal fam alsa slim mpd)
What do i have to type in the rc.conf for the session bus daemon?
Offline
do you use openbox-session?
in autostart.sh you may need this:
# D-bus
if which dbus-launch >/dev/null && test -z "$DBUS_SESSION_BUS_ADDRESS"; then
eval `dbus-launch --sh-syntax --exit-with-session`
fi
vlad
Offline
I use slim and an openbox entry in the ~/.xnitrc
#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)
#
eval `cat ~/.fehbg` &
pypanel &
exec openbox
But I give your suggestion a try and edit my ~/.config/openbox/autostart.sh
I will report later or tomorrow
Offline
I use slim and an openbox entry in the ~/.xnitrc
#!/bin/sh # # ~/.xinitrc # # Executed by startx (run your window manager from here) # eval `cat ~/.fehbg` & pypanel & exec openbox
But I give your suggestion a try and edit my ~/.config/openbox/autostart.sh
I will report later or tomorrow
you can add the dbus entry also to your ~/.xinitrc.
or simply add following:
exec /usr/bin/openbox-session
and edit the autostart.sh
vlad
Offline
What do i have to type in the rc.conf for the session bus daemon?
http://wiki.archlinux.org/index.php/Daemons
Just incase you switch DE/WMs.
Offline
or another method is to start it via .xinitrc
dbus-launch --exit-with-session openbox
Offline
Thank you for all the help guys, but I'm still having some problems with it.
While dbus is launching fine now, but whenever a dbus-launch command is executed, my keyboard becomes unresponsive, no matter what I do.
If I skip those shell commands at the autostart.sh and enter them at a terminal at at later time. The keyboard misses keys from time to time. and This is very anoyying. I appreciate if anyone has a fix for this problem. Thanks!
Last edited by blu3ness (2008-01-22 04:21:01)
Archlinux on Compaq Presario v5000 laptop
Offline
or another method is to start it via .xinitrc
dbus-launch --exit-with-session openbox
That fixed it for me...thanks
Offline
removing the --exit-with-session argument fixed the unresponsive keyboard problem for me. Not sure why
Archlinux on Compaq Presario v5000 laptop
Offline
hi,
i had the same problem after a fresh install of arch (openbox as WM). It was actually ROXTerm which showed the "dbus connection fail" error, firefox could start without problem.
Anyways, all of this solutions didnt worked for me, but after i finally reinstalled hal and dbus, the problem now seems to be solved.
cheers
daniel
Offline