Ivman hal dbus problem

I tried automount and this with the packages from current and extra
when starting ivman I get this:
libhal.c 644 : Error connecting to system bus: Failed to connect to socket /var/lib/dbus/system_bus_socket: Connection refused
** (process:3869): WARNING **: manager.c/656: Failed to initialize HAL!
if I start hal it seems to start but later does not have a process so I think it stops again:
12:08:17.822 [I] hald.c:394: hal 0.4.7
12:08:17.823 [I] hald.c:396: Will daemonize
12:08:17.823 [I] hald.c:406: Becoming a daemon
ps ax|grep hal shows me nothing
finally dbus:
dbus gets started at boottime and has this lines when I ps for it:
3746 tty1     S      0:00 /usr/bin/dbus-launch --sh-syntax --exit-with-session
3747 ?        Ss     0:00 dbus-daemon-1 --fork --print-pid 8 --print-address 6
so somehow some kind of dbus is running but hal can't connect to it so ivman wont start.
I could not find any information about this problem.
any help appreciated
thanks
wabi

Hi
I got some other problem hal related
It was running since weeks without problems..automounting usb, cd etc.
since the latest update, where hal and dbus was updated some very very strange things happen.
After fresh start I had normally 77 processes running, mounting was ok etc.
Now...after a restart I got 150 processes running increasing every few seconds.
After a minute or so I got 280. 200 are hal and hotlug.hal related.
and the Hard Drive and CPU is always showing actibities. never happened before.
...and  automounting isn´t working anymore too.
What is this? 
tia
mic

