[arch-general] Broken DBus
Hello, DBus broke for me after last upgrade [0]. I'm using testing repository and have: dbus 1.4.20-1 dbus-core 1.4.20-2 dbus-glib 0.98-1 dbus-python 1.0.0-1 but disabling it and downgrading (via pacman -Syuu) to: dbus 1.4.16-1 dbus-core 1.4.16-1 dbus-glib 0.98-1 dbus-python 0.84.0-1 doesn't fix problem (not entirely at least). On testing Gnome starts in fallback mode, chromium and wicd-curses says: Failed to call method: org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1 After downgrading, wicd-curses (which uses dbus-python) works fine, but other things are still broken. dbus-daemon is present in process list... What can be wrong, where should I look? [0] List of upgraded packages: http://pastebin.com/CYbTTaUQ Only: [2012-04-11 21:59] upgraded dbus-core (1.4.20-1 -> 1.4.20-2) looks suspicious to me, but downgrading only dbus-core to 1.4.20-1 doesn't change anything. Cheers, Kacper Żuk PS Sorry for my grammar...
Hello, I had a problem with dbus shortly. The error messagtes were of the kind "file not found: /var/dbus/system_bus_socket" However, I use systemd (an init replacement using parallel and on-demand loading of system services) and have no idea whether this is somehow related. The issue is that the socket /var/run/dbus/system_bus_socket isn't created. On a systemd-System this task is done by the unit dbus.socket and my computer runs flawlessy after manually calling 'sudo systemctl restart dbus.socket' I donÄt know whether this is of any value to you but who knows? Good luck!
On 15 April 2012 17:22, mlell08 <mlell08@googlemail.com> wrote:
Hello,
I had a problem with dbus shortly. The error messagtes were of the kind "file not found: /var/dbus/system_bus_socket" However, I use systemd (an init replacement using parallel and on-demand loading of system services) and have no idea whether this is somehow related. The issue is that the socket /var/run/dbus/system_bus_socket isn't created. On a systemd-System this task is done by the unit dbus.socket and my computer runs flawlessy after manually calling 'sudo systemctl restart dbus.socket'
I donÄt know whether this is of any value to you but who knows?
Good luck!
Are you using [testing] ? Could you please add the output of $pacman -Q systemd systemd-arch-units initscripts-systemd ?
Von: Kacper Żuk Fri, 13 Apr 2012 22:17:32 +0200
Hello, DBus broke for me after last upgrade [0]. I'm using testing repository and have: dbus 1.4.20-1 dbus-core 1.4.20-2 dbus-glib 0.98-1 dbus-python 1.0.0-1
but disabling it and downgrading (via pacman -Syuu) to: dbus 1.4.16-1 dbus-core 1.4.16-1 dbus-glib 0.98-1 dbus-python 0.84.0-1
doesn't fix problem (not entirely at least). On testing Gnome starts in fallback mode, chromium and wicd-curses says: Failed to call method: org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1
After downgrading, wicd-curses (which uses dbus-python) works fine, but other things are still broken.
dbus-daemon is present in process list... What can be wrong, where should I look?
[0] List of upgraded packages: http://pastebin.com/CYbTTaUQ Only: [2012-04-11 21:59] upgraded dbus-core (1.4.20-1 -> 1.4.20-2) looks suspicious to me, but downgrading only dbus-core to 1.4.20-1 doesn't change anything.
Cheers, Kacper Żuk
PS Sorry for my grammar...
On 15.04.2012 17:28, Alexandre Ferrando wrote:
On 15 April 2012 17:22, mlell08 <mlell08@googlemail.com> wrote:
Hello,
I had a problem with dbus shortly. The error messagtes were of the kind "file not found: /var/dbus/system_bus_socket" However, I use systemd (an init replacement using parallel and on-demand loading of system services) and have no idea whether this is somehow related. The issue is that the socket /var/run/dbus/system_bus_socket isn't created. On a systemd-System this task is done by the unit dbus.socket and my computer runs flawlessy after manually calling 'sudo systemctl restart dbus.socket'
I donÄt know whether this is of any value to you but who knows?
Good luck! Are you using [testing] ?
Could you please add the output of $pacman -Q systemd systemd-arch-units initscripts-systemd ?
Hello Alexandre, no, I'm not using [testing] but I have the same version of dbus and dbus-core like Kacper so I thought I'd post what I have. $pacman -Q systemd systemd-arch-units initscripts-systemd dbus dbus-core systemd 44-5 systemd-arch-units 20120410-1 initscripts-systemd 20120412-1 dbus 1.4.20-1 dbus-core 1.4.20-2 Regards! P.S. sysctl status output of dbus.service & dbus.socket: $ sudo systemctl show dbus.service Id=dbus.service Names=dbus.service Requires=dbus.socket systemd-journald.socket basic.target WantedBy=multi-user.target arch-daemons.target Conflicts=shutdown.target Before=shutdown.target multi-user.target arch-daemons.target After=syslog.target systemd-journald.socket basic.target dbus.socket TriggeredBy=dbus.socket Description=D-Bus System Message Bus LoadState=loaded ActiveState=active SubState=running FragmentPath=/usr/lib/systemd/system/dbus.service UnitFileState=static InactiveExitTimestamp=Sun, 15 Apr 2012 17:48:25 +0200 InactiveExitTimestampMonotonic=48976923 ActiveEnterTimestamp=Sun, 15 Apr 2012 17:48:26 +0200 ActiveEnterTimestampMonotonic=49431345 ActiveExitTimestamp=Sun, 15 Apr 2012 17:48:25 +0200 ActiveExitTimestampMonotonic=48908905 InactiveEnterTimestamp=Sun, 15 Apr 2012 17:48:25 +0200 InactiveEnterTimestampMonotonic=48940577 CanStart=yes CanStop=yes CanReload=yes CanIsolate=no StopWhenUnneeded=no RefuseManualStart=no RefuseManualStop=no AllowIsolate=no DefaultDependencies=yes OnFailureIsolate=no IgnoreOnIsolate=no IgnoreOnSnapshot=no DefaultControlGroup=name=systemd:/system/dbus.service ControlGroup=cpu:/system/dbus.service name=systemd:/system/dbus.service NeedDaemonReload=no JobTimeoutUSec=0 ConditionTimestamp=Sun, 15 Apr 2012 17:48:25 +0200 ConditionTimestampMonotonic=48972031 ConditionResult=yes Type=simple Restart=no NotifyAccess=none RestartUSec=100ms TimeoutUSec=1min 30s WatchdogUSec=0 WatchdogTimestampMonotonic=0 StartLimitInterval=10000000 StartLimitBurst=5 StartLimitAction=none ExecStartPre={ path=/usr/bin/dbus-uuidgen ; argv[]=/usr/bin/dbus-uuidgen --ensure ; ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status ExecStartPre={ path=/bin/rm ; argv[]=/bin/rm -f /var/run/dbus.pid ; ignore_errors=yes ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 } ExecStart={ path=/usr/bin/dbus-daemon ; argv[]=/usr/bin/dbus-daemon --system --address=systemd: --nofork --systemd-activation ; ignore_errors=no ; start_time=[n/a] ; st ExecReload={ path=/usr/bin/dbus-send ; argv[]=/usr/bin/dbus-send --print-reply --system --type=method_call --dest=org.freedesktop.DBus / org.freedesktop.DBus.ReloadConf PermissionsStartOnly=no RootDirectoryStartOnly=no RemainAfterExit=no GuessMainPID=yes MainPID=633 ControlPID=0 SysVStartPriority=-1 FsckPassNo=0 Result=success UMask=0022 [...] $ sudo systemctl show dbus.socket Id=dbus.socket Names=dbus.socket Requires=var-run.mount sysinit.target -.mount RequiredBy=console-kit-daemon.service systemd-logind.service dbus.service NetworkManager.service colord.service rtkit-daemon.service accounts-daemon.service WantedBy=sockets.target Conflicts=shutdown.target Before=console-kit-daemon.service systemd-logind.service NetworkManager.service dbus.service sockets.target shutdown.target colord.service rtkit-daemon.service accounts After=var-run.mount sysinit.target -.mount Triggers=dbus.service Description=D-Bus System Message Bus Socket LoadState=loaded ActiveState=active SubState=running FragmentPath=/usr/lib/systemd/system/dbus.socket UnitFileState=static InactiveExitTimestamp=Sun, 15 Apr 2012 17:48:25 +0200 InactiveExitTimestampMonotonic=48970409 ActiveEnterTimestamp=Sun, 15 Apr 2012 17:48:25 +0200 ActiveEnterTimestampMonotonic=48970409 ActiveExitTimestamp=Sun, 15 Apr 2012 17:48:25 +0200 ActiveExitTimestampMonotonic=48970349 InactiveEnterTimestamp=Sun, 15 Apr 2012 17:48:25 +0200 InactiveEnterTimestampMonotonic=48970349 CanStart=yes CanStop=yes CanReload=no CanIsolate=no StopWhenUnneeded=no RefuseManualStart=no RefuseManualStop=no AllowIsolate=no DefaultDependencies=yes OnFailureIsolate=no IgnoreOnIsolate=no IgnoreOnSnapshot=no DefaultControlGroup=name=systemd:/system/dbus.socket ControlGroup=cpu:/system/dbus.socket name=systemd:/system/dbus.socket NeedDaemonReload=no JobTimeoutUSec=0 ConditionTimestamp=Sun, 15 Apr 2012 17:48:25 +0200 ConditionTimestampMonotonic=48970360 ConditionResult=yes BindIPv6Only=default Backlog=128 TimeoutUSec=1min 30s ControlPID=0 DirectoryMode=0755 SocketMode=0666 [...]
W dniu 15.04.2012 17:22, mlell08 pisze:
Hello,
I had a problem with dbus shortly. The error messagtes were of the kind "file not found: /var/dbus/system_bus_socket" However, I use systemd (an init replacement using parallel and on-demand loading of system services) and have no idea whether this is somehow related.
I don't use systemd so it can't be related.
Good luck!
Thanks. I've managed to track down the problem. pacman -Qk showed missing files in consolkit package. Reinstalling consolekit fixed the issue. I have no idea how that happened though... I guess it was my fault, as always ;).
participants (3)
-
Alexandre Ferrando
-
Kacper Żuk
-
mlell08