Package: apt
Version: 0.9.16.1
Severity: minor
I never have system-wide D-Bus daemon running; but sometimes I do have a
per-session D-Bus daemon running. When this is the case, this check
succeeds:
if which dbus-send >/dev/null && pidof dbus-daemon >/dev/null; then
...and the cron script proceeds to send stuff to the system-wide message
bus, which of course fails:
Failed to open connection to "system" message bus: Failed to connect to socket
/var/run/dbus/system_bus_socket: No such file or directory
Please improve the way availability of D-Bus daemon is detected.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'experimental')
Architecture: i386 (x86_64)
Foreign Architectures: amd64
Kernel: Linux 3.12-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages apt depends on:
ii debian-archive-keyring 2012.4
ii gnupg 1.4.16-1.1
ii libapt-pkg4.12 0.9.16.1
ii libc6 2.18-4
ii libgcc1 1:4.9-20140303-1
ii libstdc++6 4.9-20140303-1
Versions of packages apt suggests:
pn apt-doc <none>
pn aptitude | synaptic | wajig <none>
ii dpkg-dev 1.17.6
ii python-apt 0.9.3.4
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
