network manager broken

Bug #332407 reported by Peter Silva
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plasma-widget-networkmanagement (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

was running find with Jaunty for the past month. on the 19th, did apt-get upgrade to get latest stuff, and network-manager has been broken since. It didn't work with a WPA-2 protected network at work, a WPA-1 PSK one at home, nor with plain old copper and DHCP. All of the above worked well before then. Now nothing works at all unless I shutdown NetworkManager completely and use /etc/network/interfaces instead. It doesn't even work to use the manual interface and leave NetworkManager running, because NM ensures there is no default route.

No way to get any type of network connection over any interfaces with NM lately. Originally tried with knetworkmanager, but repeated same symptoms with the plasmoid as well.

Revision history for this message
Andy Ferguson (teknostatik) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't start working on it yet, because your bug report didn't include enough information.

Please include the information requested at https://wiki.ubuntu.com/DebuggingNetworkManager. If you have trouble, do not hesitate to ask for more assistance. Thanks in advance.

Regards,

Andy

Changed in network-manager:
status: New → Incomplete
Revision history for this message
Peter Silva (peter-bsqt) wrote :

if you could provide some guidance as to what you need, that would be somewhat more useful.

Revision history for this message
Peter Silva (peter-bsqt) wrote :

i did...

# start with serial log and tee it in a log file
NM_SERIAL_DEBUG=1 NetworkManager --no-daemon 2>&1 | tee /tmp/nm-serial.txt
added some logs for a sample... nm_wpa_log is the output from this..
to reproduce, I just startup network manager and it doesn't work, regardless of iface.
it's an intel chipset, and connecting manually with copper at least, works fine. so it's now hw.

Revision history for this message
Peter Silva (peter-bsqt) wrote :
Download full text (7.0 KiB)

ok... well now copper works ok...

root@tough:/etc/network# NetworkManager --no-daemon 2>&1 | tee /tmp/nm-serial_cu.log NetworkManager: <info> starting...
NetworkManager: <info> Found radio killswitch /org/freedesktop/Hal/devices/pci_8086_4222_rfkill_3945ABG_wlan
NetworkManager: <info> Found radio killswitch /org/freedesktop/Hal/devices/iwl_wlan_switch
NetworkManager: <info> (eth0): new Ethernet device (driver: 'sky2')
NetworkManager: <info> (eth0): exported as /org/freedesktop/Hal/devices/net_00_0b_97_35_37_2f
NetworkManager: <info> (wlan0): driver supports SSID scans (scan_capa 0x01).
NetworkManager: <info> (wlan0): new 802.11 WiFi device (driver: 'iwl3945')
NetworkManager: <info> (wlan0): exported as /org/freedesktop/Hal/devices/net_00_18_de_97_10_08
NetworkManager: <info> Trying to start the system settings daemon...
NetworkManager: <WARN> killswitch_getpower_reply(): Error getting killswitch power: Method "GetPower" with signature "" on interface "org.freedesktop.Hal.Device.KillSwitch" doesn't exist
.
NetworkManager: <WARN> connection_get_settings_cb(): connection_get_settings_cb: Invalid connection: 'NMSettingWirelessSecurity' / 'psk' invalid: 1
NetworkManager: <info> (eth0): device state change: 1 -> 2
NetworkManager: <info> (eth0): bringing up device.
NetworkManager: <info> (eth0): preparing device.
NetworkManager: <info> (eth0): deactivating device (reason: 2).
NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
NetworkManager: <info> (wlan0): device state change: 1 -> 2
NetworkManager: <info> (wlan0): bringing up device.
NetworkManager: <info> (wlan0): preparing device.
NetworkManager: <info> (wlan0): deactivating device (reason: 2).
NetworkManager: <info> (wlan0): device state change: 2 -> 3
NetworkManager: <info> (wlan0): supplicant interface state: starting -> ready
NetworkManager: <info> (eth0): carrier now ON (device state 2) ...

Read more...

Revision history for this message
Peter Silva (peter-bsqt) wrote :

[disconnect copper, click on connection to my WPA wlan, intel 3495 ]

NetworkManager: <info> (eth0): device state change: 7 -> 8
NetworkManager: <info> Policy set 'Auto eth0' (eth0) as default for routing and DNS.
NetworkManager: <info> Activation (eth0) successful, device activated.
NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
NetworkManager: <info> (eth0): carrier now OFF (device state 8)
NetworkManager: <info> (eth0): device state change: 8 -> 2
NetworkManager: <info> (eth0): deactivating device (reason: 40).
NetworkManager: <info> eth0: canceled DHCP transaction, dhcp client pid 12947
-- Error received: Numerical result out of range
-- Original message: type=0x19 length=56 flags=<REQUEST,ACK> sequence-nr=1235234095 pid=4207241
NetworkManager: <WARN> check_one_route(): (eth0) error -34 returned from rtnl_route_del(): Sucess

NetworkManager: <WARN> wait_for_connection_expired(): Connection (2) /org/freedesktop/NetworkManagerSettings/Connection/0 failed to activate (timeout): (0) Connection was not provided by any settings service

if I re-connect copper it's OK.

Revision history for this message
Peter Silva (peter-bsqt) wrote :

I installed nm-applet, and everything works... so the problem has something to do with KDE.
the problem is reproducible with either knetworkmanager and/or the plasmoid.

Revision history for this message
Scott Kitterman (kitterman) wrote :

Package renamed.

Revision history for this message
Peter Silva (peter-bsqt) wrote : Re: [Bug 332407] Re: network manager broken

confirmed... it didn't work with the plasmoid, and it doesn't work with the
widget either.

WPA1 with known SSID, as well as and WPA2 with private SSID.

both cases work fine with Gnome nm-applet.

On Mon, Feb 23, 2009 at 11:05 PM, Scott Kitterman <email address hidden>wrote:

> Package renamed.
>
> ** Changed in: plasma-widget-network-manager (Ubuntu)
> Sourcepackagename: plasmoid-network-manager =>
> plasma-widget-network-manager
>
> --
> network manager broken
> https://bugs.launchpad.net/bugs/332407
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Andreas Ntaflos (daff) wrote :

I seem to be able to confirm that problem with the latest Alpha (6) of Kubuntu. Knetworkmanager shows the network in question but connecting to it simply doesn't work. The Gnome applet nm-applet on the other hand works just fine. Hope this gets fixed in time.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Is this still a problem with the final version of Kubuntu 9.04?

Revision history for this message
Peter Silva (peter-bsqt) wrote :

yes.

On Fri, Jul 31, 2009 at 9:50 AM, Jonathan Thomas <email address hidden>wrote:

> Is this still a problem with the final version of Kubuntu 9.04?
>
> --
> network manager broken
> https://bugs.launchpad.net/bugs/332407
> You received this bug notification because you are a direct subscriber
> of the bug.
>

affects: plasma-widget-network-manager (Ubuntu) → plasma-widget-networkmanagement (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for plasma-widget-networkmanagement (Ubuntu) because there has been no activity for 60 days.]

Changed in plasma-widget-networkmanagement (Ubuntu):
status: Incomplete → Expired
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.