[kubuntu] NetworkManager default unmanaged

Bug #465591 reported by Bartłomiej Żogała
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
plasma-widget-networkmanagement (Ubuntu)
Confirmed
High
Unassigned

Bug Description

Binary package hint: network-manager

After updating from jaunty to karmic installer changed in /etc/NetworkManager/nm-system-settings.conf

in section
[ifupdown]
-managed=true
+managed=false

Then the kdenetwork manager didn't see the wifi at all. After enabling managed and restart everything works. Is there any reason that this setting isn't default ? I'm asking about Kubuntu, maybe in Ubuntu this is solved in another way, but I can't see any other way to configure wireless under Kubuntu - manually setup a config in text file IMHO isn't really convinient.

Revision history for this message
dusoft (dusoft-staznosti) wrote :

this is outrageous, first on upgrade system changes my default config, which managed=true and everything worked to false and now even after connecting computer via fixed connection eth0 at different network, it is absolutely unable to connect.

there is no reason that it: overwrites my config and that default config is not set to managed=true !!!

Revision history for this message
Fabián Rodríguez (magicfab) wrote :

I can reproduce this on clean install of Kubuntu 10.04LTS, although it's within a VM (in kvm) so the interface is virtual. Network connectivity is there, everything works as expected except it can't be managed via NM.

I didn't need to reboot, but I restarted the service:
sudo service network-manager restart

Changed in network-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
Fabián Rodríguez (magicfab) wrote :

Upon closer inspection I couldn't manage the interface although the NM indicator showed a valid connection.

Revision history for this message
Fabián Rodríguez (magicfab) wrote :

I can confirm after changing the entry managed=false in /etc/NetworkManager/nm-system-settings.conf this works expected.

I've marked this as importance=high as it fits one or more of the following criteria:

# Has a severe impact on a small portion of Ubuntu users (estimated)
# Makes a default Ubuntu installation generally unusable for some users
# A problem with an essential hardware component (disk controller, laptop built-in wireless, video card, keyboard, mouse)
# Has a moderate impact on a large portion of Ubuntu users (estimated)

For more information on bugs importance see:
https://wiki.ubuntu.com/Bugs/Importance

Changed in network-manager (Ubuntu):
importance: Undecided → High
Revision history for this message
Fabián Rodríguez (magicfab) wrote :

Bug #524454 is similar to this one and has been fixed upstream.

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Fabian, this is a different issue. It looks to be something different in the way knetwork-manager (anyway, the NetworkManager plasma applet) handles these settings.

affects: network-manager (Ubuntu) → plasma-widget-networkmanagement (Ubuntu)
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.