Your message dated Sun, 07 Mar 2010 23:09:20 +0100
with message-id <4b942410.3010...@debian.org>
and subject line Re: Bug#461502: network-manager-kde: knetworkmanager hangs
kicker, blocks shutdown on first use
has caused the Debian Bug report #461502,
regarding network-manager-kde: knetworkmanager hangs kicker, blocks shutdown on
first use
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
461502: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=461502
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: network-manager-kde
Version: 1:0.2-2
Severity: normal
This bug reports a severe, but not reproducible, problem. Given the
severity, and the resemblance to some existing bugs, I thought it
would be useful to report anyway. I am quite unsure what package is
the ultimate cause of the problem.
After using knetworkmanager to turn on a wireless network
1) the icon for knetworkmanager disappeared from the kicker
2) the kicker itself stopped being painted and responding
3) when I tried to shut the system down, with shutdown -r now, it
would not shut down and I had to power off.
When I restarted, things seemed to be working alright.
Fuller history:
My laptop has an Intel 4965AGN wireless card and a regular ethernet
connection as well. The latter is unplugged. I had been starting
both with conventional /etc/network/interfaces (using wpa-* options),
bring the interfaces up manually. After reading the Debian
instructions for network-manager I changed interfaces to
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0
allow-hotplug eth0
iface eth0 inet dhcp
auto wlan0
iface wlan0 inet dhcp
and shutdown.
When I restarted, dhcpclient was trying to get information for wlan0 during the
initial system startup. This produced a delay, and doesn't seem like
proper behavior, but ultimately the system started.
I logged in to my account under KDE, and knetworkmanager (via the
applet in the kicker) showed available networks. I selected mine,
which is password protected, and entered the password. This failed.
This progress indicator went up through 25%, and the logs show it at
stage 2.
I tried again and failed again. At this point, the icon for
knetworkmanager disappeared, the kicker became unresponsive and was
not repainted (so eventually nothing was visible in it), and there was
an initial period of high CPU use from xorg. The CPU use quieted
down. The kicker and 2 wpa_supplicant processes (wpa_supplicant as
root) were all in state D (uninterruptible sleep) according to ps.
During the whole time dhcp-client continued to attempt to get
information non both eth0 and wlan0.
>From within a root shell in my KDE session I executed shutdown -r
now. Nothing appeared in virtual terminal 1 (which was displaying the
startup messages), but vt7 did lose the KDE session and showed
messages for the shutdown of window managers and "shutting down
apache2." The cursor remained after the end of that last line. I had
to hit the power off, which was a dirty shutdown.
On reboot, I was not connected to anything. However, this time I used
knetworkmanager to connect to my wireless network.
Selected logs:
Jan 18 12:47:23 cotton kernel: iwl4965: Intel(R) Wireless WiFi Link 4965AGN
driver for Linux, 1.2.22ds
Jan 18 12:47:23 cotton kernel: iwl4965: Copyright(c) 2003-2007 Intel
Corporation
Jan 18 12:47:23 cotton kernel: iwl4965: Tunable channels: 11 802.11bg, 13
802.11a channels
Jan 18 12:47:23 cotton kernel: wmaster0: Selected rate control
algorithm 'iwl-4965-rs'
Jan 18 12:47:23 cotton kernel: lo: Disabled Privacy Extensions
Jan 18 12:47:23 cotton kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jan 18 12:47:23 cotton kernel: ADDRCONF(NETDEV_UP): wlan0: link is not
ready
# also bluetooth, avahi, snort
Jan 18 12:47:39 cotton NetworkManager: <info> starting...
Jan 18 12:47:39 cotton NetworkManager: <info> New VPN service 'openvpn'
(org.freedesktop.NetworkManager.openvpn).
Jan 18 12:47:39 cotton NetworkManager: <info> New VPN service 'vpnc'
(org.freedesktop.NetworkManager.vpnc).
Jan 18 12:47:39 cotton NetworkManager: <info> wlan0: Device is fully-supported
using driver 'iwl4965'.
Jan 18 12:47:39 cotton NetworkManager: <info> nm_device_init(): waiting for
device's worker thread to start
Jan 18 12:47:39 cotton NetworkManager: <info> nm_device_init(): device's
worker thread started, continuing.
Jan 18 12:47:39 cotton NetworkManager: <info> Now managing wireless (802.11)
device 'wlan0'.
Jan 18 12:47:39 cotton NetworkManager: <info> Deactivating device wlan0.
Jan 18 12:47:39 cotton avahi-daemon[5211]: Withdrawing address record for
169.254.7.238 on wlan0.
Jan 18 12:47:39 cotton avahi-daemon[5211]: Leaving mDNS multicast group on
interface wlan0.IPv4 with address 169.254.7.238.
Jan 18 12:47:39 cotton avahi-daemon[5211]: Interface wlan0.IPv4 no longer
relevant for mDNS.
Jan 18 12:47:39 cotton NetworkManager: <info> eth0: Device is fully-supported
using driver 'tg3'.
Jan 18 12:47:39 cotton NetworkManager: <info> nm_device_init(): waiting for
device's worker thread to start
Jan 18 12:47:39 cotton /usr/sbin/cron[5341]: (CRON) INFO (Running @reboot jobs)
Jan 18 12:47:39 cotton NetworkManager: <info> nm_device_init(): device's
worker thread started, continuing.
Jan 18 12:47:39 cotton NetworkManager: <info> Now managing wired Ethernet
(802.3) device 'eth0'.
Jan 18 12:47:39 cotton NetworkManager: <info> Deactivating device eth0.
Jan 18 12:47:39 cotton avahi-daemon[5211]: Withdrawing address record for
169.254.2.90 on eth0.
Jan 18 12:47:39 cotton avahi-daemon[5211]: Leaving mDNS multicast group on
interface eth0.IPv4 with address 169.254.2.90.
Jan 18 12:47:39 cotton avahi-daemon[5211]: Interface eth0.IPv4 no longer
relevant for mDNS.
Jan 18 12:47:52 cotton NetworkManager: <debug> [1200678472.980887]
nm_hal_device_added(): New device added (hal udi is
'/org/freedesktop/Hal/devices/bluetooth_acl_7618d1961').
Jan 18 12:47:53 cotton hidd[5288]: New HID device 00:07:61:8D:19:61 (Logitech
(3) Button Mouse)
Jan 18 12:47:53 cotton NetworkManager: <debug> [1200678473.327136]
nm_hal_device_added(): New device added (hal udi is
'/org/freedesktop/Hal/devices/bluetooth_acl_7618d1961_logicaldev_input').
Jan 18 12:47:53 cotton kernel: input: Logitech (3) Button Mouse as
/class/input/input7
Jan 18 12:48:41 cotton NetworkManager: <info> Updating allowed wireless
network lists.
kbluetooth_auth_1234) registered
# Here's where I tried to get on the wireless network
Jan 18 12:49:54 cotton NetworkManager: <debug> [1200678594.168634]
nm_device_802_11_wireless_get_activation_ap(): Forcing AP '1087B'
Jan 18 12:49:54 cotton NetworkManager: <info> User Switch:
/org/freedesktop/NetworkManager/Devices/wlan0 / 1087B
Jan 18 12:49:54 cotton NetworkManager: <info> Deactivating device wlan0.
Jan 18 12:49:54 cotton dhcdbd: message_handler: message handler not found under
/com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.reason
Jan 18 12:49:54 cotton NetworkManager: <info> Device wlan0 activation
scheduled...
Jan 18 12:49:54 cotton NetworkManager: <info> Activation (wlan0) started...
Jan 18 12:49:54 cotton NetworkManager: <info> Activation (wlan0) Stage 1 of 5
(Device Prepare) scheduled...
Jan 18 12:49:54 cotton NetworkManager: <info> Activation (wlan0) Stage 1 of 5
(Device Prepare) started...
Jan 18 12:49:54 cotton NetworkManager: <info> Activation (wlan0) Stage 2 of 5
(Device Configure) scheduled...
Jan 18 12:49:54 cotton NetworkManager: <info> Activation (wlan0) Stage 1 of 5
(Device Prepare) complete.
Jan 18 12:49:54 cotton NetworkManager: <info> Activation (wlan0) Stage 2 of 5
(Device Configure) starting...
Jan 18 12:49:54 cotton NetworkManager: <info> Activation (wlan0/wireless):
access point '1087B' is encrypted, but NO valid key exists. New key needed.
Jan 18 12:49:54 cotton NetworkManager: <info> Activation (wlan0) New wireless
user key requested for network '1087B'.
Jan 18 12:49:54 cotton NetworkManager: <info> Activation (wlan0) Stage 2 of 5
(Device Configure) complete.
Jan 18 12:50:19 cotton NetworkManager: <info> Activation (wlan0) New wireless
user key for network '1087B' received.
Jan 18 12:50:19 cotton NetworkManager: <info> Activation (wlan0) Stage 1 of 5
(Device Prepare) scheduled...
Jan 18 12:50:19 cotton NetworkManager: <info> Activation (wlan0) Stage 1 of 5
(Device Prepare) started...
Jan 18 12:50:19 cotton NetworkManager: <info> Activation (wlan0) Stage 2 of 5
(Device Configure) scheduled...
Jan 18 12:50:19 cotton NetworkManager: <info> Activation (wlan0) Stage 1 of 5
(Device Prepare) complete.
Jan 18 12:50:19 cotton NetworkManager: <info> Activation (wlan0) Stage 2 of 5
(Device Configure) starting...
Jan 18 12:50:19 cotton NetworkManager: <info> Activation (wlan0/wireless):
access point '1087B' is encrypted, and a key exists. No new key needed.
Jan 18 12:50:20 cotton NetworkManager: <info> SUP: sending command
'INTERFACE_ADD wlan0^I^Iwext^I/var/run/wpa_supplicant^I'
Jan 18 12:50:21 cotton NetworkManager: <info> SUP: response was 'OK'
Jan 18 12:50:21 cotton NetworkManager: <info> SUP: sending command 'AP_SCAN 1'
Jan 18 12:50:21 cotton NetworkManager: <info> SUP: response was 'OK'
Jan 18 12:50:21 cotton NetworkManager: <info> SUP: sending command
'ADD_NETWORK'
Jan 18 12:50:21 cotton NetworkManager: <info> SUP: response was '0'
Jan 18 12:50:21 cotton NetworkManager: <info> SUP: sending command
'SET_NETWORK 0 ssid 3130383742'
Jan 18 12:50:21 cotton NetworkManager: <info> SUP: response was 'OK'
Jan 18 12:50:21 cotton NetworkManager: <info> SUP: sending command
'SET_NETWORK 0 proto WPA'
Jan 18 12:50:21 cotton NetworkManager: <info> SUP: response was 'OK'
Jan 18 12:50:21 cotton NetworkManager: <info> SUP: sending command
'SET_NETWORK 0 key_mgmt WPA-PSK'
Jan 18 12:50:21 cotton NetworkManager: <info> SUP: response was 'OK'
Jan 18 12:50:21 cotton NetworkManager: <info> SUP: sending command
'SET_NETWORK 0 psk <key>'
Jan 18 12:50:21 cotton NetworkManager: <info> SUP: response was 'OK'
Jan 18 12:50:21 cotton NetworkManager: <info> SUP: sending command
'ENABLE_NETWORK 0'
Jan 18 12:50:21 cotton NetworkManager: <info> SUP: response was 'OK'
Jan 18 12:50:21 cotton NetworkManager: <info> Activation (wlan0) Stage 2 of 5
(Device Configure) complete.
Jan 18 12:50:22 cotton kernel: wlan0: Initial auth_alg=0
Jan 18 12:50:22 cotton kernel: wlan0: authenticate with AP 00:18:4d:80:b6:24
Jan 18 12:50:22 cotton kernel: wlan0: RX authentication from 00:18:4d:80:b6:24
(alg=0 transaction=2 status=0)
Jan 18 12:50:22 cotton kernel: wlan0: authenticated
Jan 18 12:50:22 cotton kernel: wlan0: associate with AP 00:18:4d:80:b6:24
Jan 18 12:50:22 cotton kernel: wlan0: RX AssocResp from 00:18:4d:80:b6:24
(capab=0x411 status=0 aid=1)
Jan 18 12:50:22 cotton kernel: wlan0: associated
Jan 18 12:50:22 cotton kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes
ready
Jan 18 12:50:22 cotton kernel: wlan0: association frame received from
00:18:4d:80:b6:24, but not in associate state - ignored
Jan 18 12:50:22 cotton kernel: wlan0: CTS protection enabled
(BSSID=00:18:4d:80:b6:24)
Jan 18 12:50:24 cotton avahi-daemon[5211]: Registering new address record for
fe80::213:e8ff:fe8d:f71b on wlan0.*.
Jan 18 12:50:26 cotton kernel: wlan0: RX deauthentication from
00:18:4d:80:b6:24 (reason=15)
Jan 18 12:50:26 cotton kernel: wlan0: deauthenticated
Jan 18 12:50:27 cotton NetworkManager: <info> Old device 'wlan0' activating,
won't change.
Jan 18 12:50:27 cotton kernel: wlan0: authenticate with AP 00:18:4d:80:b6:24
Jan 18 12:50:27 cotton kernel: wlan0: RX authentication from 00:18:4d:80:b6:24
(alg=0 transaction=2 status=0)
Jan 18 12:50:27 cotton kernel: wlan0: authenticated
Jan 18 12:50:27 cotton kernel: wlan0: associate with AP 00:18:4d:80:b6:24
Jan 18 12:50:27 cotton kernel: wlan0: RX ReassocResp from 00:18:4d:80:b6:24
(capab=0x411 status=0 aid=1)
Jan 18 12:50:27 cotton kernel: wlan0: associated
Jan 18 12:50:31 cotton kernel: wlan0: RX deauthentication from
00:18:4d:80:b6:24 (reason=15)
Jan 18 12:50:31 cotton kernel: wlan0: deauthenticated
Jan 18 12:50:32 cotton kernel: wlan0: authenticate with AP 00:18:4d:80:b6:24
Jan 18 12:50:32 cotton kernel: wlan0: RX authentication from 00:18:4d:80:b6:24
(alg=0 transaction=2 status=0)
Jan 18 12:50:32 cotton kernel: wlan0: authenticated
Jan 18 12:50:32 cotton kernel: wlan0: associate with AP 00:18:4d:80:b6:24
Jan 18 12:50:32 cotton kernel: wlan0: RX ReassocResp from 00:18:4d:80:b6:24
(capab=0x411 status=0 aid=1)
Jan 18 12:50:32 cotton kernel: wlan0: associated
Jan 18 12:50:33 cotton kernel: wlan0: no IPv6 routers present
Jan 18 12:50:34 cotton NetworkManager: <info> Activation (wlan0/wireless):
disconnected during association, asking for new key.
Jan 18 12:50:34 cotton NetworkManager: <info> Activation (wlan0) New wireless
user key requested for network '1087B'.
Jan 18 12:50:36 cotton kernel: wlan0: RX deauthentication from
00:18:4d:80:b6:24 (reason=15)
Jan 18 12:50:36 cotton kernel: wlan0: deauthenticated
Jan 18 12:50:37 cotton kernel: wlan0: authenticate with AP 00:18:4d:80:b6:24
Jan 18 12:50:37 cotton kernel: wlan0: RX authentication from 00:18:4d:80:b6:24
(alg=0 transaction=2 status=0)
Jan 18 12:50:37 cotton kernel: wlan0: authenticated
Jan 18 12:50:37 cotton kernel: wlan0: associate with AP 00:18:4d:80:b6:24
Jan 18 12:50:37 cotton kernel: wlan0: RX ReassocResp from 00:18:4d:80:b6:24
(capab=0x411 status=0 aid=1)
Jan 18 12:50:37 cotton kernel: wlan0: associated
Jan 18 12:50:41 cotton kernel: wlan0: RX deauthentication from
00:18:4d:80:b6:24 (reason=15)
Jan 18 12:50:41 cotton kernel: wlan0: deauthenticated
Jan 18 12:50:42 cotton kernel: wlan0: authenticate with AP 00:18:4d:80:b6:24
Jan 18 12:50:42 cotton kernel: wlan0: RX authentication from 00:18:4d:80:b6:24
(alg=0 transaction=2 status=0)
Jan 18 12:50:42 cotton kernel: wlan0: authenticated
Jan 18 12:50:42 cotton kernel: wlan0: associate with AP 00:18:4d:80:b6:24
Jan 18 12:50:42 cotton kernel: wlan0: RX ReassocResp from 00:18:4d:80:b6:24
(capab=0x411 status=0 aid=1)
Jan 18 12:50:42 cotton kernel: wlan0: associated
Jan 18 12:50:44 cotton NetworkManager: <info> wlan0: link timed out.
Jan 18 12:50:46 cotton kernel: wlan0: RX deauthentication from
00:18:4d:80:b6:24 (reason=15)
Jan 18 12:50:46 cotton kernel: wlan0: deauthenticated
Jan 18 12:50:47 cotton kernel: wlan0: authenticate with AP 00:18:4d:80:b6:24
Jan 18 12:50:47 cotton kernel: wlan0: RX authentication from 00:18:4d:80:b6:24
(alg=0 transaction=2 status=0)
Jan 18 12:50:47 cotton kernel: wlan0: authenticated
Jan 18 12:50:47 cotton kernel: wlan0: associate with AP 00:18:4d:80:b6:24
Jan 18 12:50:47 cotton kernel: wlan0: RX ReassocResp from 00:18:4d:80:b6:24
(capab=0x411 status=0 aid=1)
Jan 18 12:50:47 cotton kernel: wlan0: associated
Jan 18 12:50:51 cotton kernel: wlan0: RX deauthentication from
00:18:4d:80:b6:24 (reason=15)
Jan 18 12:50:51 cotton kernel: wlan0: deauthenticated
Jan 18 12:50:52 cotton kernel: wlan0: authenticate with AP 00:18:4d:80:b6:24
Jan 18 12:50:52 cotton kernel: wlan0: RX authentication from 00:18:4d:80:b6:24
(alg=0 transaction=2 status=0)
Jan 18 12:50:52 cotton kernel: wlan0: authenticated
Jan 18 12:50:52 cotton kernel: wlan0: associate with AP 00:18:4d:80:b6:24
Jan 18 12:50:52 cotton kernel: wlan0: RX ReassocResp from 00:18:4d:80:b6:24
(capab=0x411 status=0 aid=1)
Jan 18 12:50:52 cotton kernel: wlan0: associated
Jan 18 12:50:54 cotton NetworkManager: <info> wlan0: link timed out.
Jan 18 12:50:56 cotton kernel: wlan0: RX deauthentication from
00:18:4d:80:b6:24 (reason=15)
Jan 18 12:50:56 cotton kernel: wlan0: deauthenticated
Jan 18 12:50:57 cotton kernel: wlan0: authenticate with AP 00:18:4d:80:b6:24
Jan 18 12:50:57 cotton kernel: wlan0: RX authentication from 00:18:4d:80:b6:24
(alg=0 transaction=2 status=0)
Jan 18 12:50:57 cotton kernel: wlan0: authenticated
Jan 18 12:50:57 cotton kernel: wlan0: associate with AP 00:18:4d:80:b6:24
Jan 18 12:50:57 cotton kernel: wlan0: RX ReassocResp from 00:18:4d:80:b6:24
(capab=0x411 status=0 aid=1)
Jan 18 12:50:57 cotton kernel: wlan0: associated
Jan 18 12:51:01 cotton kernel: wlan0: RX deauthentication from
00:18:4d:80:b6:24 (reason=15)
Jan 18 12:51:01 cotton kernel: wlan0: deauthenticated
Jan 18 12:51:02 cotton kernel: wlan0: authenticate with AP 00:18:4d:80:b6:24
Jan 18 12:51:03 cotton kernel: wlan0: authenticate with AP 00:18:4d:80:b6:24
Jan 18 12:51:03 cotton kernel: wlan0: RX authentication from 00:18:4d:80:b6:24
(alg=0 transaction=2 status=0)
Jan 18 12:51:03 cotton kernel: wlan0: authenticated
Jan 18 12:51:03 cotton kernel: wlan0: associate with AP 00:18:4d:80:b6:24
Jan 18 12:51:03 cotton kernel: wlan0: RX ReassocResp from 00:18:4d:80:b6:24
(capab=0x411 status=0 aid=1)
Jan 18 12:51:03 cotton kernel: wlan0: associated
Jan 18 12:51:04 cotton NetworkManager: <info> wlan0: link timed out.
Jan 18 12:51:07 cotton kernel: wlan0: RX deauthentication from
00:18:4d:80:b6:24 (reason=15)
Jan 18 12:51:07 cotton kernel: wlan0: deauthenticated
Jan 18 12:51:08 cotton kernel: wlan0: authenticate with AP 00:18:4d:80:b6:24
Jan 18 12:51:08 cotton kernel: wlan0: RX authentication from 00:18:4d:80:b6:24
(alg=0 transaction=2 status=0)
Jan 18 12:51:08 cotton kernel: wlan0: authenticated
Jan 18 12:51:08 cotton kernel: wlan0: associate with AP 00:18:4d:80:b6:24
Jan 18 12:51:08 cotton kernel: wlan0: RX ReassocResp from 00:18:4d:80:b6:24
(capab=0x411 status=0 aid=1)
Jan 18 12:51:08 cotton kernel: wlan0: associated
Jan 18 12:51:12 cotton kernel: wlan0: RX deauthentication from
00:18:4d:80:b6:24 (reason=15)
Jan 18 12:51:12 cotton kernel: wlan0: deauthenticated
Jan 18 12:51:13 cotton kernel: wlan0: authenticate with AP 00:18:4d:80:b6:24
Jan 18 12:51:13 cotton kernel: wlan0: RX authentication from 00:18:4d:80:b6:24
(alg=0 transaction=2 status=0)
Jan 18 12:51:13 cotton kernel: wlan0: authenticated
Jan 18 12:51:13 cotton kernel: wlan0: associate with AP 00:18:4d:80:b6:24
Jan 18 12:51:13 cotton kernel: wlan0: RX ReassocResp from 00:18:4d:80:b6:24
(capab=0x411 status=0 aid=1)
Jan 18 12:51:13 cotton kernel: wlan0: associated
Jan 18 12:51:15 cotton dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port
67 interval 7
Jan 18 12:51:15 cotton NetworkManager: <info> wlan0: link timed out.
Jan 18 12:51:17 cotton kernel: wlan0: RX deauthentication from
00:18:4d:80:b6:24 (reason=15)
Jan 18 12:51:17 cotton kernel: wlan0: deauthenticated
Jan 18 12:51:17 cotton NetworkManager: <info> Activation (wlan0) New wireless
user key for network '1087B' received.
Jan 18 12:51:17 cotton NetworkManager: <info> Activation (wlan0) Stage 1 of 5
(Device Prepare) scheduled...
Jan 18 12:51:17 cotton NetworkManager: <info> Activation (wlan0) Stage 1 of 5
(Device Prepare) started...
Jan 18 12:51:17 cotton NetworkManager: <info> Activation (wlan0) Stage 2 of 5
(Device Configure) scheduled...
Jan 18 12:51:17 cotton NetworkManager: <info> Activation (wlan0) Stage 1 of 5
(Device Prepare) complete.
Jan 18 12:51:17 cotton NetworkManager: <info> Activation (wlan0) Stage 2 of 5
(Device Configure) starting...
Jan 18 12:51:17 cotton NetworkManager: <info> Activation (wlan0/wireless):
access point '1087B' is encrypted, and a key exists. No new key needed.
Jan 18 12:51:18 cotton kernel: wlan0: authenticate with AP 00:18:4d:80:b6:24
Jan 18 12:51:18 cotton kernel: wlan0: RX authentication from 00:18:4d:80:b6:24
(alg=0 transaction=2 status=0)
Jan 18 12:51:18 cotton kernel: wlan0: authenticated
Jan 18 12:51:18 cotton kernel: wlan0: associate with AP 00:18:4d:80:b6:24
Jan 18 12:51:18 cotton kernel: wlan0: RX ReassocResp from 00:18:4d:80:b6:24
(capab=0x411 status=0 aid=1)
Jan 18 12:51:18 cotton kernel: wlan0: associated
Jan 18 12:51:18 cotton NetworkManager: <info> SUP: sending command
'INTERFACE_ADD wlan0^I^Iwext^I/var/run/wpa_supplicant^I'
Jan 18 12:51:20 cotton NetworkManager: <info> SUP: response was '°äØ·°äØ·(K
^H(K'
Jan 18 12:51:20 cotton NetworkManager: <WARN>
nm_utils_supplicant_request_with_check(): supplicant_interface_init: supplicant
error for 'INTERFACE_ADD wlan0^I^Iwext^I/var/run/wpa_supplicant^I'. Response:
'°äØ·°äØ·(K'
Jan 18 12:51:20 cotton NetworkManager: <WARN> real_act_stage2_config():
Activation (wlan0/wireless): couldn't connect to the supplicant.
Jan 18 12:51:20 cotton NetworkManager: <info> Activation (wlan0) failure
scheduled...
Jan 18 12:51:20 cotton NetworkManager: <info> Activation (wlan0) Stage 2 of 5
(Device Configure) complete.
Jan 18 12:51:20 cotton NetworkManager: <info> Activation (wlan0) failed for
access point (1087B)
Jan 18 12:51:20 cotton NetworkManager: <info> Activation (wlan0) failed.
Jan 18 12:51:20 cotton NetworkManager: <info> Deactivating device wlan0.
Jan 18 12:51:22 cotton dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port
67 interval 16
Jan 18 12:51:38 cotton dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port
67 interval 10
Jan 18 12:51:48 cotton dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port
67 interval 10
Jan 18 12:51:58 cotton dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port
67 interval 9
Jan 18 12:52:07 cotton dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port
67 interval 9
Jan 18 12:52:16 cotton dhclient: No DHCPOFFERS received.
Jan 18 12:52:16 cotton dhclient: No working leases in persistent database -
sleeping.
Jan 18 12:52:39 cotton anacron[5324]: Job `cron.daily' started
Jan 18 12:52:39 cotton anacron[6956]: Updated timestamp for job `cron.daily' to
2008-01-18
Jan 18 12:54:16 cotton dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port
67 interval 7
Jan 18 12:54:23 cotton dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port
67 interval 9
# many more dhcp entries
# here's where I tried to shut down
Jan 18 14:13:09 cotton shutdown[9943]: shutting down for system halt
Jan 18 14:13:09 cotton init: Switching to runlevel: 0
Jan 18 14:14:38 cotton shutdown[9956]: shutting down for system halt
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.22-3-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages network-manager-kde depends on:
ii kdelibs4c2a 4:3.5.8.dfsg.1-4 core libraries and binaries for al
ii libc6 2.7-5 GNU C Library: Shared libraries
ii libdbus-1-3 1.1.2-1 simple interprocess messaging syst
ii libdbus-qt-1-1c2 0.62.git.20060814-2 simple interprocess messaging syst
ii libgcc1 1:4.2.2-4 GCC support library
ii libglib2.0-0 2.14.3-1 The GLib library of C routines
ii libhal1 0.5.10-5 Hardware Abstraction Layer - share
ii libice6 2:1.0.4-1 X11 Inter-Client Exchange library
ii libnl1-pre6 1.0~pre6-5 Library for dealing with netlink s
ii libnm-util0 0.6.5-3 network management framework (shar
ii libpng12-0 1.2.15~beta5-3 PNG library - runtime
ii libqt3-mt 3:3.3.7-9 Qt GUI Library (Threaded runtime v
ii libsm6 2:1.0.3-1+b1 X11 Session Management library
ii libstdc++6 4.2.2-4 The GNU Standard C++ Library v3
ii libx11-6 2:1.0.3-7 X11 client-side library
ii libxext6 1:1.0.3-2 X11 miscellaneous extension librar
ii network-manager 0.6.5-3 network management framework daemo
ii zlib1g 1:1.2.3.3.dfsg-8 compression library - runtime
Versions of packages network-manager-kde recommends:
ii kwalletmanager 4:3.5.8-1 wallet manager for KDE
ii network-manager-openvpn 0.3.2svn2855-1 network management framework (Open
ii network-manager-vpnc 0.6.4svn2806-1 network management framework (VPNC
-- no debconf information
--- End Message ---
--- Begin Message ---
On 19.01.2008 03:42, Ross Boylan wrote:
> Package: network-manager-kde
> Version: 1:0.2-2
> Severity: normal
>
> This bug reports a severe, but not reproducible, problem. Given the
> severity, and the resemblance to some existing bugs, I thought it
> would be useful to report anyway. I am quite unsure what package is
> the ultimate cause of the problem.
>
> After using knetworkmanager to turn on a wireless network
> 1) the icon for knetworkmanager disappeared from the kicker
> 2) the kicker itself stopped being painted and responding
> 3) when I tried to shut the system down, with shutdown -r now, it
> would not shut down and I had to power off.
knm has been rewritten completely and we also don't have kicker anymore, so I
assume this bug is no valid, thus closing.
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-extras
