I found a temporary solution to the bug. The problem seems to be related to a dhcp issue. After I restarted the network devices manually I recognized that the start script waits for a dhcp answer. And it does this very long. If you haven't got a static configuration for your devices you can fix the bug temporarily by commenting out all the devices execpt the loopback device, which is essential, in the /etc/network/interfaces . My file:
auto lo
iface lo inet loopback
#auto eth0
#iface eth0 inet dhcp
#auto eth1
#iface eth1 inet dhcp
#auto eth2
#iface eth2 inet dhcp
#auto ath0
#iface ath0 inet dhcp
#auto wlan0
#iface wlan0 inet dhcp
For me this resolves the problem. But this is just a temporary solution because I don't expect all the future Feisty users with this issue to read this bug report or to be willing to find a solution by themselves...
I found a temporary solution to the bug. The problem seems to be related to a dhcp issue. After I restarted the network devices manually I recognized that the start script waits for a dhcp answer. And it does this very long. If you haven't got a static configuration for your devices you can fix the bug temporarily by commenting out all the devices execpt the loopback device, which is essential, in the /etc/network/ interfaces . My file:
auto lo
iface lo inet loopback
#auto eth0
#iface eth0 inet dhcp
#auto eth1
#iface eth1 inet dhcp
#auto eth2
#iface eth2 inet dhcp
#auto ath0
#iface ath0 inet dhcp
#auto wlan0
#iface wlan0 inet dhcp
For me this resolves the problem. But this is just a temporary solution because I don't expect all the future Feisty users with this issue to read this bug report or to be willing to find a solution by themselves...