[Bug 30220] Problem with automatic start NIC adapters after update Dapper Drake Flight CD3

[UbuPetr]

Public bug reported:
https://launchpad.net/malone/bugs/30220

Affects: hal hal-device-manager (Ubuntu)
       Severity: Normal
       Priority: (none set)
         Status: Unconfirmed

Description:
I installed Kubuntu Dapper Drake Flight CD3 and everything worked well.
I think, there was a hotplug (I hope, it was there) and in
/etc/netwok/interfaces I had for booth NIC cards allow-hotplug, for
automatic start after boot Operating System. Next day I made aptitude
update; aptitude upgrade and NIC cards do not start automatic after boot
Operating System and look at that: I think that hotplug was repalced
with hal daemon (if hotplug and hal daemon is equal in functions) and
happening this now: If we add in booth NIC cards auto eth0 and auto eth1
(replaced from older allow-hotplug eth0 and allow-hotplug eth1), so NIC
cards start automatic, but packet traffic is freeze. Route tables, DNS,
gateways, ... everything is filled correctly, but no packet traffic
(this do not help: ifdown NICs, ifup NICs and modprobe -r net_drivers
and again modprobe net_drivers). And continue listening: If we remove
auto eth0 a auto eth1 and after booting Operating System we manually
type ifup eth0 and ifup eth1, so NIC cards starts and everything working
right. Do You know, where is the problem? It is injured by hal daemon,
or beceasue hotplag is disappered? I think, there is a bug, because with
manual start without auto eth0 and auto eth1 NIC cards working - I
think, something do bad things, that driving this commands auto eth0 and
auto eth1 in /etc/network/interfaces. It was happend in Kubuntu Dapper
Drake Flight CD3 after aptitude update; aptitude upgrade. Your's
Sincerely, Petr Novák `'ubu (dot] petr /at\ seznam [dot) cz". PS: Excuse
me for my bad english.