Similar Messages

  • Hal/Dbus/gnome-volume-manager mount permission problem

    Hello,
    I have hal/dbus/gnome-volume-manager installed (of course I use gnome as DE).
    I need help in configuring the permissions for automatically mounted disk/partitions.
    When I connect an external USB HDD having 1 NTFS and 1 partition, these partitions are auto-mounted and the desktop icons appear for the both.
    As a normal user I am able to read/write FAT partition (I think, not because I have configured anything properly, but because FAT does not support permissions on filesystem), but I am not even able to read (browse) NTFS filesystem (ERORR: You do not have permission...).
    Yes, I have NTFS filesystm support enabled, because I am able to access that same NTFS partition as root.

    Well, Thanks for the reply but I had not put any static entry in fstab for this external USB HDD.
    Anyway, I figured out something (havn't tested it yet)
    When an external USB HDD is attached ... depending storage.policy and volume.policy rules in /usr/share/hal .. the hal daemon (hald) calls fstab-sync with appropriate parameters.
    fstab-sync, then, generates /etc/fstab enteries automatically (with comment=managed keyword).
    I have added a user policy so that umask and gid value is set correctly. I'll test is as soon as I'll get time.
    In the meanwhile if anybody have any other suggestions, please post it here.

  • Startup error messages for Pulseaudio initialization, dbus problem?

    I am experiencing some lag on startup when logging in with my user. I suspected something going wrong when initializing my autostart daemons. Indeed, Pulseaudio seems to have some trouble (but the sound output works just fine).
    Here is the tail of my /var/log/messages.log:
    Sep 24 11:36:31 localhost pulseaudio[520]: [pulseaudio] module.c: Failed to load module "module-jackdbus-detect" (argument: ""): initialization failed.
    Sep 24 11:36:31 localhost pulseaudio[520]: [pulseaudio] bluetooth-util.c: org.bluez.Manager.ListAdapters() failed: org.freedesktop.systemd1.LoadFailed: Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.
    Sep 24 11:36:31 localhost pulseaudio[520]: [pulseaudio] main.c: Module load failed.
    Sep 24 11:36:31 localhost pulseaudio[520]: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
    Sep 24 11:36:31 localhost pulseaudio[520]: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
    Sep 24 11:38:51 localhost pulseaudio[550]: [pulseaudio] module-jackdbus-detect.c: Unable to contact D-Bus session bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
    Sep 24 11:38:51 localhost pulseaudio[550]: [pulseaudio] module.c: Failed to load module "module-jackdbus-detect" (argument: ""): initialization failed.
    Sep 24 11:38:51 localhost pulseaudio[550]: [pulseaudio] bluetooth-util.c: org.bluez.Manager.ListAdapters() failed: org.freedesktop.systemd1.LoadFailed: Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.
    Sep 24 11:38:51 localhost pulseaudio[550]: [pulseaudio] main.c: Module load failed.
    Sep 24 11:38:51 localhost pulseaudio[550]: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
    Sep 24 11:38:51 localhost pulseaudio[550]: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
    Sep 24 11:40:08 localhost pulseaudio[913]: [pulseaudio] pid.c: Daemon already running.
    There seems to be some dbus problem.
    Here is /var/log/daemons.log:
    Sep 24 11:36:04 localhost [ 0.843288] systemd-udevd[48]: starting version 189
    Sep 24 11:36:04 localhost [ 4.252979] systemd[1]: systemd 189 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ; arch)
    Sep 24 11:36:04 localhost [ 4.261977] systemd[1]: Inserted module 'autofs4'
    Sep 24 11:36:04 localhost [ 4.262169] systemd[1]: Set hostname to <alppc>.
    Sep 24 11:36:04 localhost [ 4.334060] systemd[1]: Cannot add dependency job for unit pulseaudio.service, ignoring: Unit pulseaudio.service failed to load: No such file or directory. See system logs and 'systemctl status pulseaudio.service' for details.
    Sep 24 11:36:04 localhost [ 4.334069] systemd[1]: Cannot add dependency job for unit hal.service, ignoring: Unit hal.service failed to load: No such file or directory. See system logs and 'systemctl status hal.service' for details.
    Sep 24 11:36:04 localhost [ 4.334075] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. See system logs and 'systemctl status display-manager.service' for details.
    Sep 24 11:36:04 localhost [ 4.334197] systemd[1]: Socket service syslog.service not loaded, refusing.
    Sep 24 11:36:04 localhost [ 4.495856] systemd-udevd[155]: starting version 189
    Sep 24 11:36:05 localhost connmand[459]: Checking loopback interface settings
    Sep 24 11:36:05 localhost connmand[459]: System hostname is alppc
    Sep 24 11:36:05 localhost connmand[459]: Failed to open RFKILL control device
    Sep 24 11:36:05 localhost connmand[459]: lo {newlink} index 1 operstate 0 <UNKNOWN>
    Sep 24 11:36:05 localhost connmand[459]: eth0 {create} index 2 type 1 <ETHER>
    Sep 24 11:36:05 localhost connmand[459]: eth0 {update} flags 4098 <DOWN>
    Sep 24 11:36:05 localhost connmand[459]: eth0 {newlink} index 2 address 1C:6F:65:C4:12:E9 mtu 1500
    Sep 24 11:36:05 localhost connmand[459]: eth0 {newlink} index 2 operstate 2 <DOWN>
    Sep 24 11:36:05 localhost connmand[459]: Adding interface eth0 [ ethernet ]
    Sep 24 11:36:05 localhost connmand[459]: eth0 {update} flags 36867 <UP>
    Sep 24 11:36:05 localhost connmand[459]: eth0 {newlink} index 2 address 1C:6F:65:C4:12:E9 mtu 1500
    Sep 24 11:36:05 localhost connmand[459]: eth0 {newlink} index 2 operstate 2 <DOWN>
    Sep 24 09:36:05 localhost rtkit-daemon[521]: Successfully called chroot.
    Sep 24 09:36:05 localhost rtkit-daemon[521]: Successfully dropped privileges.
    Sep 24 09:36:05 localhost rtkit-daemon[521]: Successfully limited resources.
    Sep 24 09:36:05 localhost rtkit-daemon[521]: Running.
    Sep 24 09:36:05 localhost rtkit-daemon[521]: Watchdog thread running.
    Sep 24 09:36:05 localhost rtkit-daemon[521]: Canary thread running.
    Sep 24 11:36:05 localhost polkitd[525]: started daemon version 0.105 using authority implementation `local' version `0.105'
    Sep 24 11:36:06 localhost connmand[459]: eth0 {add} route fe80:: gw :: scope 0 <UNIVERSE>
    Sep 24 11:36:06 localhost connmand[459]: eth0 {update} flags 102467 <UP,RUNNING,LOWER_UP>
    Sep 24 11:36:06 localhost connmand[459]: eth0 {newlink} index 2 address 1C:6F:65:C4:12:E9 mtu 1500
    Sep 24 11:36:06 localhost connmand[459]: eth0 {newlink} index 2 operstate 6 <UP>
    Sep 24 11:36:06 localhost connmand[459]: eth0 {del} route fe80:: gw :: scope 0 <UNIVERSE>
    Sep 24 11:36:06 localhost connmand[459]: Skipping disconnect of carrier, network is connecting.
    Sep 24 11:36:06 localhost connmand[459]: eth0 {add} route fe80:: gw :: scope 0 <UNIVERSE>
    Sep 24 11:36:07 localhost connmand[459]: Setting domainname to fritz.box
    Sep 24 11:36:07 localhost connmand[459]: Deleting host route failed (No such process)
    Sep 24 11:36:07 localhost connmand[459]: eth0 {add} address 192.168.178.39/24 label eth0 family 2
    Sep 24 11:36:07 localhost connmand[459]: eth0 {add} route 192.168.178.0 gw 0.0.0.0 scope 253 <LINK>
    Sep 24 11:36:07 localhost connmand[459]: eth0 {add} route 192.168.178.1 gw 0.0.0.0 scope 253 <LINK>
    Sep 24 11:36:07 localhost connmand[459]: eth0 {add} route 0.0.0.0 gw 192.168.178.1 scope 0 <UNIVERSE>
    Sep 24 11:36:07 localhost connmand[459]: Setting default gateway route failed (File exists)
    Sep 24 11:36:08 localhost connmand[459]: eth0 {add} route 81.169.141.235 gw 192.168.178.1 scope 0 <UNIVERSE>
    Sep 24 11:36:08 localhost connmand[459]: Client-IP: 62.143.54.223
    Sep 24 11:36:08 localhost connmand[459]: Client-Country: DE
    Sep 24 11:36:08 localhost connmand[459]: eth0 {del} route 81.169.141.235 gw 192.168.178.1 scope 0 <UNIVERSE>
    Sep 24 11:38:23 localhost dbus[433]: [system] Activating systemd to hand-off: service name='org.freedesktop.ColorManager' unit='colord.service'
    Sep 24 11:38:23 localhost [ 0.849968] systemd-udevd[48]: starting version 189
    Sep 24 11:38:23 localhost [ 4.136460] systemd[1]: systemd 189 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ; arch)
    Sep 24 11:38:23 localhost [ 4.145534] systemd[1]: Inserted module 'autofs4'
    Sep 24 11:38:23 localhost [ 4.145728] systemd[1]: Set hostname to <alppc>.
    Sep 24 11:38:23 localhost [ 4.217389] systemd[1]: Cannot add dependency job for unit pulseaudio.service, ignoring: Unit pulseaudio.service failed to load: No such file or directory. See system logs and 'systemctl status pulseaudio.service' for details.
    Sep 24 11:38:23 localhost [ 4.217398] systemd[1]: Cannot add dependency job for unit hal.service, ignoring: Unit hal.service failed to load: No such file or directory. See system logs and 'systemctl status hal.service' for details.
    Sep 24 11:38:23 localhost [ 4.217404] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. See system logs and 'systemctl status display-manager.service' for details.
    Sep 24 11:38:23 localhost [ 4.217523] systemd[1]: Socket service syslog.service not loaded, refusing.
    Sep 24 11:38:23 localhost [ 4.394737] systemd-udevd[155]: starting version 189
    Sep 24 11:38:23 localhost dbus[433]: [system] Successfully activated service 'org.freedesktop.systemd1'
    Sep 24 11:38:23 localhost connmand[490]: Connection Manager version 1.6
    Sep 24 11:38:23 localhost connmand[490]: Checking loopback interface settings
    Sep 24 11:38:23 localhost connmand[490]: System hostname is alppc
    Sep 24 11:38:23 localhost dbus[433]: [system] Successfully activated service 'org.freedesktop.ColorManager'
    Sep 24 11:38:23 localhost dbus[433]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service'
    Sep 24 11:38:23 localhost connmand[490]: Failed to open RFKILL control device
    Sep 24 11:38:23 localhost connmand[490]: lo {newlink} index 1 operstate 0 <UNKNOWN>
    Sep 24 11:38:23 localhost connmand[490]: eth0 {create} index 2 type 1 <ETHER>
    Sep 24 11:38:23 localhost connmand[490]: eth0 {update} flags 4098 <DOWN>
    Sep 24 11:38:23 localhost connmand[490]: eth0 {newlink} index 2 address 1C:6F:65:C4:12:E9 mtu 1500
    Sep 24 11:38:23 localhost connmand[490]: eth0 {newlink} index 2 operstate 2 <DOWN>
    Sep 24 11:38:23 localhost connmand[490]: Adding interface eth0 [ ethernet ]
    Sep 24 11:38:23 localhost dbus[433]: [system] Activating via systemd: service name='org.freedesktop.colord-sane' unit='colord-sane.service'
    Sep 24 11:38:23 localhost dbus[433]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
    Sep 24 11:38:23 localhost connmand[490]: eth0 {update} flags 36867 <UP>
    Sep 24 11:38:23 localhost connmand[490]: eth0 {newlink} index 2 address 1C:6F:65:C4:12:E9 mtu 1500
    Sep 24 11:38:23 localhost connmand[490]: eth0 {newlink} index 2 operstate 2 <DOWN>
    Sep 24 11:38:23 localhost dbus[433]: [system] Successfully activated service 'org.freedesktop.colord-sane'
    Sep 24 11:38:23 localhost dbus[433]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
    Sep 24 11:38:23 localhost dbus[433]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
    Sep 24 11:38:24 localhost dbus[433]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
    Sep 24 11:38:24 localhost dbus[433]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
    Sep 24 09:38:24 localhost rtkit-daemon[551]: Successfully called chroot.
    Sep 24 09:38:24 localhost rtkit-daemon[551]: Successfully dropped privileges.
    Sep 24 09:38:24 localhost rtkit-daemon[551]: Successfully limited resources.
    Sep 24 09:38:24 localhost rtkit-daemon[551]: Running.
    Sep 24 09:38:24 localhost rtkit-daemon[551]: Canary thread running.
    Sep 24 09:38:24 localhost rtkit-daemon[551]: Watchdog thread running.
    Sep 24 11:38:24 localhost dbus[433]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper)
    Sep 24 11:38:24 localhost polkitd[555]: started daemon version 0.105 using authority implementation `local' version `0.105'
    Sep 24 11:38:24 localhost dbus[433]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
    Sep 24 11:38:24 localhost dbus[433]: [system] Activating via systemd: service name='org.freedesktop.ConsoleKit' unit='console-kit-daemon.service'
    Sep 24 11:38:24 localhost dbus[433]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
    Sep 24 11:38:24 localhost dbus[433]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
    Sep 24 11:38:25 localhost connmand[490]: eth0 {add} route fe80:: gw :: scope 0 <UNIVERSE>
    Sep 24 11:38:25 localhost connmand[490]: eth0 {update} flags 102467 <UP,RUNNING,LOWER_UP>
    Sep 24 11:38:25 localhost connmand[490]: eth0 {newlink} index 2 address 1C:6F:65:C4:12:E9 mtu 1500
    Sep 24 11:38:25 localhost connmand[490]: eth0 {newlink} index 2 operstate 6 <UP>
    Sep 24 11:38:25 localhost connmand[490]: eth0 {del} route fe80:: gw :: scope 0 <UNIVERSE>
    Sep 24 11:38:25 localhost connmand[490]: Skipping disconnect of carrier, network is connecting.
    Sep 24 11:38:25 localhost connmand[490]: eth0 {add} route fe80:: gw :: scope 0 <UNIVERSE>
    Sep 24 11:38:26 localhost dbus[433]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
    Sep 24 11:38:26 localhost dbus[433]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
    Sep 24 11:38:26 localhost connmand[490]: Setting domainname to fritz.box
    Sep 24 11:38:26 localhost connmand[490]: Deleting host route failed (No such process)
    Sep 24 11:38:26 localhost connmand[490]: eth0 {add} address 192.168.178.39/24 label eth0 family 2
    Sep 24 11:38:26 localhost connmand[490]: eth0 {add} route 192.168.178.0 gw 0.0.0.0 scope 253 <LINK>
    Sep 24 11:38:26 localhost connmand[490]: eth0 {add} route 192.168.178.1 gw 0.0.0.0 scope 253 <LINK>
    Sep 24 11:38:26 localhost connmand[490]: eth0 {add} route 0.0.0.0 gw 192.168.178.1 scope 0 <UNIVERSE>
    Sep 24 11:38:26 localhost connmand[490]: Setting default gateway route failed (File exists)
    Sep 24 11:38:26 localhost connmand[490]: eth0 {add} route 81.169.141.235 gw 192.168.178.1 scope 0 <UNIVERSE>
    Sep 24 11:38:26 localhost connmand[490]: Client-IP: 62.143.54.223
    Sep 24 11:38:26 localhost connmand[490]: Client-Country: DE
    Sep 24 11:38:26 localhost connmand[490]: eth0 {del} route 81.169.141.235 gw 192.168.178.1 scope 0 <UNIVERSE>
    Sep 24 11:38:27 localhost dbus[433]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
    Sep 24 11:38:27 localhost dbus[433]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
    Sep 24 11:38:28 localhost dbus[433]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
    Sep 24 11:38:28 localhost dbus[433]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
    Sep 24 09:38:49 localhost rtkit-daemon[551]: Warning: PolicyKit call failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
    Sep 24 11:38:49 localhost dbus[433]: [system] Failed to activate service 'org.freedesktop.ConsoleKit': timed out
    Sep 24 11:38:51 localhost dbus[433]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
    Sep 24 11:38:51 localhost dbus[433]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.
    Sep 24 11:40:07 localhost dbus[433]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
    Sep 24 11:40:07 localhost dbus[433]: [system] Successfully activated service 'org.freedesktop.UPower'
    Sep 24 11:40:07 localhost dbus[433]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
    Sep 24 11:40:07 localhost udisksd[839]: udisks daemon version 1.94.0 starting
    Sep 24 11:40:07 localhost dbus[433]: [system] Successfully activated service 'org.freedesktop.UDisks2'
    Sep 24 11:40:07 localhost udisksd[839]: Acquired the name org.freedesktop.UDisks2 on the system message bus
    Sep 24 11:40:08 localhost udisksd[839]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/WDC_WD1600ADFD_60NLR5_WD_WMAP42316678: Error updating SMART data: sk_disk_smart_status: Input/output error (udisks-error-quark, 0)
    Sep 24 09:50:09 localhost udisksd[839]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/WDC_WD1600ADFD_60NLR5_WD_WMAP42316678: Error updating SMART data: sk_disk_smart_status: Input/output error (udisks-error-quark, 0)
    And here is my /var/log/errors.log:
    Sep 24 11:36:04 localhost [ 4.334197] systemd[1]: Socket service syslog.service not loaded, refusing.
    Sep 24 11:36:04 localhost kernel: [ 5.310147] CX24123: cx24123_i2c_readreg: reg=0x0 (error=-121)
    Sep 24 11:36:04 localhost kernel: [ 5.310444] CX24123: wrong demod revision: 87
    Sep 24 11:36:05 localhost connmand[459]: Failed to open RFKILL control device
    Sep 24 11:36:07 localhost connmand[459]: Deleting host route failed (No such process)
    Sep 24 11:36:07 localhost connmand[459]: Setting default gateway route failed (File exists)
    Sep 24 11:36:31 localhost pulseaudio[520]: [pulseaudio] module-jackdbus-detect.c: Unable to contact D-Bus session bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
    Sep 24 11:36:31 localhost pulseaudio[520]: [pulseaudio] module.c: Failed to load module "module-jackdbus-detect" (argument: ""): initialization failed.
    Sep 24 11:36:31 localhost pulseaudio[520]: [pulseaudio] bluetooth-util.c: org.bluez.Manager.ListAdapters() failed: org.freedesktop.systemd1.LoadFailed: Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.
    Sep 24 11:36:31 localhost pulseaudio[520]: [pulseaudio] main.c: Module load failed.
    Sep 24 11:38:23 localhost [ 4.217523] systemd[1]: Socket service syslog.service not loaded, refusing.
    Sep 24 11:38:23 localhost kernel: [ 5.220124] CX24123: cx24123_i2c_readreg: reg=0x0 (error=-121)
    Sep 24 11:38:23 localhost kernel: [ 5.220487] CX24123: wrong demod revision: 87
    Sep 24 11:38:23 localhost connmand[490]: Failed to open RFKILL control device
    Sep 24 11:38:26 localhost connmand[490]: Deleting host route failed (No such process)
    Sep 24 11:38:26 localhost connmand[490]: Setting default gateway route failed (File exists)
    Sep 24 11:38:51 localhost pulseaudio[550]: [pulseaudio] module-jackdbus-detect.c: Unable to contact D-Bus session bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
    Sep 24 11:38:51 localhost pulseaudio[550]: [pulseaudio] module.c: Failed to load module "module-jackdbus-detect" (argument: ""): initialization failed.
    Sep 24 11:38:51 localhost pulseaudio[550]: [pulseaudio] bluetooth-util.c: org.bluez.Manager.ListAdapters() failed: org.freedesktop.systemd1.LoadFailed: Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.
    Sep 24 11:38:51 localhost pulseaudio[550]: [pulseaudio] main.c: Module load failed.
    Sep 24 11:40:08 localhost pulseaudio[913]: [pulseaudio] pid.c: Daemon already running.
    What is going on here? Could someone explain how to resolve this issue?
    Last edited by Alp (2012-09-24 07:56:44)

    # /etc/rc.conf - configuration file for initscripts
    # Most of rc.conf has been replaced by various other configuration
    # files. See archlinux(7) for details.
    # For more details on rc.conf see rc.conf(5).
    DAEMONS=(syslog-ng !network dbus hal connmand ntpd !hwclock crond @cupsd @samba @httpd @mysqld @nginx pulseaudio @alsa @mpd @mpdscribble !slim)
    #DAEMON_LOCALE="yes"
    # Storage
    # USEDMRAID="no"
    # USELVM="no"
    # Network
    interface=eth0
    # address=
    # netmask=
    # gateway=

  • KDE / HAL / dbus

    I am trying to setup HAL/dbus with KDE, but have hit a bit of a snag. When popping in a CD/DVD or USB device, then selecting "Open in New Window" from the prompt, I get this message ("/mnt/usbdisk" differs when using a dvd):
    /mnt/usbdisk is a folder, but a file was expected.
    After that error message, I can click the link on my desktop to the device, and it opens up.
    Here is some relevant information:
    /etc/fstab:
    /dev/sr0 /mnt/dvd auto ro,user,noauto,nodev,nosuid0 0
    /dev/sdc1 /mnt/usbdisk auto user,noauto,nodev,nosuid 0 0

    xyon wrote:
    Here is some relevant information:
    /etc/fstab:
    /dev/sr0 /mnt/dvd auto ro,user,noauto,nodev,nosuid0 0
    /dev/sdc1 /mnt/usbdisk auto user,noauto,nodev,nosuid 0 0
    Removable media shall be controllable by HAL of operating system, which does automount. /etc/fstab creates hard mounts. Even if the documents or fstab examples state what you pasted, remove these lines or comment them out. Let Linux do it for you.

  • Autofs or hal/dbus ?

    When I was setting up my Arch box I used autofs so it would automount dvds I wanted to watch with smplayer.  Then I wanted to try "thunar", which needed hal/dbus.  When I enable hal in my rc.conf and rebooted, it said the DVD was locked - by autofs I assume.  So I removed autofs from my rc.conf, and rebooted.  Now thunar works.  I had avoided hal/dbus because I thought I read they were part of gnome and I was afraid it would clutter my system, but then I found it was already installed and I just had to enable it.  Is using autofs deprecated in favor of using hal/dbus?

    HAL and dbus are needed by alot of things, and using it in conjunction with a volume manager (such as  thunar-volman) seems to be the prefered way to do it.
    not sure if autofs is "deprecated" (i can think of a few uses where it'd work better than hal/dbus+volume manager) but since you already got hal/dbus + a volume manager installed, use them

  • Hal or dbus problem?

    Hi,
    when starting banshee I get
    banshee
    Warning: [13/09/2006 15:03:59] (Cannot connect to NetworkManager) - An available, working network connection will be assumed
    Debug: [13/09/2006 15:03:59] (Default player engine) - GStreamer 0.10
    Warning: [13/09/2006 15:03:59] (HAL context could not be created) - Could not initialise HAL context; D-Bus may not be working or configured properly
    Warning: [13/09/2006 15:03:59] (Audio CD support will be disabled for this instance) - HAL is not initialised
    Warning: [13/09/2006 15:03:59] (DAP support will be disabled for this instance) - Cannot initialise DapCore because HalCore is not initialised
    Warning: [13/09/2006 15:03:59] (Could not initialize plugin `Daap') - Daemon not running
    Warning: [13/09/2006 15:04:00] (Could not connect to D-Bus) - D-Bus support will be disabled for this instance: Unable to determine the address of the message bus (try 'man dbus-launch' and 'man dbus-daemon' for help)
    Scanning library for tracks to update
    Done scanning library
    Processing track queue for pending queries
    Setting MusicBrainz proxy to www.musicbrainz.org:80
    Done processing track queue
    Now hal in daemons in rc.conf... ipod is connected but does not show up now
    emmmm  :?

    emmmm ... so I have to run that every time I use banshee???
    dbus-launch banshee
    Warning: [13/09/2006 17:06:25] (Cannot connect to NetworkManager) - An available, working network connection will be assumed
    Debug: [13/09/2006 17:06:26] (Default player engine) - GStreamer 0.10
    Debug: [13/09/2006 17:06:26] (Audio CD Core Initialised) -
    Warning: [13/09/2006 17:06:26] (Could not initialize plugin `Daap') - Daemon not running
    Scanning library for tracks to update
    Done scanning library
    Processing track queue for pending queries
    Setting MusicBrainz proxy to www.musicbrainz.org:80
    Done processing track queue
    weird!
    (I never read error messages as a rule lol. ..
    thanks dude 

  • HAL/DBUS No longer works in nautilus.

    Hey,
    After a recent upgrade I noticed that nautilus no longer recognises any devices such as USB or DVD/CD there's is no longer even an icon with which to mount from. This worked perfectly before but stopped after the upgrade. I checked hal and dbus and they both start and are definitely running, outside of that, I can't even see any errors.
    Any help?
    I also just noticed that my wastebasket no longer works. Has anything major happened to nautilus? I think that's where the problem may be/ I checked the logs and they mostly show udev picking it up but it never shows in nautilus, not even an icon. Also the only associated error is 
    kernel: sd 6:0:0:0: [sdf] Assuming drive cache: write through
    Last edited by MrGone (2009-09-30 21:59:38)

    No i'm just using the one in extra i believe.
    Last edited by MrGone (2009-09-30 19:21:47)

  • Ivman or dbus configuraion error

    Hi, I just installed ivman and just wanted it to automount my cdrom drive.
    In my IvmConfigActions.xml I have the following rule:
    <ivm:Match name="storage.removable" value="true">
            <ivm:Option name="unlock" value="true" />
    </ivm:Match>
    In my Mappings file I have a:
    <ivm:Map device="/dev/cdroms/cdrom0"    maps="/dev/ide/host1/bus0/target0/lun0/cd"/>
    my fstab is setup in a way that, if I say mount /dev/cdroms/cdrom0 or mount /mnt/cdrom, I can access my drive.
    As I searched on the gentoo forums, I read in a thread that you should use dbus-monitor --system and watch for any message, when removing/inserting a cdrom, but I got none.
    Then I tried to remove and plug in my usb mouse and got:
    signal interface=org.freedesktop.Hal.Manager; member=DeviceRemoved; sender=:1.0
    string:/org/freedesktop/Hal/devices/usb_usb_device_46d_c00e_1110_-1_noserial_0
    signal interface=org.freedesktop.Hal.Manager; member=DeviceRemoved; sender=:1.0
    string:/org/freedesktop/Hal/devices/usb_device_46d_c00e_1110_-1_noserial
    signal interface=org.freedesktop.Hal.Manager; member=DeviceAdded; sender=:1.0
    string:/org/freedesktop/Hal/devices/usb_device_46d_c00e_1110_-1_noserial
    signal interface=org.freedesktop.Hal.Manager; member=DeviceAdded; sender=:1.0
    string:/org/freedesktop/Hal/devices/usb_usb_device_46d_c00e_1110_-1_noserial_0
    So I think there is something wrong with my dbus configuration.

    Well first of all ivman will only work for root straight out of the box. After you remove the .default extension you need to add to your rc.conf in DAEMONS: dbus hal ivman in that order, hal requires dbus to be started ahead. Reboot. log onto to your normal user and at the konsole type: ivman &. Dont worry about the warnings. Now you should see a hidden folder under your home directory (/home/username/.ivman). In there you will find similar config files that will need to be uncommented( "<!--" and "-->" ) -read through carefully. To get this to happen every time you need to go into your /home/user/.kde/Autostart folder and right click->create new file->link to application->. In the application tab enter ivman for the command. In advanced options I would deselect launch feedback. Click ok to finish then go back and right click and select properties and check the executeable box now that its been created.

  • (TRASH) dbus problem....cant login to gui-(TRASH)

    ok...so I get this error on startup
    failed to start message bus Error in file /etc/dbus-1/system.d/gdm.conf line 1 column 16 not well formed
    I have xfce4, dbus, hal, gamin, gdm, and all the xf86-input-synaptic and such all freshly installed on this laptop...
    when I startxfce4 it opens but no keyboard or mouse.... am I missing something? last time I did this all I needed was the xf86 drivers and such and it worked fine.
    Could I have installed hal or gdm wrong?
    When I tried to gdm from the command line I get:
    /usr/sbin/gdm line1: syntax error near unexpected token '('
    /usr/sbin/gdm line 1: 'n tfds_in_quene (1:2)'
    Last edited by BarefootSoul83 (2010-03-31 14:50:48)

    BarefootSoul83 wrote:
    I use xorg... Hal (being tied to dbus) is not starting and giving me this error:
    failed to start message bus Error in file /etc/dbus-1/system.d/gdm.conf line 1 column 16 not well formed
    Another reason I hate gdm
    Maybe try slim?
    http://wiki.archlinux.org/index.php/Slim
    Sorry that this doesn't directly solve your problem. I just thought of a suggestion
    Also, reinstalling them never hurt. Maybe run:
    pacman -S hal
    pacman -S dbus
    pacman -S gdm
    Last edited by itsbrad212 (2010-03-29 05:01:42)

  • Dbus problems, sudo and wicd fail to work

    Every time I try to run any command with "sudo", my system hangs, and the terminal that I entered this into becomes unusable (no ctrl+C will exit the process).
    For some reason wicd is also not running; when I use "wicd-client" from the command line, I get this error:
    ERROR:dbus.proxies:Introspect error on :1.22:/org/wicd/daemon: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply.
    I have hal in my DAEMONS section of my rc.conf, which should start dbus (I have also tried adding dbus right before hal as well), so while dbus has started, it doesn't seem to be working.
    I can supply any more information, but this problem has gone past my individual troubleshooting capability and a conventional google search.

    This is not a sudo bug from what I can tell, but rather a dbus bug that is breaking many programs, sudo included.
    Reinstalling could be difficult, since wicd will not start, I have no internet.
    EDIT: also rebooting does not work, I have to force power off. The system stalls at trying to halt the dbus daemon.
    Last edited by xvedejas (2010-04-21 01:24:39)

  • Wireless, Network-manager, dbus problem

    Hey, I'm trying to connect to wireless network at school using dhcdbd, gnome-network-manager, nm-applet... and it works but get disconnected constantly. Don't know much about networking so could use some help. Here's some output with lots of dbus errors...any ideas? Thanks.
    ** Message: <information> You are now connected to the wireless network 'XXXXXXXXXXX'.
    libnotify-Message: Unable to get session bus: Unable to determine the address of the message bus (try 'man dbus-launch' and 'man dbus-daemon' for help)
    ** (nm-applet:5382): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
    ** (nm-applet:5382): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
    ** (nm-applet:5382): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
    ** (nm-applet:5382): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
    ** (nm-applet:5382): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
    ** (nm-applet:5382): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
    libnotify-Message: Unable to get session bus: Unable to determine the address of the message bus (try 'man dbus-launch' and 'man dbus-daemon' for help)
    ** (nm-applet:5382): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
    ** (nm-applet:5382): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
    ** (nm-applet:5382): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
    ** (nm-applet:5382): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
    ** (nm-applet:5382): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
    ** (nm-applet:5382): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
    ** (nm-applet:5382): WARNING **: <WARNING> nmi_save_network_info (): Error saving secret for wireless network 'XXXXXXXXXXX' in keyring: 2
    ** Message: <information> You are now connected to the wireless network 'XXXXXXXXXXX'.
    libnotify-Message: Unable to get session bus: Unable to determine the address of the message bus (try 'man dbus-launch' and 'man dbus-daemon' for help)
    ** (nm-applet:5382): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
    ** (nm-applet:5382): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
    ** (nm-applet:5382): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
    ** (nm-applet:5382): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
    ** (nm-applet:5382): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
    ** (nm-applet:5382): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
    libnotify-Message: Unable to get session bus: Unable to determine the address of the message bus (try 'man dbus-launch' and 'man dbus-daemon' for help)
    ** (nm-applet:5382): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
    ** (nm-applet:5382): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
    ** (nm-applet:5382): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
    ** (nm-applet:5382): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
    ** (nm-applet:5382): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
    ** (nm-applet:5382): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
    ** (nm-applet:5382): WARNING **: <WARNING> nmi_save_network_info (): Error saving secret for wireless network 'XXXXXXXXXXX' in keyring: 2

    When I configure a Wep key to my wireless internet
    sharing network, my windows installed notebook can't
    connect to my iMac. But when I set up it free the
    notebook connects easily.
    There does seem to be a known issue with a WEP encrypted software base station and Windows clients.
    As far as I am aware there is no way to get a Windows client to connect to a WEP encrypted software base station (sharing internet via Airport on a Mac).
    I tried both with ASCII and
    HEX keys and generated them from:
    You could try a ASCII key of
    1234567123456
    which will be a HEX key of
    31323334353637313233343536
    However if this doesn't work then nothing will.
    I don't know what to do and I don't want to set a
    wireless network free for security problems. Does
    anyone know a solution?
    Yes, get a wireless router and use that, it really is the only suitable solution.
    iFelix

  • Odd hal automounting problem

    Hi
    usually when I bung a dvd in my drive, hal automounts it to /media and I can see it in thunar
    but all of a sudden it gets mounted to /mnt/cd and when I click on it in thunar I get the following error:
    Failed to mount "stuff".
    Failed to determine the mount point for /dev/hdc
    nor can I eject it, I get a message saying it wasn't mounted by hal:
    how can I find out what is mounting it and stop it??
    I've recently installed banshee and rhythmbox, could this have anything to do with it?

    In case anyone cares, or has a similar problem I fixed this
    I think the problem was I had pmount installed as a dependancy of one of the mp3 players I installed (banshee I think), and it was auto-mounting dvds before hal got a chance.
    When I uninstalled banshee, it didn't uninstall the huge amount of other packages it installed with it. I'm still an arch newbie, and would like to know how I would have uninstalled banshee and all the other packages that come with it using pacman.
    Anyone help?

  • Annoying inconsistent udev/HAL/dbus external USB HDD detection...

    Hello!  I am a newbie to ARCH.  When I first installed it, my USB drive almost always was detected AND auto-mounted upon booting into GNOME.  It was beautiful.  This shows that I have DBUS/HAL and all that nice stuff installed. 
    After a while, I decided to update my daemons as below.  (i added portmap and fam --- that is all!)
    DAEMONS=(syslog-ng network portmap fam dbus hal netfs crond alsa openntpd gdm)
    Anyway... now the USB external drive is never automatically detected or mounted, period.  I have to boot into GNOME, THEN unplug the USB cable... wait a bit... plug it back in.  Then it is detected.  Then I have to manually do:
    mount /dev/sda5 /media/usb
    mount /dev/sda6 /media/usb
    to mount them.  This is very annoying. 
    Is there anyway to get consistent detection and auto-mounting behavior???  It was working fine the first few times.  No idea where I went wrong, friends.
    btw... i am in the proper groups for my user too, though that is irrelevant because if i wasn't, it would still show up, just give me a security msg preventing mounting - GROUPS = disk wheel ftp dbus hal network video audio optical storage camera power users pacman
    Last edited by darweth (2007-04-07 13:42:39)

    Well, I eventually discovered the necessity of gnome-volume-manager and all is fine now.   No more help needed.  Weird that the behavior was bipolar w/o it though.

  • DBUS problem

    Hi, I have a big problem. After an upgrade I cannot start any service (including x server) as normal user. Some time ago I had to add policy for nm-applet the same as root for me. Now I cannot do anything unless I am root. The biggest deal is I cannot even log in. I use cdm and dwm and it cannot log me in. Please help me. I am desperate. I think just blind adding policies doesn't solve anything, or if it does, I think this is not the right way. I am in the dbus group. (also in root group). Please don't tell me I have to reinstall the system. I would have to kill myself.
    EDIT: the nm-applet problem was, that the network manager couldn't start, so I had to add something like <policy user="sdoky"> <allow ...> </policy> just copy those lines from root, just add them below the root with changed user. I could have lived with that (also using wicd right now - has a ncurses client)
    HELP please, I am desperate. There must be something I am doing wrong... please tell me what.
    Last edited by sDoky (2010-04-02 20:19:19)

    This sounds all pretty vague I doubt anyone can help you with this little information. And why exactly are you making reinstalling look like such a drama, you have backups, don't you? And even if you don't it's not like it's impossible to use a Live system for backupping data. And then a reinstall is what, 3 hours of work at most?!
    The best reason I see for not reinstalling would be seeing it as a challenge, which I'd understand perfectly but then again that doesn't make one desperate.
    If you need to be root for such simple tasks maybe permsisions for a folder like /usr/bin are messed up, I doubt DBUS is to blame. And where exactly have you added those policies?
    And please stay  a little bit more calm if you want people to help you it's not like you haven't chosen freely to use a Linux distribution that needs a little bit more work than others.
    Could you elaborate on what exactly are the sympotms what is the ouput of the commands you can't run as a normal user?
    Which commands are you trying to run and whats in your X error logs?

  • Banshee + dbus problem

    I just switched from gnome to xfce and xmonad.
    Everything is wonderful but I've got an issue with banshee.
    It works, but it doesn't "connect" to dbus, and so I can't set my keybindings to it since if I try to execute something like "banshee-1 --previous" it would open a new banshee istance
    [Info 01:13:22.903] Running Banshee 1.5.2: [source-tarball (linux-gnu, x86_64) @ 2009-11-21 20:36:59 UTC]
    [Warn 01:13:23.096] DBus support could not be started. Disabling for this session.
    [Warn 01:13:23.709] Caught an exception - No support GNOME Settings Daemon could be reached. (in `Banshee.MultimediaKeys')
    at Banshee.MultimediaKeys.MultimediaKeysService.Banshee.ServiceStack.IExtensionService.Initialize () [0x00000]
    at Banshee.ServiceStack.ServiceManager.StartExtension (Mono.Addins.TypeExtensionNode node) [0x00000]
    [Warn 01:13:23.709] Extension `Banshee.MultimediaKeys.MultimediaKeysService' not started: No support GNOME Settings Daemon could be reached.
    [Warn 01:13:23.776] Caught an exception - No support GNOME Settings Daemon could be reached. (in `Banshee.MultimediaKeys')
    at Banshee.MultimediaKeys.MultimediaKeysService.Banshee.ServiceStack.IExtensionService.Initialize () [0x00000]
    at Banshee.ServiceStack.ServiceManager.StartExtension (Mono.Addins.TypeExtensionNode node) [0x00000]
    [Warn 01:13:23.776] Extension `Banshee.MultimediaKeys.MultimediaKeysService' not started: No support GNOME Settings Daemon could be reached.
    [Info 01:13:23.777] All services are started 0.680205s
    [Warn 01:13:24.212] IScreensaverManager extension failed to load - Argument cannot be null.
    Parameter name: address (in `NDesk.DBus')
    at NDesk.DBus.Bus.Open (System.String address) [0x00000]
    at NDesk.DBus.Bus.get_Session () [0x00000]
    Unable to open the session message bus. (in `NDesk.DBus')
    at NDesk.DBus.Bus.get_Session () [0x00000]
    at Banshee.GnomeBackend.GnomeScreensaverManager.get_Manager () [0x00000]
    at Banshee.GnomeBackend.GnomeScreensaverManager..ctor () [0x00000]
    at (wrapper managed-to-native) System.Reflection.MonoCMethod:InternalInvoke (object,object[],System.Exception&)
    at System.Reflection.MonoCMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000]
    Exception has been thrown by the target of an invocation. (in `mscorlib')
    at System.Reflection.MonoCMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000]
    at System.Reflection.MonoCMethod.Invoke (BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000]
    at System.Reflection.ConstructorInfo.Invoke (System.Object[] parameters) [0x00000]
    at System.Activator.CreateInstance (System.Type type, Boolean nonPublic) [0x00000]
    at System.Activator.CreateInstance (System.Type type) [0x00000]
    at Mono.Addins.TypeExtensionNode.CreateInstance () [0x00000]
    at Mono.Addins.InstanceExtensionNode.CreateInstance (System.Type expectedType) [0x00000]
    at Banshee.PlatformServices.ScreensaverManager..ctor () [0x00000]
    [Info 01:13:24.434] nereid Client Started
    The problem is exactly the one described here: http://bbs.archlinux.org/viewtopic.php?id=65189 and in fact if I try to launch banshee with dbus-launch it doesn't throw that error.
    Is there a way to fix that?

    ok, someone suggested the solution in irc: http://wiki.archlinux.org/index.php/D-Bus#D-bus_Launch

Maybe you are looking for

  • Error during restore/recovery and 'open resetlogs'

    Hello forum. I'm attempting to restore a database to a new host and have run into an error during the opening of the database (with resetlogs). The renaming of the datafiles, restore, switching of datafiles, and recovery are all done by an rman scrip

  • RAW files in CS4 Extended, I'm Wndows Vist platform

    I have a Canon EOS 7D and a Canon EOS 50D and CS4 Extended, I've downloaded the camera raw 5.3 updater for windows.  The CS4 is recognising my raw files on my 50D but not my 7D, can someone help me out?

  • Should I have restored on a new iphone?

    Hi all, I upgraded my phone to the 5S today and when I plugged it in to my itunes it came up with the options of setting up a new phone or (and had already selected) restoring a phone.  As it was already selected and because I wanted everything from

  • Changing Schema information in BPEL

    Hi, We are working on an assignment for which we had developed an XSD for the BPEl process. Due to certain requirements which keep cropping up we need to add certain nodes/elements to the XSD. But everytime we make a change in the XSD (under Schemas

  • Syncing podcasts on apple tv

    I can't get my podcasts on my iPhone (running iOS 7.0.2) to sync properly with my Apple tv running 6.0.  Most show up, but there's always one or missing, and podcasts listened to on my phone still show unplayed on my Apple TV.