Me too... Kubuntu Fiesty amd64 on x86_64 ... also after compiling to get 
video/audio/dvd/etc working...
Dell D630 Intel DuoCore, Intel chipset, Intel video, Intel wireless, broadcom 
gigabit 
[EMAIL PROTECTED]:~/d630$ uname -a
Linux outside 2.6.22.1 #1 SMP Fri Aug 3 15:51:41 PDT 2007 x86_64 GNU/Linux
[EMAIL PROTECTED]:~/d630$

dmesg content:
Aug  4 13:43:37 outside dhcdbd: Started up.
Aug  4 13:43:38 outside dhcdbd: message_handler: message handler not found 
under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Aug  4 13:43:38 outside dhcdbd: message_handler: message handler not found 
under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason

[ snip ]

Aug  4 15:41:13 outside kernel: [ 1784.782777] tg3: eth0: Link is down.
Aug  4 15:41:29 outside kernel: [ 1787.671145] tg3: eth0: Link is up at 100 
Mbps, full duplex.
Aug  4 15:41:29 outside kernel: [ 1787.671155] tg3: eth0: Flow control is on 
for TX and on for RX.
Aug  4 15:41:35 outside dhcdbd: message_handler: message handler not found 
under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name
Aug  4 15:41:35 outside dhcdbd: message_handler: message handler not found 
under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.domain_name
Aug  4 15:41:35 outside dhcdbd: message_handler: message handler not found 
under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
Aug  4 15:41:35 outside dhcdbd: message_handler: message handler not found 
under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers

I am reasonably sure the dhcdbd messages are related to the network
event. I unplugged from one ethernet cable to another one. Why? From a
short cable to a longer one to move from a table across the room. This
message repeats.

Once before, I chased down this code through the network if scripts and
couldn't see an easy workaround.

:) Chris

-- 
Dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 
for sub-path eth1.dbus.get.reason
https://bugs.launchpad.net/bugs/93360
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to