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?
Similar Messages
-
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= -
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: 2When 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 -
(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) -
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
-
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) -
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
wabiHi
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 -
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. -
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 -
Problem with wlan sticks module, not able to write to disk any more
Hello everybody,
when I booted my PC today, a strange and some sort of severe problem occurred concerning my wlan stick(s) that I think, I'm not able to solve without your help. I searched for a solution but it didn't seem that somebody else has had a similar problem before.
Here is the description:
I have two wlan sticks (but I do not use both of them nor are they both plugged in at the same time), and both happen to malfunction since today. My "main" stick (used most of the time) is a BigTec Wireless 11N Adapter with a Realtek chipset. My second one (only used to solve problems with the other stick) is a Fritz! WLAN USB Stick (to be used with ndiswrapper).
After bootup, which makes no problems at all, my "main" wlan stick is not able to connect to the network. When I run wicd-curses (I use wicd as network manager), the virtual terminal freezes (when I use urxvt under openbox to run wicd-curses, only the window freezes). After one minute, a message appears that says something about a dbus problem but I am not able to read it because of the screen clears. Then I'm able to use the terminal again, but (and this is the very, very strange about this) when I run any program that tries to write on my disk it stucks, so I can't cancel it with ctrl-c nor can I kill the process. Wicd-curses, ifconfig or iwconfig also crash after entering the command and show the same behavior. At this point, my wlan stick does not show any sign of being plugged in (normally it blinks...).
My second stick makes the computer crash: After a few moments a stacktrace is shown (like when a kernel panic occurs), saying something about "stack being overrun". But I can't find the message in the log files so it is difficult to post it.
When I tried to figure out a solution, I saw in pacman.log, that yesterday udev and hwdetect were updated... But also downgrading all the packages that were updated yesterday did not solve the problem!
I'll post now the last lines of a few logs here (but nothing concerning the ndiswrapper stick, else it would be too disturbing), I hope they help you at helping me!
everything.log
Jan 23 15:25:26 localhost dhcpcd[835]: dhcpcd not running
Jan 23 15:25:27 localhost kernel: [ 21.415035] r8712u: Loading firmware from "rtlwifi/rtl8712u.bin"
Jan 23 15:25:27 localhost kernel: [ 22.063785] r8712u: 1 RCR=0x153f00e
Jan 23 15:25:27 localhost kernel: [ 22.064534] r8712u: 2 RCR=0x553f00e
Jan 23 15:25:27 localhost kernel: [ 22.170765] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jan 23 15:25:27 localhost dhcpcd[847]: dhcpcd not running
Jan 23 15:25:28 localhost kernel: [ 22.410354] e1000e 0000:00:19.0: irq 41 for MSI/MSI-X
Jan 23 15:25:28 localhost kernel: [ 22.463386] e1000e 0000:00:19.0: irq 41 for MSI/MSI-X
Jan 23 15:25:28 localhost kernel: [ 22.463902] ADDRCONF(NETDEV_UP): eth0: link is not ready
Jan 23 15:25:28 localhost dhcpcd[854]: dhcpcd not running
Jan 23 15:25:28 localhost kernel: [ 22.735037] r8712u: Loading firmware from "rtlwifi/rtl8712u.bin"
Jan 23 15:25:29 localhost kernel: [ 23.383789] r8712u: 1 RCR=0x153f00e
Jan 23 15:25:29 localhost kernel: [ 23.384535] r8712u: 2 RCR=0x553f00e
Jan 23 15:25:29 localhost kernel: [ 23.490763] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jan 23 15:26:11 localhost dhcpcd[1382]: dhcpcd not running
Jan 23 15:26:12 localhost kernel: [ 66.495307] r8712u: Loading firmware from "rtlwifi/rtl8712u.bin" # then I hard reset because of the freeze
errors.log
Jan 23 15:00:01 localhost /USR/SBIN/CROND[5597]: (CRON) EXEC FAILED (/usr/sbin/sendmail): No such file or directory
Jan 23 15:20:01 localhost /USR/SBIN/CROND[6215]: (CRON) EXEC FAILED (/usr/sbin/sendmail): No such file or directory
Jan 23 15:25:26 localhost dhcpcd[835]: dhcpcd not running
Jan 23 15:25:27 localhost dhcpcd[847]: dhcpcd not running
Jan 23 15:25:28 localhost dhcpcd[854]: dhcpcd not running
Jan 23 15:26:11 localhost dhcpcd[1382]: dhcpcd not running # then I hard reset because of the freeze
daemon.log
Jan 23 15:25:15 localhost [ 0.864888] udevd[48]: starting version 175
Jan 23 15:25:15 localhost [ 4.116488] udevd[235]: starting version 178
Jan 23 15:25:26 localhost dhcpcd[835]: dhcpcd not running
Jan 23 15:25:27 localhost dhcpcd[847]: dhcpcd not running
Jan 23 15:25:28 localhost dhcpcd[854]: dhcpcd not running
Jan 23 15:26:11 localhost dhcpcd[1382]: dhcpcd not running # then I hard reset because of the freeze
I hope you can help me and thank you for trying
hoeffl
P.S.: Excuse all the mistakes I made because of being new here, please!This seems to be a problem with r8712u on all 3.2.x and 3.3-rc kernels on all distros. I've had it for weeks on Gentoo, Arch, and several other distros.
If you are running a 3.2.x kernel, this is almost definitely the problem. All 3.1 kernels don't do this.
I posted a temporary work-around on the Arch bugzilla, and Larry Finger (kernel dev with wireless) is currently working on it (a patch).
In the meantime, If you compile your own kernels, you can get 3.2.x's to work normally- see my comment here for more details. https://bugs.archlinux.org/task/27996
Top of page doesn't say r8712u, but it's the same problem, and after the first 2-3 comments it deals with r8712u specifically.
There is also info on the Gentoo forum 3.2 kernel quirks thread, towards the bottom of Page 1: http://forums.gentoo.org/viewtopic-t-901702.html
Last edited by wrc1944 (2012-02-03 07:45:32) -
[solved] DBus permissions? polkit? a lot of things do not work.
Hello,
here is the problem.
i made some updates.
after rebooting i started to get problems.
I use KDE 4.9.3
first, NetworkManager was not working. i realize that there were some problems with permissions and NW.
in some way i was able to get it work and that's why i'm able to write here.
but: wireless is not working at all.
the error says: "no session found for uid 1000 (unknown)"
i cannot mount any kind of devices. the error says: "permission denided"
if i try to change the clock setting, kde is no more asking me the root password. indeed, the change has not effect. no error displayed
i really don't know where i could search for a solution.
is a DBUS problem? it seems so.
it's a problem of polkit? i found out that something happens in the last updates. i think that everything migrated to systemd and also there was something about polkit or policykit.
can some of you give me some suggestions?
do you have some ideas why i got this problems?
thanks in advance
Last edited by darkman (2012-11-22 22:09:36)yes.
thanks.
that was the problem.
i followed the wiki and i found the solution. everything is solved.
thanks.
btw, i was thinking that everything was in auto-magic because
1) i'm a newbie here in arch
2) i found that the package was installed and, noticied that pacman configure the packages for you i convince myself that it did also for systemd.
3) i read the news but nothing was talking about the fact that "you have to follow the wiki". so, i was wrong.
thanks. -
[solved] nm-applet does not show up in Gnome panel
Hi all,
I installed networkmanager, network-manager-applet and dbus this afternoon. As well as a fresh install of Gnome. This is all done on my laptop, which my wife wants to use now and then. I always set up the network CLI, but now I will need a nice flashy applet in the Gnome panel.
I managed to run the network-connection-editor as root, and got the network up.
I had some dbus problems when I tried launching nm-applet, but fixed it with a dbus-hack I found in some other thread. But when I now launch nm-applet, it says that there allready is an instance running of nm-applet.
I guess it should show up in the panel, if it is. But I don't see anything there... Do you have any ideas of what I forgot to install/configure/check.
Thanks,
jocom
Last edited by jocom (2011-02-19 19:46:58)There have been a couple similar posts recently. I'm not using Gnome anymore or networkmanager, so I don't know if there's a problem with it or not. If I remember correctly I had to install gnome-panel-bonobo, and I believe python-notify and gksu too. You can do a search on the wiki for networkmanager, there is a page for it that explains the configuration changes you'll need to make. Hope it helps.
Last edited by stlarch (2011-02-19 18:16:26) -
I've upgraded glibsc, filesystem and migrated to systemd. I can't load KDE after it. I didn't find any info about KDE and systemd, but seems systed is the problem. KDM and initializations works without troubles, but kde plasma and desktop doesn't show up. Black screen or wallpaper and cursor is visible. Some of my daemon.log:
Dec 27 11:40:17 localhost dbus[195]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Dec 27 11:40:17 localhost systemd[1]: Starting Authorization Manager...
Dec 27 11:40:17 localhost systemd[1]: upower.service: main process exited, code=dumped, status=5/TRAP
Dec 27 11:40:17 localhost systemd[1]: Unit upower.service entered failed state
Dec 27 11:40:17 localhost systemd[1]: polkit.service: main process exited, code=exited, status=1/FAILURE
Dec 27 11:40:17 localhost systemd[1]: Failed to start Authorization Manager.
Dec 27 11:40:17 localhost systemd[1]: Unit polkit.service entered failed state
Dec 27 11:40:42 localhost dbus-daemon[195]: dbus[195]: [system] Failed to activate service 'org.freedesktop.PolicyKit1': timed out
Dec 27 11:40:42 localhost dbus[195]: [system] Failed to activate service 'org.freedesktop.PolicyKit1': timed out
Dec 27 11:40:42 localhost udisks-daemon[664]: (udisks-daemon:664): udisks-daemon-CRITICAL **: error getting authority reference: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freedesktop.PolicyKit1 timed out
Dec 27 11:40:42 localhost systemd[1]: udisks.service: main process exited, code=exited, status=1/FAILURE
Dec 27 11:40:42 localhost systemd[1]: Unit udisks.service entered failed state
Probably I need to show some other log? I'm not sure which exactly.I've dived into systemd and had some progress. One of problems was with conflict between udisk2 and udisk (both were loaded). As far as I understand KDE doesn't support udisk2, so I did systemctl disable udisk2.service. Now there are no failed units:
UNIT LOAD ACTIVE SUB DESCRIPTION
proc-sys...t_misc.automount loaded active running Arbitrary Executable File Fo
sys-devi...-net-eth0.device loaded active plugged /sys/devices/pci0000:00/0000
sys-devi...-sda-sda1.device loaded active plugged ST3120026A
sys-devi...-sda-sda2.device loaded active plugged ST3120026A
sys-devi...-sda-sda3.device loaded active plugged ST3120026A
sys-devi...block-sda.device loaded active plugged ST3120026A
sys-devi...block-sr0.device loaded active plugged HL-DT-ST_DVDRAM_GSA-4163B
sys-devi...und-card0.device loaded active plugged /sys/devices/pci0000:00/0000
sys-devi...block-fd0.device loaded active plugged /sys/devices/platform/floppy
sys-devi...tty-ttyS2.device loaded active plugged /sys/devices/platform/serial
sys-devi...tty-ttyS3.device loaded active plugged /sys/devices/platform/serial
sys-devi...tty-ttyS0.device loaded active plugged /sys/devices/pnp0/00:09/tty/
sys-devi...tty-ttyS1.device loaded active plugged /sys/devices/pnp0/00:0a/tty/
sys-module-fuse.device loaded active plugged /sys/module/fuse
sys-subs...ices-eth0.device loaded active plugged /sys/subsystem/net/devices/e
-.mount loaded active mounted /
dev-hugepages.mount loaded active mounted Huge Pages File System
dev-mqueue.mount loaded active mounted POSIX Message Queue File Sys
home.mount loaded active mounted /home
proc-sys...infmt_misc.mount loaded active mounted Arbitrary Executable File Fo
sys-kernel-debug.mount loaded active mounted Debug File System
tmp.mount loaded active mounted Temporary Directory
systemd-...ord-console.path loaded active waiting Dispatch Password Requests t
systemd-...ssword-wall.path loaded active waiting Forward Password Requests to
colord.service loaded active running Manage, Install and Generate
console-kit-daemon.service loaded active running Console Manager
console-...em-start.service loaded active exited Console System Startup Loggi
crond.service loaded active running LEGACY unit for "crond" rc s
cups.service loaded active running CUPS Printing Service
dbus.service loaded active running D-Bus System Message Bus
[email protected] loaded active running Getty on tty1
kdm.service loaded active running K Display Manager
network.service loaded active running LEGACY unit for "network" rc
openntpd.service loaded active running OpenNTP Daemon
polkit.service loaded active running Authorization Manager
rc-local.service loaded active exited /etc/rc.local Compatibility
samba.service loaded active running LEGACY unit for "samba" rc s
syslog-ng.service loaded active running System Logger Daemon
systemd-binfmt.service loaded active exited Set Up Additional Binary For
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running Login Service
systemd-remount-fs.service loaded active exited Remount Root and Kernel File
systemd-sysctl.service loaded active exited Apply Kernel Variables
systemd-...es-setup.service loaded active exited Recreate Volatile Files and
systemd-...-trigger.service loaded active exited udev Coldplug all Devices
systemd-udevd.service loaded active running udev Kernel Device Manager
systemd-...sessions.service loaded active exited Permit User Sessions
systemd-...le-setup.service loaded active exited Setup Virtual Console
udisks.service loaded active running UDisks
udisks2.service loaded active running Disk Manager
upower.service loaded active running Daemon for power management
dbus.socket loaded active running D-Bus System Message Bus Soc
dmeventd.socket loaded active listening Device-mapper event daemon F
lvmetad.socket loaded active listening LVM2 metadata daemon socket
syslog.socket loaded active running Syslog Socket
systemd-initctl.socket loaded active listening /dev/initctl Compatibility N
systemd-journald.socket loaded active running Journal Socket
systemd-shutdownd.socket loaded active listening Delayed Shutdown Socket
systemd-...d-control.socket loaded active listening udev Control Socket
systemd-udevd-kernel.socket loaded active running udev Kernel Socket
dev-sda2.swap loaded active active /dev/sda2
arch-daemons.target loaded active active Arch Daemons
basic.target loaded active active Basic System
cryptsetup.target loaded active active Encrypted Volumes
getty.target loaded active active Login Prompts
graphical.target loaded active active Graphical Interface
local-fs-pre.target loaded active active Local File Systems (Pre)
local-fs.target loaded active active Local File Systems
multi-user.target loaded active active Multi-User
remote-fs.target loaded active active Remote File Systems
sockets.target loaded active active Sockets
sound.target loaded active active Sound Card
swap.target loaded active active Swap
sysinit.target loaded active active System Initialization
syslog.target loaded active active Syslog
systemd-...iles-clean.timer loaded active waiting Daily Cleanup of Temporary D
But it's still not working. Seems now it's dbus problem or so. What do I need to run KDE? How can I figure it out? Any wiki? suggestions? -
Upgrade to networkmanager breaks networkmanager applets
The newest version of network manager breaks the applets - neither nm-applet nor knetworkmanager can connect via dbus. dhcdbd neither for that matter. What gives? I can' t diagnose it any further than that it is a dbus problem since I don' t know anything about dbus - comething which I am busy remedying now...
parkash wrote:
Ok wait, I added myself to the network group.. Yes, I can now "use" network manager. But it doesn't find any wireless networks! It doesn't even know (I presume) that I have a wireless card!
Any help will be appreciated.
Once I added myself to the network group everything worked fine.
What is the output of iwconfig? Does it list your wireless card? If not, then check if the module is loaded for your card. If you use nsidwrapper, check to see what ndiswrapper -l gives you. You'll have to give a little more info than what you gave. What card/chipset do you have for starters? Post the output of lspci.
Maybe you are looking for
-
hi, i am getting the following error while downloading a material group from ECC 5.0-> CRM 5.0 : "Category for product hierarchy 1010AV does not exist" i had carried out the download of DNL_CUST_PROD1 and i've checked this material group is present
-
How do I disable Facebook from posting all my contacts birthdays in calendar?
Recently updated to iOS6 on my iPhone 4S. Now my calendar is filled with the birthdays of all my Facebook friends. Is there a way to disable this feature? Thanks!
-
I don't have a touchsmart PC, BUT . . .
I have seen the commercials on TV and the software that is demonstrated that shows the actor moving the pictures in an arc on the screen and then selecting an image and manipulating it, LOOKS ABSOLUTELY WiiiiiiLD !!! What is the software called and
-
Hello all- Is it possible to generate a series of images into a Podcast where the user drives the image flow? For example, let's say that I have 10 jpegs or PDFs or whatever works best. I'd like to allow someone to download onto iPod and choose when
-
We have recently purchased a Cisco 1310 outdoor device. I have a couple of questions you may help me with please. We have configured the device to act as an Access Point to provide VOIP (7920), however the range is not very good to provide recommende