On 11/19/07, bawigga <email address hidden> wrote:
> Same error with latest Gutsy. Now my wireless wont connect at all, even
> after a reboot (tried 3 times).
If you did update/upgrade from fiesty, it is probably more issue with
the kernel than this error message and dhcdbd. I made my entry on this
a long time ago. IMHO, the output of this bug is pretty irrelevant and
the impact people have is varied and certainly unrelated to the code
which makes this bug.
I will agree though, that the dhcdbd package has a big effect on a
system and that if something isn't configured (where/how? got me), the
symptoms reported in this thread can occur. I've had real good luck
with eliminating all other error messages, too, like the another one
typically ignored: http://ubuntuforums.org/showthread.php?t=521751
--
Chris Kelley
President
California Cycleworks, Inc
www.ca-cycleworks.com
619/501-2466
On 11/19/07, bawigga <email address hidden> wrote:
> Same error with latest Gutsy. Now my wireless wont connect at all, even
> after a reboot (tried 3 times).
If you did update/upgrade from fiesty, it is probably more issue with
the kernel than this error message and dhcdbd. I made my entry on this
a long time ago. IMHO, the output of this bug is pretty irrelevant and
the impact people have is varied and certainly unrelated to the code
which makes this bug.
I will agree though, that the dhcdbd package has a big effect on a ubuntuforums. org/showthread. php?t=521751
system and that if something isn't configured (where/how? got me), the
symptoms reported in this thread can occur. I've had real good luck
with eliminating all other error messages, too, like the another one
typically ignored: http://
-- cycleworks. com
Chris Kelley
President
California Cycleworks, Inc
www.ca-
619/501-2466