Startup error messages for Pulseaudio initialization, dbus problem?

Alp · 2012-09-24 07:55:24

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)

nTia89 · 2012-09-24 08:02:50

i think that this line is explanatory:

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.

Alp · 2012-09-24 08:04:55

Here is the output:

$ systemctl status pulseaudio.service
pulseaudio.service
	  Loaded: error (Reason: No such file or directory)
	  Active: inactive (dead)

The strange thing is: When i play music and open pavucontrol, i see the output meters moving, so i am definitely having pulseaudio running. I am confused right now.

nTia89 · 2012-09-24 08:05:57

post your rc.conf

Alp · 2012-09-24 08:11:55

#
# /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=

nTia89 · 2012-09-24 08:14:41

try to remove pulseaudio from the DAEMONS array and check if the errors are fixed

Alp · 2012-09-24 17:04:38

I switched hal and dbus in the DAEMONS array and it seems to work.

nTia89 · 2012-09-24 17:07:05

Alp wrote:

I switched hal and dbus in the DAEMONS array and it seems to work.

off-topic question: why do you still have HAL?

Alp · 2012-09-24 17:17:56

I wrote it there because it is listed in the beginner's installation guide in the official wiki. Isn't it needed anymore?

nTia89 · 2012-09-24 17:21:45

no, it's deprecated and fully substitute by udev

do you have HAL installed in your system?

Alp · 2012-09-24 22:40:10

Now, i am really confused. No, i doesn't seem to have hal installed. Which is good i guess. I threw it out of my rc.conf.

Last edited by Alp (2012-09-24 22:40:28)

nTia89 · 2012-09-25 08:15:47

pacman -Qi

, gives you the full list+details of installed packages

pacman -Qi | grep hal -A 10 -B 10

, extracts from the list the lines which contain the "hal" word

Alp · 2012-09-25 17:13:47

Nope, it's not installed.

Arch Linux

#1 2012-09-24 07:55:24

Startup error messages for Pulseaudio initialization, dbus problem?

#2 2012-09-24 08:02:50

Re: Startup error messages for Pulseaudio initialization, dbus problem?

#3 2012-09-24 08:04:55

Re: Startup error messages for Pulseaudio initialization, dbus problem?

#4 2012-09-24 08:05:57

Re: Startup error messages for Pulseaudio initialization, dbus problem?

#5 2012-09-24 08:11:55

Re: Startup error messages for Pulseaudio initialization, dbus problem?

#6 2012-09-24 08:14:41

Re: Startup error messages for Pulseaudio initialization, dbus problem?

#7 2012-09-24 17:04:38

Re: Startup error messages for Pulseaudio initialization, dbus problem?

#8 2012-09-24 17:07:05

Re: Startup error messages for Pulseaudio initialization, dbus problem?

#9 2012-09-24 17:17:56

Re: Startup error messages for Pulseaudio initialization, dbus problem?

#10 2012-09-24 17:21:45

Re: Startup error messages for Pulseaudio initialization, dbus problem?

#11 2012-09-24 22:40:10

Re: Startup error messages for Pulseaudio initialization, dbus problem?

#12 2012-09-25 08:15:47

Re: Startup error messages for Pulseaudio initialization, dbus problem?

#13 2012-09-25 17:13:47

Re: Startup error messages for Pulseaudio initialization, dbus problem?

Board footer