Knemo does not report wireless link quality information for drivers that use a "=" to seperate the measurement and the label as opposed to a ":". The regular expression that parses this part of the iwconfig output incorrectly assumes the former. This leads to link quality information not being reported on at least ipw2x00-driven cards. A patch will be attached that fixes this problem. The bug has been reported upstream. Reproducible: Always Steps to Reproduce: 1. 'emerge =net-misc/knemo-0.3.1' 2. Set up knemo for a wireless interface using a driver that fits the above description. 3. Open the interface status dialog. 4. Switch to the 'Wireless' tab. Link quality is not reported. Actual Results: Link Quality was not reported. Expected Results: iwconfig output should have been parsed differently. Portage 2.0.51.19 (default-linux/x86/2004.3, gcc-3.4.3-20050110, glibc-2.3.4.20040808-r1, 2.6.11.6 i686) ================================================================= System uname: 2.6.11.6 i686 Intel(R) Pentium(R) 4 CPU 2.20GHz Gentoo Base System version 1.6.9 Python: dev-lang/python-2.3.4 [2.3.4 (#1, Oct 24 2004, 04:58:11)] distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.4 [enabled] dev-lang/python: 2.3.4 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4 sys-devel/binutils: 2.14.90.0.8-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=i686 -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=i686 -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distcc distlocks prelink sandbox sfperms" GENTOO_MIRRORS="http://gentoo.mirrors.tds.net/gentoo http://adelie.polymtl.ca/ http://gentoo.mirrors.pair.com/ http://mirror.datapipe.net/gentoo" MAKEOPTS="-j6" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://server.oakcourt.local/gentoo-portage" USE="x86 X acpi alsa arts avi bash-completion berkdb bitmap-fonts cdr crypt cups curl dbus dvdr emboss encode esd fam flac font-server foomaticdb fortran gdbm gif gphoto2 gpm gstreamer hal howl imagemagick imlib java jpeg junit kde libg++ libwww mad mikmod mmx motif mp3 mpeg ncurses nls odbc oggvorbis opengl pam pdflib perl png python qt quicktime readline samba scanner sdl slang snmp spell sse ssl svga tcltk tcpd tetex tiff truetype truetype-fonts type1-fonts xml2 xmms xv zeroconf zlib" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS
Created attachment 55925 [details] Patch that fixes described problem The following patch against knemo 0.3.1 fixes the problem described in the bug report.
If it is going to be included in 0.3.2, I think we can wait for that release, or is the patch critical for knemo functionality?
Definitely not critical, but as I have not heard back from the author yet, and 0.3.1 has been out for some months, I don't even know if there's going to /be/ an 0.3.2. I'll be sure to say something here if I do.
doesn't harm, committed
