Your message dated Thu, 10 Jul 2008 22:32:00 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#490218: "Bug" solved :-(
has caused the Debian Bug report #490218,
regarding network-manager-kde: does not see wireless device
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 [EMAIL PROTECTED]
immediately.)
--
490218: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490218
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: network-manager-kde
Version: 1:0.2.2-1
Severity: normal
(I'm not sure whether this bug is in network-manager-kde: could be in
wpasupplicant, or elsewhere.)
When started, KNetworkManager finds the wired device, but not the wireless
device. (KWifiManager and command line find it and work OK with it -
currently I use them; that's why I suspect wpasupplicant could be guilty, too -
V0.6.3-2.)
Situation:
Newly reinstalled (from scratch) laptop ASUS X51R-AP140. Before the reinstall
KNetworkManager worked OK. (I remember it needed some tinkering when
I installed it first, but could not recall the details.)
Reinstall started with a network CD for Etch, standard system only, then
dist-upgraded to Lenny/Sid, and added the rest. Installed MadWiFi for my
Atheros-based card (m-a a-i madwifi).
Added my user to the netdev group. Read network-manager/README.Debian. Tried
installing and removing the recommended packages.
My /etc/network/inerfaces:
---
# The loopback network interface
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0
auto eth0
iface eth0 inet dhcp
auto ath0
iface ath0 inet dhcp
---
If more info is needed, please ask.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.25-2-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.9.dfsg.1-6 core libraries and binaries for al
ii libc6 2.7-12 GNU C Library: Shared libraries
ii libdbus-1-3 1.2.1-2 simple interprocess messaging syst
ii libdbus-qt-1-1c2 0.62.git.20060814-2 simple interprocess messaging syst
ii libgcc1 1:4.3.1-6 GCC support library
ii libhal1 0.5.11-2 Hardware Abstraction Layer - share
ii libice6 2:1.0.4-1 X11 Inter-Client Exchange library
ii libnl1 1.1-2 library for dealing with netlink s
ii libnm-util0 0.6.6-2 network management framework (shar
ii libpng12-0 1.2.27-1 PNG library - runtime
ii libqt3-mt 3:3.3.8b-5 Qt GUI Library (Threaded runtime v
ii libsm6 2:1.0.3-2 X11 Session Management library
ii libstdc++6 4.3.1-6 The GNU Standard C++ Library v3
ii libx11-6 2:1.1.4-2 X11 client-side library
ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar
ii network-manager 0.6.6-2 network management framework daemo
ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime
Versions of packages network-manager-kde recommends:
pn kwalletmanager <none> (no description available)
pn network-manager-openvpn <none> (no description available)
pn network-manager-vpnc <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
Quoting Grigor Gatchev <[EMAIL PROTECTED]>:
Found the problem. For unknown reason, the wpa_supplicant executable was only
several K long. Reinstalled the package, and things went smoothly.
(Sorry for the trouble. I lost two days on experimenting before sending the
report, but only after that got the idea to inspect the executables.)
No problem.
Thanks for reporting back, that the problem is now fixed.
Closing the bug report.
Cheers,
Michael
P.S: There is a nice tool called debsums, which might help you in the
future to detect such problems easier.
------------------------------------------------------------
This mail was sent through TecO-Webmail: http://www.teco.edu
--- End Message ---
