Ubuntu
plasma-widget-network-manager package

network manager plasmoid connects but shows "disconnected" icon

Bug #404309 reported by melissawm
90
This bug affects 12 people
Affects Status Importance Assigned to Milestone
knetworkmanager
Fix Released
Medium
plasma-widget-network-manager (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Hi, I'm using Kubuntu 9.04 Jaunty and although plasma-widget-network-manager (version 0.0+svn966653-0ubuntu0.1) connects to the wireless network and I have full access, the icon never changes to the "connected" icon. Attached is a screen capture of the icon and the result of "tail -n0 -f /var/log/syslog > /tmp/syslog" is below.

** EDIT: this is kde 4.3 (KDE 4.2.98 (KDE 4.3 RC3)) from the PPA backports. ***

[stopped network-manager]

Jul 24 22:40:48 elphaba NetworkManager: <WARN> nm_signal_handler(): Caught signal 15, shutting down normally.
Jul 24 22:40:48 elphaba NetworkManager: <info> (eth0): now unmanaged
Jul 24 22:40:48 elphaba NetworkManager: <info> (eth0): device state change: 2 -> 1
Jul 24 22:40:48 elphaba NetworkManager: <info> (eth0): cleaning up...
Jul 24 22:40:48 elphaba NetworkManager: <info> (eth0): taking down device.
Jul 24 22:40:48 elphaba NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Jul 24 22:40:48 elphaba NetworkManager: <info> (eth1): now unmanaged
Jul 24 22:40:48 elphaba NetworkManager: <info> (eth1): device state change: 8 -> 1
Jul 24 22:40:48 elphaba NetworkManager: <info> (eth1): deactivating device (reason: 36).
Jul 24 22:40:48 elphaba NetworkManager: <info> eth1: canceled DHCP transaction, dhcp client pid 13977
Jul 24 22:40:48 elphaba NetworkManager: <WARN> nm_device_wifi_disable_encryption(): error setting key for device eth1: Invalid argument
Jul 24 22:40:48 elphaba NetworkManager: <WARN> check_one_route(): (eth1) error -34 returned from rtnl_route_del(): Sucess
Jul 24 22:40:48 elphaba NetworkManager: <info> (eth1): cleaning up...
Jul 24 22:40:48 elphaba NetworkManager: <info> (eth1): taking down device.
Jul 24 22:40:48 elphaba avahi-daemon[3527]: Withdrawing address record for 192.168.2.3 on eth1.
Jul 24 22:40:48 elphaba avahi-daemon[3527]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.2.3.
Jul 24 22:40:48 elphaba avahi-daemon[3527]: Interface eth1.IPv4 no longer relevant for mDNS.
Jul 24 22:40:48 elphaba avahi-daemon[3527]: Withdrawing address record for fe80::221:ff:fe44:834f on eth1.
Jul 24 22:40:48 elphaba NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Jul 24 22:40:48 elphaba NetworkManager: <info> exiting (success)

[started network manager]

Jul 24 22:41:26 elphaba NetworkManager: <info> starting...
Jul 24 22:41:26 elphaba NetworkManager: <info> (eth0): new Ethernet device (driver: 'forcedeth')
Jul 24 22:41:26 elphaba NetworkManager: <info> (eth0): exported as /org/freedesktop/Hal/devices/net_00_1d_72_6c_41_29
Jul 24 22:41:26 elphaba NetworkManager: <info> (eth1): driver does not support SSID scans (scan_capa 0x00).
Jul 24 22:41:26 elphaba NetworkManager: <info> (eth1): new 802.11 WiFi device (driver: 'wl')
Jul 24 22:41:26 elphaba NetworkManager: <info> (eth1): exported as /org/freedesktop/Hal/devices/net_00_21_00_44_83_4f
Jul 24 22:41:27 elphaba avahi-daemon[3527]: Registering new address record for fe80::221:ff:fe44:834f on eth1.*.
Jul 24 22:41:31 elphaba NetworkManager: <info> (eth0): device state change: 1 -> 2
Jul 24 22:41:31 elphaba NetworkManager: <info> (eth0): bringing up device.
Jul 24 22:41:31 elphaba kernel: [15306.932040] forcedeth 0000:00:0a.0: irq 2300 for MSI/MSI-X
Jul 24 22:41:31 elphaba kernel: [15306.932255] eth0: no link during initialization.
Jul 24 22:41:31 elphaba NetworkManager: <info> (eth0): preparing device.
Jul 24 22:41:31 elphaba NetworkManager: <info> (eth0): deactivating device (reason: 2).
Jul 24 22:41:31 elphaba NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Jul 24 22:41:31 elphaba NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Jul 24 22:41:31 elphaba NetworkManager: <info> (eth1): device state change: 1 -> 2
Jul 24 22:41:31 elphaba NetworkManager: <info> (eth1): preparing device.
Jul 24 22:41:31 elphaba NetworkManager: <info> (eth1): deactivating device (reason: 2).
Jul 24 22:41:31 elphaba kernel: [15306.933617] ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 24 22:41:31 elphaba NetworkManager: <WARN> nm_device_wifi_disable_encryption(): error setting key for device eth1: Invalid argument
Jul 24 22:41:31 elphaba NetworkManager: <info> (eth1): device state change: 2 -> 3
Jul 24 22:41:31 elphaba NetworkManager: <info> (eth1): supplicant interface state: starting -> ready
Jul 24 22:41:36 elphaba kernel: [15312.828021] eth1: no IPv6 routers present
Jul 24 22:41:56 elphaba NetworkManager: <info> Activation (eth1) starting connection 'memenet'
Jul 24 22:41:56 elphaba NetworkManager: <info> (eth1): device state change: 3 -> 4
Jul 24 22:41:56 elphaba NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Jul 24 22:41:56 elphaba NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Jul 24 22:41:56 elphaba NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Jul 24 22:41:56 elphaba NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Jul 24 22:41:56 elphaba NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Jul 24 22:41:56 elphaba NetworkManager: <info> (eth1): device state change: 4 -> 5
Jul 24 22:41:56 elphaba NetworkManager: <info> Activation (eth1/wireless): access point 'memenet' has security, but secrets are required.
Jul 24 22:41:56 elphaba NetworkManager: <info> (eth1): device state change: 5 -> 6
Jul 24 22:41:56 elphaba NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Jul 24 22:41:56 elphaba NetworkManager: <WARN> update_one_setting(): Failed to update connection secrets: 1 802-1x
Jul 24 22:41:56 elphaba NetworkManager: <WARN> real_connection_secrets_updated(): Ignoring updated secrets for setting 'ipv4'.
Jul 24 22:41:56 elphaba NetworkManager: <WARN> real_connection_secrets_updated(): Ignoring updated secrets for setting '802-11-wireless'.
Jul 24 22:41:56 elphaba NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Jul 24 22:41:56 elphaba NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Jul 24 22:41:56 elphaba NetworkManager: <info> (eth1): device state change: 6 -> 4
Jul 24 22:41:56 elphaba NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Jul 24 22:41:56 elphaba NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Jul 24 22:41:56 elphaba NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Jul 24 22:41:56 elphaba NetworkManager: <info> (eth1): device state change: 4 -> 5
Jul 24 22:41:56 elphaba NetworkManager: <info> Activation (eth1/wireless): connection 'memenet' has security, and secrets exist. No new secrets needed.
Jul 24 22:41:56 elphaba NetworkManager: <info> Config: added 'ssid' value 'memenet'
Jul 24 22:41:56 elphaba NetworkManager: <info> Config: added 'scan_ssid' value '1'
Jul 24 22:41:56 elphaba NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Jul 24 22:41:56 elphaba NetworkManager: <info> Config: added 'auth_alg' value 'OPEN'
Jul 24 22:41:56 elphaba NetworkManager: <info> Config: added 'psk' value '<omitted>'
Jul 24 22:41:56 elphaba NetworkManager: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
Jul 24 22:41:56 elphaba NetworkManager: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
Jul 24 22:41:56 elphaba NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Jul 24 22:41:56 elphaba NetworkManager: <info> Config: set interface ap_scan to 1
Jul 24 22:41:56 elphaba NetworkManager: <info> (eth1): supplicant connection state: scanning -> disconnected
Jul 24 22:42:01 elphaba NetworkManager: <info> (eth1): supplicant connection state: disconnected -> scanning
Jul 24 22:42:06 elphaba NetworkManager: <info> (eth1): supplicant connection state: scanning -> associating
Jul 24 22:42:06 elphaba NetworkManager: <info> (eth1): supplicant connection state: associating -> associated
Jul 24 22:42:06 elphaba NetworkManager: <info> (eth1): supplicant connection state: associated -> 4-way handshake
Jul 24 22:42:06 elphaba NetworkManager: <info> (eth1): supplicant connection state: 4-way handshake -> group handshake
Jul 24 22:42:06 elphaba NetworkManager: <info> (eth1): supplicant connection state: group handshake -> completed
Jul 24 22:42:06 elphaba NetworkManager: <info> Activation (eth1/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'memenet'.
Jul 24 22:42:06 elphaba NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) scheduled.
Jul 24 22:42:06 elphaba NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) started...
Jul 24 22:42:06 elphaba NetworkManager: <info> (eth1): device state change: 5 -> 7
Jul 24 22:42:06 elphaba NetworkManager: <info> Activation (eth1) Beginning DHCP transaction.
Jul 24 22:42:06 elphaba NetworkManager: <info> dhclient started with pid 14721
Jul 24 22:42:06 elphaba NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) complete.
Jul 24 22:42:06 elphaba dhclient: Internet Systems Consortium DHCP Client V3.1.1
Jul 24 22:42:06 elphaba dhclient: Copyright 2004-2008 Internet Systems Consortium.
Jul 24 22:42:06 elphaba dhclient: All rights reserved.
Jul 24 22:42:06 elphaba dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Jul 24 22:42:06 elphaba dhclient:
Jul 24 22:42:06 elphaba NetworkManager: <info> DHCP: device eth1 state changed (null) -> preinit
Jul 24 22:42:06 elphaba dhclient: Listening on LPF/eth1/00:21:00:44:83:4f
Jul 24 22:42:06 elphaba dhclient: Sending on LPF/eth1/00:21:00:44:83:4f
Jul 24 22:42:06 elphaba dhclient: Sending on Socket/fallback
Jul 24 22:42:07 elphaba dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
Jul 24 22:42:07 elphaba dhclient: DHCPOFFER of 192.168.2.3 from 192.168.2.1
Jul 24 22:42:07 elphaba dhclient: DHCPREQUEST of 192.168.2.3 on eth1 to 255.255.255.255 port 67
Jul 24 22:42:07 elphaba dhclient: DHCPACK of 192.168.2.3 from 192.168.2.1
Jul 24 22:42:07 elphaba NetworkManager: <info> DHCP: device eth1 state changed preinit -> bound
Jul 24 22:42:07 elphaba NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Get) scheduled...
Jul 24 22:42:07 elphaba NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Get) started...
Jul 24 22:42:07 elphaba NetworkManager: <info> address 192.168.2.3
Jul 24 22:42:07 elphaba NetworkManager: <info> prefix 24 (255.255.255.0)
Jul 24 22:42:07 elphaba NetworkManager: <info> gateway 192.168.2.1
Jul 24 22:42:07 elphaba NetworkManager: <info> nameserver '192.168.2.1'
Jul 24 22:42:07 elphaba NetworkManager: <info> nameserver '138.48.4.4'
Jul 24 22:42:07 elphaba NetworkManager: <info> nameserver '138.48.4.10'
Jul 24 22:42:07 elphaba NetworkManager: <info> domain name 'memenet'
Jul 24 22:42:07 elphaba NetworkManager: nm_ip4_config_add_search: assertion `strlen (search) > 0' failed
Jul 24 22:42:07 elphaba dhclient: bound to 192.168.2.3 -- renewal in 2147483648 seconds.
Jul 24 22:42:07 elphaba NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) scheduled...
Jul 24 22:42:07 elphaba NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Get) complete.
Jul 24 22:42:07 elphaba NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) started...
Jul 24 22:42:07 elphaba avahi-daemon[3527]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.2.3.
Jul 24 22:42:07 elphaba avahi-daemon[3527]: New relevant interface eth1.IPv4 for mDNS.
Jul 24 22:42:07 elphaba avahi-daemon[3527]: Registering new address record for 192.168.2.3 on eth1.IPv4.
Jul 24 22:42:08 elphaba NetworkManager: <info> (eth1): device state change: 7 -> 8
Jul 24 22:42:08 elphaba NetworkManager: <info> Policy set 'memenet' (eth1) as default for routing and DNS.
Jul 24 22:42:08 elphaba NetworkManager: <info> Activation (eth1) successful, device activated.
Jul 24 22:42:08 elphaba NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) complete.
Jul 24 22:42:10 elphaba ntpdate[14784]: adjust time server 91.189.94.4 offset 0.056501 sec

See original description
Revision history for this message
melissawm (melissawm) wrote :
melissawm (melissawm)
description: updated
Revision history for this message
bigbrovar (bigbrovar) wrote :

I can confirm this on kubuntu 9.04 running kde 4.3 from the kde ppa backport .. it use to work fine too i upgraded to kde 4.3 RC3 which is when the problem started .. i get no feed back on connection status even when am connected to a wireless network

Revision history for this message
Mark (mark-ale8) wrote :

Confirmed here, after upgrading to KDE 4.3 RC3 today, the network manager widget works fine, and seems to connect faster than before, but does not show the correct icon, or the "working" spinning icon while making a connection. Only the "disconnected" icon is shown.

Revision history for this message
darkness_s (dark13ness) wrote :

Confirmed on Kubuntu 9.04 after updating to KDE 4.3 RC3. The icon never changes although it does connect fine, and faster than before.

Jonathan Thomas (echidnaman)
Changed in plasma-widget-network-manager (Ubuntu):
status: New → Triaged
importance: Undecided → Low
Bug Watch Updater (bug-watch-updater)
Changed in knetworkmanager:
status: Unknown → New
Revision history for this message
bigbrovar (bigbrovar) wrote :

I would like to add that downgrading from plasma-widget-network-manager Version: 0.0+svn966653-0ubuntu0.1 (the version after the upgrade to kde 4.3 RC3) to the previous version of plasma-widget-network-manager Version: 0.0+svn930811-0ubuntu2 (the version before the upgrade) seem not to fix the problem. So this may not be a problem with the plasma-widget-network-manager package its self

Revision history for this message
Leon Maurer (leon-n-maurer) wrote :

I can confirm this behavior with KDE 4.3 RC3 too.

Revision history for this message
micuintus (micuintus) wrote :

confirmed (packages from kubuntu.org --- ppa sources)

Revision history for this message
darkness_s (dark13ness) wrote :

Also, after Plasma crashed and reloaded, the icon changed to the spinning "connecting" icon and then "connected" icon appeared when the connection was established. However, it appeared below the other icon so both were visible. The connecting icon never stopped spinning.

Revision history for this message
Ole Jon Bjørkum (olejonbj) wrote :

Confirmed here, with Kubuntu 9.04 and KDE 4.3 RC3 from backports. Worked fine in RC2.

Revision history for this message
Ole Jon Bjørkum (olejonbj) wrote :

One more thing: If I hover the mouse over the icon, it says "wlan0 not connected" but if I left-click on it, it says that it is connected.

Revision history for this message
Ole Jon Bjørkum (olejonbj) wrote :

Hmm, just found out that if I kill plasma-desktop (killall plasma-desktop), and then run plasma-desktop again, the icon now shows the correct icon (connected).

Revision history for this message
Simone (rsimone77) wrote :

Confirmed here, with Kubuntu 9.04 and KDE 4.3 RC3 from ppa backports. Worked fine in RC2.

Revision history for this message
Jeremy LaCroix (jlacroix82-deactivatedaccount) wrote :

Same problem here. It shows the "unplugged" icon when I am connected to wireless. If I connect to a wired connection, only then does the icon change. If I hover my mouse over the icon, it says "eth0: unavailable" and "eth1: Not Connected".

Bug Watch Updater (bug-watch-updater)
Changed in knetworkmanager:
status: New → Confirmed
Bug Watch Updater (bug-watch-updater)
Changed in knetworkmanager:
status: Confirmed → Invalid
Jonathan Thomas (echidnaman)
Changed in knetworkmanager:
status: Invalid → Unknown
Bug Watch Updater (bug-watch-updater)
Changed in knetworkmanager:
status: Unknown → New
Revision history for this message
Søren Holm (sgh) wrote :

I also confirm. #11 trick also works for me.

Revision history for this message
urusha (urusha) wrote :

The same thing. kde 4.2.98 from backports.

Revision history for this message
José Tomás Atria (jtatria) wrote :

still present in kde 4.3.0

Bug Watch Updater (bug-watch-updater)
Changed in knetworkmanager:
status: New → Confirmed
Revision history for this message
rusart (ruslan-levitskiy) wrote :

Confirm this bug in KDE 4.3.0

Revision history for this message
Ole Jon Bjørkum (olejonbj) wrote :

Is this bug still in KDE 4.3 final?

Revision history for this message
Engenilk (engenilk) wrote :

The bug persists in KDE 4.3

Revision history for this message
micuintus (micuintus) wrote :

confirmed in 4.3 --- packages from kubuntu.org

Bug Watch Updater (bug-watch-updater)
Changed in knetworkmanager:
status: Confirmed → Fix Released
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Fixed with the latest packages.

Changed in plasma-widget-network-manager (Ubuntu):
status: Triaged → Fix Released
Bug Watch Updater (bug-watch-updater)
Changed in knetworkmanager:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Bug attachments

Remote bug watches

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