[Bug 404309] [NEW] network manager plasmoid connects but shows "disconnected" icon
melissawm
melissawm at gmail.com
Fri Jul 24 20:44:02 UTC 2009
Public bug reported:
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.
[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
** Affects: plasma-widget-network-manager (Ubuntu)
Importance: Undecided
Status: New
--
network manager plasmoid connects but shows "disconnected" icon
https://bugs.launchpad.net/bugs/404309
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to plasma-widget-network-manager in ubuntu.
More information about the kubuntu-bugs
mailing list