dhcdbd must depend on dbus-1-utils (provides /usr/bin/dbus-send)

[Václav Šmilauer]

network-manager fails to obtain DHCP info if dbus-1-utils packages is not installed, because it calls dhcdbd, which in turn calls dhclient with appropriate options, talking to dbus from a shell script by dbus-send command. This command is provided by dbus-1-utils, but dhcdbd does not depend on it. If it is not installed, dhclient works as per normal, but the information from DHCP server is not send through dbus. The result is that dhcdbd does not work at all.

With dbus-1-utils installed, all works fine. I Wonder if I am the only person having this problem??? Some transcripts from terminal follow.

Regards, VS

---
NetworkManager without dbus-1-utils installed:

falx:~# NetworkManager --no-daemon
NetworkManager: <information> starting...
NetworkManager: <information> eth0: Driver support level for '8139too' is fully-supported
NetworkManager: <information> Will activate wired connection 'eth0' because it now has a link.
NetworkManager: <information> Device eth0 activation scheduled...
NetworkManager: <information> nm_device_new(): waiting for device's worker thread to start
NetworkManager: <information> nm_device_new(): device's worker thread started, continuing.
NetworkManager: <information> Now managing wired device 'eth0'.
NetworkManager: <information> Deactivating device eth0.
NetworkManager: <information> named started with pid 6084
NetworkManager: <information> Updating allowed wireless network lists.
NetworkManager: <information> Activation (eth0) started...
NetworkManager: <information> Activation (eth0) Stage 1 (Device Prepare) scheduled...
NetworkManager: <information> Activation (eth0) Stage 1 (Device Prepare) started...
NetworkManager: <information> Activation (eth0) Stage 2 (Device Configure) scheduled...
NetworkManager: <information> Activation (eth0) Stage 1 (Device Prepare) complete.
NetworkManager: <information> Activation (eth0) Stage 2 (Device Configure) starting...
NetworkManager: <information> Activation (eth0/wired) Stage 2 (Device Configure) successful.
NetworkManager: <information> Activation (eth0) Stage 3 (IP Configure Start) scheduled.
NetworkManager: <information> Activation (eth0) Stage 2 (Device Configure) complete.
NetworkManager: <information> Activation (eth0) Stage 3 (IP Configure Start) started...
NetworkManager: <information> Old device 'eth0' activating, won't change.
NetworkManager: <information> Activation (eth0) Beginning DHCP transaction.
NetworkManager: <information> DHCP daemon state now 12 for interface eth0
NetworkManager: <information> Activation (eth0) Stage 3 (IP Configure Start) complete.
NetworkManager: <information> Device 'eth0' DHCP transaction took too long (>25s), stopping it.
NetworkManager: <information> Activation (eth0) Stage 4 (IP Configure Timeout) scheduled...
NetworkManager: <information> Activation (eth0) Stage 4 (IP Configure Timeout) started...
NetworkManager: <information> No DHCP reply received. Automatically obtaining IP via Zeroconf.
[...]

---

NetworkManager calls dhclient with the following commandline (taken from /proc/<PID>/cmdline):

falx:/# /sbin/dhclient -1 -lf /var/lib/dhcp3/dhclient.eth0.leases -pf /var/run/dhclient.eth0.pid -e dhc_dbus=31 -x -d eth0
There is already a pid file /var/run/dhclient.eth0.pid with pid 0
Internet Systems Consortium DHCP Client V3.0.2
Copyright 2004 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

/etc/dhcp3/dhclient-script: line 16: /usr/bin/dbus-send: No such file or directory

Listening on LPF/eth0/00:e0:00:83:b0:ea
Sending on LPF/eth0/00:e0:00:83:b0:ea
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPOFFER from 10.14.125.1
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 10.14.125.1
bound to 10.14.125.21 -- renewal in 38160 seconds.
falx:/#

[Michael Bienia (geser)]

As dbus-send moved to dbus (0.60) the dependency should be added on dbus instead of dbus-1-utils.