Comment 32 for bug 93360

or those of you who have not yet tried to find out what this "thing" actually is, here is something from Debian: "dhcdbd provides a D-Bus interface to dhclient, the DHCP client from ISC, so applications such as NetworkManager can query and control dhclient. This allows an application-neutral interface for such operations"

 It was suggested (in something I read somewhere) that the problem lies with NetworkManager, which is a Gnome problem. With only limited comprehension of the english language, perhaps I am misreading the Debian description which seems to put the issue squarely in this venue.

That aside, I have been able t locate two places that appear to be (at least) a part of the problem:

/etc/dbus-1/system.d <<complete text follows>>

# if we are called by dhcdbd, push the information acquired by dhclient back to dhcdbd
if [ -n "${dhc_dbus}" ]; then
  /usr/bin/dbus-send \
  --system \
  --dest=com.redhat.dhcp \
  --type=method_call \
  /com/redhat/dhcp/$interface \
  com.redhat.dhcp.set \
  'string:'"`env | /bin/egrep -v '^(PATH|SHLVL|_|PWD|dhc_dbus)\='`";
fi;

and in

/etc/dhcp3/client-exit-hooks.d/dhcdbd <<complete text follows>>

# if we are called by dhcdbd, push the information acquired by dhclient back to dhcdbd
if [ -n "${dhc_dbus}" ]; then
  /usr/bin/dbus-send \
  --system \
  --dest=com.redhat.dhcp \
  --type=method_call \
  /com/redhat/dhcp/$interface \
  com.redhat.dhcp.set \
  'string:'"`env | /bin/egrep -v '^(PATH|SHLVL|_|PWD|dhc_dbus)\='`";
fi;

Not to be at all insulting to anyone (really--I mean that) it appears that somewhere along the line a "sample script" was copied and pasted in order to make things work without reinventing the wheel. It may be that the unaltered files slipped though the quality control process.

Sorry to say, I don't know anywhere near enough to begin to rewrite this. But my guess is that it would not be a terribly difficult task who understood the guts of what is **supposed** to be happening. I also cannot assure anyone that these are the only two instances causing problems.

I hope this hekps someone to pound out a fix. Wireless that doesn't work, or doesn't work reliably is a show stopper. I admit to getting almost ticked off enough to wipe out this installation on return to Slackware. Can't have that, now, can we?