Hardy has seen the end of its life and is no longer receiving any
updates. Marking the Hardy task for this ticket as Won't Fix.
** Changed in: dhcdbd (Ubuntu Hardy)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The only package that needed dhcdbd was network-manager, and that
dependency is gone as of n-m 0.7. Here are the bugs.debian posts
requesting and confirming the package removal:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527849
** Bug watch added: Debian Bug tracker #527849
2009/6/11 AintNoBug j...@webprophets.net.au:
Just bumping.
This has appeared in a Debian release, 11/06/2009.
2.6.28-2009031001 #1 SMP Tue Mar 10 18:50:23 EST 2009 i686 GNU/Linux
It has been a while since I saw it in Ubuntu. Certainly not in Jaunty.
--
Dhcdbd doesn't recognize permanent
Just bumping.
This has appeared in a Debian release, 11/06/2009.
2.6.28-2009031001 #1 SMP Tue Mar 10 18:50:23 EST 2009 i686 GNU/Linux
dhcpdb is running.
lease can be requested and is sent.
never makes it to eth1 (which is the primary, not eth0).
This occured after a dist-upgrade.
Following
Dudes. This is /really/ frustrating. How has this not been fixed yet? I
have NO WIRELESS at the moment!
I did for a day or so after I freshly installed Ubuntu, but now, all of
a sudden, it's fucked up. How hard can it possibly be to set up a
network connection? Answer: not very. I can do it
Upon closer inspection, it looks like my bug, and I'm sure that of a few
of the above posters, is actually Bug #105251
--
Dhcdbd doesn't recognize permanent (-1) DHCP leases
https://bugs.launchpad.net/bugs/93360
You received this bug notification because you are a member of Ubuntu
Bugs, which is
By the way, I was only able to use Update Manager in those brief 99s
before the connection was killed. I had to do it a few times to complete
all the downloads :|. It wouldn't work if I manually configured the
wireless connection, either via Network Manager or via the console. The
stupid thing is
I don't know what to say. As mysteriously as the bug appeared, it
vanished. My Network Manager works perfectly now.
Here's all I did. I originally tried myric's workaround a few posts
above, and it didn't work. I updated a bunch of software via Update
Manager (there was a lot to update, since
Although my wireless connection is working (somehow), I often find that
update manager will kill that connection to the extent that I need to reboot
my router! I can't just reboot the laptop, it actually kills my router
somehow. Jeez! Yet, when I use a wired connection to my router, everything
I saw this bug yesterday in Hardy. I put in the live cd and _still_ saw
the error. Very weird. I put the live cd into my laptop and I got the
same error. Too much of a coincidence I thought.
I rebooted my router and it went away. Weirdest thing. Try it! It
worked for me!
--
Dhcdbd
Hardy Heron and it's still definitely present. Since the upgrade my
wireless connection is still operational but the indicator light on my
HP laptop wireless device shows it's not connected (red not blue as it
should be). That's four distros it's been an issue. Are we going to go
for five?
--
@Gisbert
These log messages may have nothing to do with your wifi not working. I
have theses log messages and wifi is working perfectly well. Maybe you
should open a new bug for this describing the hardware (what chipset do
you have) of the machine. You may also try to post it to a forum. I am
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION=Ubuntu 8.04
This bug caught me after the automatic upgrade to Hardy. WLAN did work
quite well before. No it doesn't any more.
When it tries to connect, it writes lots of the aforementioned messages
into the syslog:
Hi!
I'd like to say I've 'solved' my problem - I'm not sure this bug is the right
one for what I was experiencing.
I think my problem was more related to:
https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/51315
although it manifested itself at login or when switching network with
Yeah, I don't think that's my problem since LDAP isn't anywhere in my
nsswitch.conf... Thanks though!
glad that worked for you.
** Attachment added: my nsswitch.conf
http://launchpadlibrarian.net/14070909/nsswitch.conf.txt
--
Dhcdbd doesn't recognize permanent (-1) DHCP leases
It is kind of bothersome that this bug is still unassigned, and only marked
medium importance... This bug is still active, hundreds of people are hurt by
it!
It is a real show-stopper for normal laptop usage:
You can't switch cables, you can't switch from LAN to WLAN or back, you can't
Don't known if will help, but doing a
sudo /etc/init.d/networking restart
fixes the problem, of course, it's a pain in the ass to do that
everytime the system starts up.
--
Dhcdbd doesn't recognize permanent (-1) DHCP leases
https://bugs.launchpad.net/bugs/93360
You received this bug
Hi!
Thanks for the hint! Unfortunately that does not help me, but it did
inspire me to search a little further:
It seems that in my case, the problem is not really related to the
network interface or dhcp itself - those are working fine. The problem
seems to lie somewhere with nm-applet,
Hi,
That also happens to me, but only with the next config
auto lo
iface lo inet loopback
#auto eth0
#iface eth0 inet dhcp
auto br0
iface br0 inet dhcp
bridge_ports eth0
bridge_fd 2.5
If I enable the eth0, then works fine. Why I'm disabling it? Because
it's the recommended
Confirmed for Hardy LTS on fresh install:
Apr 28 10:42:08 Sparta dhcdbd: message_handler: message handler not found under
/com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.reason
Apr 28 10:42:10 Sparta kernel: [ 260.757027] ADDRCONF(NETDEV_CHANGE): ath0:
link becomes ready
Apr 28 10:42:16
Still present in Hardy latest clean install
Apr 27 08:39:06 ubuntu1 kernel: [13310.357754] eth0: link up.
Apr 27 08:39:22 ubuntu1 dhcdbd: dhco_input_option: Value 4294967295 cannot be
converted to type L
Apr 27 08:39:22 ubuntu1 dhcdbd: dhco_parse_option_settings: bad option setting:
I am getting similar behavior on Gutsy with wired Ethernet:-
Apr 15 09:15:17 john-ubuntu dhcdbd: message_handler: message handler not found
under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name
Apr 15 09:15:17 john-ubuntu dhcdbd: message_handler: message handler not found
under
Apr 13 00:22:17 * dhcdbd: Started up.
Apr 13 00:22:20 * dhcdbd: message_handler: message handler not found under
/com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.reason
Apr 13 00:22:26 * dhcdbd: message_handler: message handler not found under
/com/redhat/dhcp/eth1 for sub-path
I am seeing this same issue in the hardy beta:
Mar 29 17:33:11 ubuntu dhcdbd: message_handler: message handler not found under
/com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.reason
Mar 29 17:33:34 ubuntu kernel: [ 449.275313] ADDRCONF(NETDEV_CHANGE): ath0:
link becomes ready
My wireless
** Summary changed:
- Dhcdbd: message_handler: message handler not found under
/com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.reason
+ Dhcdbd doesn't recognize permanent (-1) DHCP leases
--
Dhcdbd doesn't recognize permanent (-1) DHCP leases
https://bugs.launchpad.net/bugs/93360
You received
25 matches
Mail list logo