[Feisty]Update breaks wireless capabilities of network manager

Bug #105825 reported by der_vegi
8
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

the latest (april 12th) update of network-manager to 0.6.4-6ubuntu6 breaks mir wireless: network manager doesn't even show that there is a wireless card any more. i can only see the wired network card.

i'm using ubuntu daily 20070409.1 on an amd64 machine with ndiswrapper.

Revision history for this message
der_vegi (m-may) wrote :

even when i am connected to the wired network, i can't ping anything. i have to do manually "ifdown eth1" (eth1 = wireless) and then network works. but still (right now for example) network-manager shows "no connection", though wired network is selected and dhcp has done everything automatically.

Revision history for this message
Mr Squiddy (pthompson66) wrote :

Numerous instances of this bug have been reported on UbuntuForums.org. Several workarounds have been suggested (see http://ubuntuforums.org/showthread.php?t=407204).

Revision history for this message
der_vegi (m-may) wrote :

the new update of network-manager to 0.6.4.-6ubuntu7 doesn't improve the situation.

Revision history for this message
probos (probostide) wrote :

I've got it working now. Do not configure your connection manually or it won't appear at KNetworkManager

Revision history for this message
der_vegi (m-may) wrote :

well, that's one possibility.

for me configuring the connection and wpa_supplicant manually works fine. still doesn't appear in gnome-network-manager, though.

Revision history for this message
Martin Pitt (pitti) wrote :

If you configure the network card manually, then n-m does not manage it any more and should not touch its configuration.

Revision history for this message
Amazing Iceman (iceman-arenas) wrote :

I would imagine that as its name says: "NetworkManager", it should "MANAGE" all network interfaces and their configuration, regardless how they are configured (static or DHCP).

Otherwise, n-m is pointless, lacks consistency and it becomes confusing new users.

Let's not give them reasons to complain, specially to those switching from Windows.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.