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 

Similar Messages

  • 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

  • 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=

  • Hal and dbus not starting

    They are both in daemons...and for /etc/rc.d/hal restart it faisl same with dbus and with using 'start' instead of 'restart'.
    /usr/sbin/hald --daemon=no --verbose=yes gives me this:
    /usr/sbin/hald --daemon=no --verbose=yes
    14:31:01.105 [i] hald.c:532: hal 0.5.9
    14:31:01.106 [i] hald.c:597: Will not daemonize
    14:31:01.106 [i] hald_dbus.c:4806: local server is listening at unix:abstract=/var/run/hald/dbus-JQyZPmcfA6,guid=4867547682ff4e78d054ad0046608205
    Runner started - allowed paths are '/usr/lib/hal:/usr/lib/hal/scripts:/usr/bin'
    14:31:01.112 [i] hald_runner.c:299: Runner has pid 5829
    14:31:01.113 [W] ci-tracker.c:200: Could not get uid for connection: org.freedesktop.DBus.Error.NameHasNoOwner Could not get UID of name 'org.freedesktop.DBus': no such name
    14:31:01.116 [E] hald_dbus.c:4461: Cannot get caller info for org.freedesktop.DBus
    14:31:01.116 [i] hald_runner.c:180: runner connection is 0x8091888
    14:31:01.117 [i] mmap_cache.c:251: cache mtime is 1180561064
    Error binding udev_event socket: Address already in use
    And when trying to start dbus with /etc/rc.d/dbus restart i get this when it fails:
    Failed to start message bus: Failed to bind socket "/var/run/dbus/system_bus_socket": Address already in use
    Any suggestions?

    If you think it's a common problem how about filing a bug report.  Would likely help more people than just posting in the forum.  Just a suggestion.

  • (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

  • (SOLVED) Hal and dbus, do I need dbus?

    I read the wiki and it says if I don't use hal in my daemons then I need to add dbus.
    I haven't been using hal, and I haven't added dbus either. My system seems to be working right, but I guess something could be wrong. Reading the wiki brings me here to ask if I need dbus and why?
    My daemons,
    DAEMONS=(@syslog-ng @network !netfs @alsa @mpd @crond)
    Last edited by Google (2010-07-03 11:21:11)

    sudo pacman -R dbus
    checking dependencies...
    error: failed to prepare transaction (could not satisfy dependencies)
    :: avahi: requires dbus>=1.1.20-1
    :: awesome: requires dbus
    :: gconf: requires dbus
    :: qt: requires dbus
    I assume I should add it to daemons?
    Last edited by Google (2010-07-03 10:08:18)

  • Hal cd automounting problem

    hi,
    im having a bit of a problem with hal! it finds flash pens & my sony ericsson phone fine, and puts them on the right hand side of pcmanfm in the location box, but cd's arent!
    if i open konqueror and goto media:/ my cd is listed there ready to mount, but i cant access media:/ through pcmanfm!
    how can i get hal to do the same with cd's as it does with flash pens & my phone??
    thanks.

    You don't need HAL to do that. Just make sure your /etc/fstab is correct, f.e.:
    /dev/sr0     /media/disc     auto     user,exec,noauto,comment=managed     0     0

  • 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

  • Wicd stopped working - (DBus problem at all?)

    Hi,
    today I have turned my laptop on and discovered, that I am not able to connect to wireless network. Wicd started to complain about DBus connection. Everything looks like this: I turn on computer, Slim logs me in, Wicd starts to connect to wireless network. After few seconds Wicd dies. When I try to start it again, it complains about DBus connection. So I have to "systemctl stop wicd" and run the daemon by "sudo wicd". Now, I am able to connect to wireless network via Wicd, but after few minutes Wicd dies again.
    Other problem - udiskie. When I plug in flash drive, nothing happens. When I run udiskie from console, no output is given - simply nothing. It seems like a problem with DBus at all to me. Do you have any ideas, how to fix it?
    Wicd: version 1.7.2.4-5
    Udiskie: version 0.4.1-4
    Systemd: version 197-4
    Uname -a: Linux linuch-laptop 3.6.11-1-ARCH #1 SMP PREEMPT Tue Dec 18 08:57:15 CET 2012 x86_64 GNU/Linux
    [michal@linuch-laptop ~]$ pacman -Q |egrep "(wicd|dbus|udisk)"
    dbus 1.6.8-6
    dbus-glib 0.100-1
    lib32-dbus-core 1.6.8-1
    python-dbus-common 1.1.1-2
    python2-dbus 1.1.1-2
    udiskie 0.4.1-4
    udisks 1.0.4-6
    udisks2 2.0.1-1
    wicd 1.7.2.4-5
    wicd-gtk 1.7.2.4-5
    I am using systemd, WM is Openbox.
    Here are some outputs from terminal:
    [michal@linuch-laptop ~]$ sudo systemctl status wicd.service
    wicd.service - Wicd a wireless and wired network manager for Linux
    Loaded: loaded (/usr/lib/systemd/system/wicd.service; enabled)
    Active: failed (Result: exit-code) since Ne 2013-01-20 16:57:15 CET
    Process: 871 ExecStart=/usr/sbin/wicd --no-daemon (code=exited, status=1/FAILURE)
    led 20 16:57:15 linuch-laptop systemd[1]: wicd.service: main process exited, code=exited, status=1/FAILURE
    led 20 16:57:15 linuch-laptop systemd[1]: Failed to start Wicd a wireless and wired network manager for Linux.
    led 20 16:57:15 linuch-laptop systemd[1]: Unit wicd.service entered failed state
    [michal@linuch-laptop ~]$ sudo systemctl status dbus.socket
    dbus.socket - D-Bus System Message Bus Socket
    Loaded: loaded (/usr/lib/systemd/system/dbus.socket; static)
    Active: active (running) since Ne 2013-01-20 16:56:38 CET
    led 20 16:56:38 linuch-laptop systemd[1]: Listening on D-Bus System Message Bus Socket.
    [michal@linuch-laptop ~]$ sudo systemctl status dbus.service
    dbus.service - D-Bus System Message Bus
    Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
    Active: active (running) since Ne 2013-01-20 17:01:34 CET
    Main PID: 2057 (dbus-daemon)
    CGroup: name=systemd:/system/dbus.service
    └─2057 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
    led 20 17:01:34 linuch-laptop systemd[1]: Starting D-Bus System Message Bus...
    led 20 17:01:34 linuch-laptop systemd[1]: Started D-Bus System Message Bus.
    First time Wicd is started after reboot:
    2013/01/20 16:56:42 :: ---------------------------
    2013/01/20 16:56:42 :: wicd initializing...
    2013/01/20 16:56:42 :: ---------------------------
    2013/01/20 16:56:42 :: wicd is version 1.7.2.4 768
    2013/01/20 16:56:42 :: did not find backend in configuration, setting default external
    2013/01/20 16:56:42 :: setting backend to external
    2013/01/20 16:56:42 :: trying to load backend external
    2013/01/20 16:56:42 :: successfully loaded backend external
    2013/01/20 16:56:42 :: trying to load backend external
    2013/01/20 16:56:42 :: successfully loaded backend external
    2013/01/20 16:56:42 :: Automatically detected wireless interface wlan0
    2013/01/20 16:56:42 :: did not find wireless_interface in configuration, setting default wlan0
    2013/01/20 16:56:42 :: setting wireless interface wlan0
    2013/01/20 16:56:42 :: Couldn't detect a wired interface.
    2013/01/20 16:56:42 :: did not find wired_interface in configuration, setting default None
    2013/01/20 16:56:42 :: setting wired interface None
    2013/01/20 16:56:42 :: did not find wpa_driver in configuration, setting default wext
    2013/01/20 16:56:42 :: setting wpa driver wext
    2013/01/20 16:56:42 :: did not find always_show_wired_interface in configuration, setting default False
    2013/01/20 16:56:42 :: did not find use_global_dns in configuration, setting default False
    2013/01/20 16:56:42 :: setting use global dns to False
    2013/01/20 16:56:42 :: did not find global_dns_1 in configuration, setting default None
    2013/01/20 16:56:42 :: did not find global_dns_2 in configuration, setting default None
    2013/01/20 16:56:42 :: did not find global_dns_3 in configuration, setting default None
    2013/01/20 16:56:42 :: did not find global_dns_dom in configuration, setting default None
    2013/01/20 16:56:42 :: did not find global_search_dom in configuration, setting default None
    2013/01/20 16:56:42 :: setting global dns
    2013/01/20 16:56:42 :: global dns servers are None None None
    2013/01/20 16:56:42 :: domain is None
    2013/01/20 16:56:42 :: search domain is None
    2013/01/20 16:56:42 :: did not find auto_reconnect in configuration, setting default True
    2013/01/20 16:56:42 :: setting automatically reconnect when connection drops True
    2013/01/20 16:56:42 :: did not find debug_mode in configuration, setting default False
    2013/01/20 16:56:42 :: did not find wired_connect_mode in configuration, setting default 1
    2013/01/20 16:56:42 :: did not find signal_display_type in configuration, setting default 0
    2013/01/20 16:56:42 :: did not find should_verify_ap in configuration, setting default 1
    2013/01/20 16:56:42 :: did not find dhcp_client in configuration, setting default 0
    2013/01/20 16:56:42 :: Setting dhcp client to 0
    2013/01/20 16:56:42 :: did not find link_detect_tool in configuration, setting default 0
    2013/01/20 16:56:42 :: did not find flush_tool in configuration, setting default 0
    2013/01/20 16:56:42 :: did not find sudo_app in configuration, setting default 0
    2013/01/20 16:56:42 :: did not find prefer_wired in configuration, setting default False
    2013/01/20 16:56:42 :: did not find show_never_connect in configuration, setting default True
    2013/01/20 16:56:42 :: Wireless configuration file not found, creating...
    2013/01/20 16:56:42 :: Wired configuration file not found, creating a default...
    2013/01/20 16:56:42 :: Creating wired profile for wired-default
    2013/01/20 16:56:42 :: dhclient.conf.template not found, copying...
    2013/01/20 16:56:42 :: chmoding configuration files 0600...
    2013/01/20 16:56:42 :: chowning configuration files root:root...
    2013/01/20 16:56:42 :: Using wireless interface...wlan0
    2013/01/20 16:56:42 :: Using wired interface...
    2013/01/20 16:56:47 :: Autoconnecting...
    2013/01/20 16:56:47 :: No wired connection present, attempting to autoconnect to wireless network
    2013/01/20 16:56:48 :: hidden
    2013/01/20 16:56:48 :: Unable to autoconnect, you'll have to manually connect
    2013/01/20 16:56:52 :: Autoconnecting...
    2013/01/20 16:56:52 :: No wired connection present, attempting to autoconnect to wireless network
    2013/01/20 16:56:53 :: hidden
    2013/01/20 16:56:53 :: Unable to autoconnect, you'll have to manually connect
    2013/01/20 16:56:57 :: Autoconnecting...
    2013/01/20 16:56:57 :: No wired connection present, attempting to autoconnect to wireless network
    2013/01/20 16:56:58 :: hidden
    2013/01/20 16:56:58 :: Unable to autoconnect, you'll have to manually connect
    2013/01/20 16:57:02 :: Autoconnecting...
    2013/01/20 16:57:02 :: No wired connection present, attempting to autoconnect to wireless network
    2013/01/20 16:57:03 :: hidden
    2013/01/20 16:57:03 :: Unable to autoconnect, you'll have to manually connect
    2013/01/20 16:57:05 :: hidden
    I have tried to completly remove wicd from my system, but without success.
    Last time I have been bitten by this, I have reinstalled my Arch - now I would like to avoid it, if possible.
    Thank you in advance.
    Michal Kvacek
    Last edited by michalkvacek (2013-01-20 15:23:26)

    Hi. I've been getting this error too, and saw your post. So I looked at the wicd wiki page...
    Have a look at this:
    https://wiki.archlinux.org/index.php/Wi … or_message

  • [Solved] Move system out of LVM DBus problems

    Hi,
    Earlier was using LVM and Arch age on Vol0/archlinux, today I moved the system out of LVM, then system now is on sda1, for move I do this (I can't remember the correct order but I thinks that's it):
    1. copied system using "rsync -ah --progress" ignoring sys,dev,run,mnt,proc
    2. configured /etc/fstab accordly:
    /dev/sda1 / btrfs rw,relatime,space_cache,compress=lzo 0 1
    3. from a chroot installed grub (no error reported), i.e.:
    grub-install --recheck /dev/sda
    4. booted in the system
    all are working well, except some services can't start at boot: dnsmasq and after login in console systemd-logind fail to start at first try (automatically) after it start normally and is working.
    another thing is that LightDM won't start, the complete output:
    [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
    [+0.00s] DEBUG: Starting Light Display Manager 1.6.0, UID=0 PID=3230
    [+0.00s] DEBUG: Loaded configuration from /etc/lightdm/lightdm.conf
    [+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
    [+0.00s] DEBUG: Using Xephyr for X servers
    [+0.00s] DEBUG: Registered seat module xlocal
    [+0.00s] DEBUG: Registered seat module xremote
    [+0.01s] DEBUG: Adding default seat
    [+0.01s] DEBUG: Starting seat
    [+0.01s] DEBUG: Starting new display for greeter
    [+0.01s] DEBUG: Starting local X display
    [+0.01s] DEBUG: Could not run plymouth --ping: Failed to execute child process "plymouth" (No such file or directory)
    [+0.01s] DEBUG: Using VT 7
    [+0.01s] DEBUG: Logging to /var/log/lightdm/x-2.log
    [+0.01s] DEBUG: Can't launch X server Xephyr, not found in path
    [+0.01s] DEBUG: X server stopped
    [+0.01s] DEBUG: Releasing VT 7
    [+0.01s] DEBUG: Display server stopped
    [+0.01s] DEBUG: Stopping display
    [+0.01s] DEBUG: Stopping seat, failed to start a display
    [+0.01s] DEBUG: Stopping seat
    [+0.01s] DEBUG: Seat stopped
    Failed to get D-Bus connection
    tried:
    1. re-installing lightdm
    2. regenerating initramfs
    3. removing and re-installing dbus and systemd (i.e.: pacman -Rnsdd systemd dbus; pacman -S systemd dbus)
    nothing of these things solves, So I think that it isn't a LightDM issue.
    dbus-monitor looks correct!
    Last edited by hotvic (2013-07-26 03:06:54)

    Is X server Xephyr in your path?
    By the way, you would be better advised to use the rsync flags mentioned in the wiki page for full system backup with rsync to make sure that you do not lose information. -a will get most stuff but not everything. For example, ping may not work and I think you will lose ACLs as well as capabilities. I doubt this is why it can't find the X server, though.

  • HAL and automounter problem

    Hello i cannot access my USB external disk although i have done all the the changes in the Policykit.conf
    Here it is
    <config version="0.1">
                   <match action="org.freedesktop.hal.storage.*">
                           <return result="yes"/>
                   </match>
                   <match action="hal-storage-mount-fixed-extra-options"> <!-- for internal devices mounted with extra op$
                           <return result="yes" />
                   </match>
                   <match action="hal-storage-mount-removable-extra-options"> <!-- for external devices mounted with extr$
                           <return result="yes" />
                   </match>
    </config>
    i dont know whta went wrong ???

    Have you seen this: http://bbs.archlinux.org/viewtopic.php?id=66402
    There are tonnes of automount posts; if this one doesn't help a search of the forums will yield many results.

  • Dbus/hal/gnome-volume-manager problem

    I've got hal and dbus running but it doesnt even seem that gnome-volume-manager is started. I added it to my gnome session but that didnt seem to do the trick. I'm trying to be able to just plug in my usb key and ipod and have them automount. It works if I restart hal or run gnome-volume-manager from the command line but then work work again unless I restart that stuff again. Here is a cut from my fstab:
    /dev/sda1 /mnt/usb auto user,noauto 0 0
    /dev/sda2 /mnt/ipod auto user,noauto 0 0

    Hi lhoerste,
    I had this problem with automount as well. The way I fixed it was adding
    dbus hal to daemons line in /etc/rc.conf. You probably did this already.
    Next, when you are in the gnome desktop, stick in a cd. Nothing happens right?
    Now go to preferences=>removable drives and media (I think this is what it is called. I'm not sitting infront of my computer at the moment). Then make sure that the checkboxes pertaining to "mount automatically" are checked.
    Close window.
    Now your cd should automount and appear on the desktop. Eject the cd by right clicking on the icon and choosing eject.
    Now, restart and ***make sure you save settings*** before leaving.
    Get back into the gnome desktop and plug your cd back in. It should automount now.
    This is how I got automount to work for me.

Maybe you are looking for

  • HTML5 development in Eclipse

    Hi all, I'm developing HCP HTML5 applications based on UI5. While the RDE looks really great, I'd still like to use the good old Eclipse to launch my project locally. To do so, I've created an HTML5 application from the cockpit, generated a sample UI

  • Barcoded forms using Adobe Reader

    Hi, As previous discussion started by me, we have developed a Barcoded form for our work process. It's use to be succesful filling & editing barcoded form with Adobe Acrobat reader 9.3 after we license the form in Livecycle. But just know the reader

  • Please help with (long) error message upon launch of final cut 7

    Hello. I have just installed final cut 7 and when opening, it asks for serial number/name etc...I enter that information then it crashes giving this error message (sorry if this is so long, but wasn't sure what to put) Process: Final Cut Pro [215] Pa

  • Can't apply bold, italic, etc. in Mail after 10.4.7

    After going through some new font follies, running through a MS Office update I'd been putting off, and then running the Tiger 10.4.7 Combo update (PPC), my Mail headers were all funky with a lot of extra spacing. Thanks to a thread here from last ye

  • Cmd + z

    Drücke ich cmd+z  um den letzten Schritt rückgängig zu machen, erhalte ich ein anderes Layout. DER LETZTE SCHRITT KANN NICHT RÜCKGÄNGIG GEMACHT WERDEN. iMac 27", Bridge CS6. Fehler besteht von Anfang an (seit etwa 1,5 Jahren). Aktuell Software update