Bug#309279: whereami: ESSID problems with testap/testssid
Package: whereami
Version: 0.3.20
Severity: normal
found a number of problems with testap/testssid:
- iwlist wlan0 scan sometimes misses the net I am looking for.
- IDs including a space like wireless Extreme can only be passed to
testap using a wildcard pattern, but then the scan problem kicks in, and
it looks as if then the wildcard pattern is used as ESSID.
I was able to change the network id as a workaround.
- My wlan interface requires a
iwconfig ${INTERFACE} essid on
before
iwconfig ${INTERFACE} essid ${ESSID}
in the testap and testssid scripts to work, or else the essid will
not be set.
I changed the tests accordingly and then they worked.
Hardware: Dell Inspiron 5150 with Broadcom BCM4306 miniPCI WLAN
controller and ndiswrapper driver
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.11.7
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15)
Versions of packages whereami depends on:
ii debconf 1.4.49 Debian configuration management sy
ii dhcp-client 2.0pl5-19.1 DHCP Client
ii fping 2.4b2-to-ipv6-10 sends ICMP ECHO_REQUEST packets to
ii netbase 4.21 Basic TCP/IP networking system
ii perl5.8.4-8 Larry Wall's Practical Extraction
-- debconf information:
* whereami/how_to_configure:
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#309279: whereami: ESSID problems with testap/testssid
On Mon, 16 May 2005, Andrew McMillan wrote: - iwlist wlan0 scan sometimes misses the net I am looking for. There is unfortunately nothing I can do about that unless you can provide me with some guidelines about how it can be reliable. For example, in my own case, iwlist ... scan always fails unless I ifconfig ... down; sleep 4; ifconfig ... up first. Bizarre, but it works :-) I think it might have something to do with how long it scans on each channel, but I am not really sure about that. We have a very rich WLAN environment here, with at least 4 different networks on air all the time, so perhaps that influences the scan somehow. The man page for iwlist says something about the driver configuration influencing the scan, so I guess it might depend on the threshold values in iwconfig nad perhaps some other things, but I would have to examine that in detail to get any meaningful results. The point is though that I can only make these sorts of empirical observations about hardware I have access to. If you can work out any further details regarding this, can you please create a new bug report with what you've discovered. ok, this may take a while. - IDs including a space like wireless Extreme can only be passed to testap using a wildcard pattern, but then the scan problem kicks in, and it looks as if then the wildcard pattern is used as ESSID. I was able to change the network id as a workaround. There is supposed to be code in testap to handle this, and I can't see where it's going wrong. If you are able to duplicate the problem for me can you file a new bug, and provide the output of whereami --scriptdebug, to assist me in solving it. Send that to me privately if you are worried about exposing it to the world! well, the first problem is that I can't simply put the ESSID in detect.conf, since all behind the space is then recognized as a target token. If I put quotes around the id, the egrep statement gets syntax errors. If I put in a wildcard, the scan fails and the ESSID does not get set. So maybe changing the detect.conf syntax to include quotes around the ESSID would be the easiest way, especially since it is a bit difficult to get information about what might be a valid ESSID string. I did a quick web survey and did not find anything, so I guess all sorts of non-alphanumeric characters could be allowed. But I'll do a test run with a space-included ESSID later and send you the results. -- peter koellner [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#307844: xlibs: xkb int'l keyboard modifiers broken since last update
I checked today that the /etc/X11/xkb directory really was updated from xlibs 4.3.0-dfsg.1--1.12 and removed any non-standard options from the XF86Config-4 file, and the keyboard map seems to be ok. @ and euro sign work, even in the gdm login screen, which they did not yesterday. The only problem remaining is that AltGr does not work as expected from the secondary russian keyboard, but I can live with that. Now I only wonder how it is possible that there are two incompatible sets of X-Windows packages, having identical names and only distinguishable by their version number when installed. I think there should be some mechanism to avoid cross-updating such packages in case of a source provider clash. But that is a different issue. thanks -- peter koellner [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#308066: trying to install libx11-dev leads to major package dependency problems
On Sun, 8 May 2005, Daniel Stone wrote: On Sat, May 07, 2005 at 06:30:20PM +0200, Peter Koellner wrote: I was trying to install the GNOME 2.10 garnome suite when I discovered that I did not yet have the X development libraries installed on my system. So I started dselect to get them. When I select libx11-dev, dselect gives me a report of dependency problems that breaks the whole desktop configuration, by wanting to deinstall libxkbui1, libxkbfile1, ^ ^^^ Are you using Ubuntu's X.Org packages, or Debian's XFree86 packages? I just went to the ubuntu website too see what it actually is. I don't think so. At one point about one and a half year ago I installed a debian XFree86 4.3.0 backport because I needed the new Radeon drivers for my laptop, but I don't have the package source any more. I am pretty sure that it was from a debian.org server. But your question indicates that there might be something very wrong with the package dependencies on my machine only, perhaps due to a pollution from some temporarily used package source. So I am going to deinstall the whole gnome/X environment, reinstall with a clean apt/sourcelist and see what happens. I'll come back in a few hours and report the results... -- peter koellner [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#308066: dependency problems gone - but maybe a different issue?
ok, it seems that I overestimated the stability and relyability of the debian package management system somehow. I always thought that package list updates would overrule ancient dependencies, but obviously there are certain problems that could not be fixed automatically. I still don't have any idea how I catched those Ubuntu dependencies, or when. After deinstalling gdm and a whole bunch of other packages I was able to reinstall them without dependency problems. I would feel much better if I knew the reason for the problems. This computer is used very intensely for all sorts of development work, so from time to time I depend on installing more exotic software packages from outer sources. Now my theory is that somewhere out there there also were some non-standard X packages that happened to have a version number higher than what I had installed (for example, xbase-client version 6.4.2 instead of 4.3.0-xxx) and slipped in with some other update I intended to make, and which I did not recognize because I could not see from which source this package would come. Thinking about it, this might be a fairly high security risk, because I could offer my own debian package source location for my own project and sneak e.g. gnupg version 3.0.3 into my package list. Well, I don't know enough about the packaging system, but maybe this would be worth investigating further. -- peter koellner [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#307844: xlibs: xkb int'l keyboard modifiers broken since last update
On Sun, 8 May 2005, Denis Barbier wrote: tags 307844 + unreproducible severity 307844 normal thanks According to your other posts, you had non-Debian packages installed. Could you please check that XKB works fine with pristine Debian packages? Well, I guess the two problems are connected. I am thinking of a least destructive method to make sure only Debian packages are installed, which is a bit difficult since I don't really know where the other packages came from and how to tell them apart. I guess that now that these libxkb* packages are gone reinstalling xbase-clients or xlibs should suffice. I'll clean up the installation and report back later. Thanks for the support everybody. -- peter koellner [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#308066: trying to install libx11-dev leads to major package dependency problems
Package: libx11-dev Version: catastrophic dependency problem Severity: important I was trying to install the GNOME 2.10 garnome suite when I discovered that I did not yet have the X development libraries installed on my system. So I started dselect to get them. When I select libx11-dev, dselect gives me a report of dependency problems that breaks the whole desktop configuration, by wanting to deinstall libxkbui1, libxkbfile1, xbase-cient, libgksuui1.0, xprint-common, wine, gdm, xprint, wine-utils, python-2.3-common, and several more. This is serious, since it renders my laptop useless for all X development purposes. dselect screen copy of dependency problems: _* Opt libdevel xlibs-static X Window System client library development files _* Opt libdevel libxv-devX Window System video extension library developme ** Opt libdevel libx11-dev X Window System protocol client library developme **- Opt libs libxkbui1 **- Opt libs libxkbfile1 _* Opt libdevel libxi-devX Window System Input extension library developme **- Opt x11 xbase-client miscellaneous X clients **- Opt libs libgksuui1.0 a graphical fronted to su library **- Opt x11 xprint-commo Xprint - the X11 print system (configuration file **- Opt libs libgksu1.2-0 library providing su and sudo functionality **- Opt otherosf wine Windows Emulator (Binary Emulator) **- Opt gnomegdm GNOME Display Manager **- Opt admingksu graphical frontend to su **- Opt x11 xprint Xprint - the X11 print system (binary) **- Opt otherosf wine-utils Windows Emulator (Utilities) **- Opt gnomegdm-themes Themes for the GNOME Display Manager **- Opt gnomegnome-sudo dumb package to provide smooth upgrade to gksu **- Opt libs python2.3-co alternative debconf configuration interface: core **- Opt x11 xprt-xprinto Xprint - the X11 print system (dummy) **- Opt python python-confi alternative debconf configuration interface: core -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.11.7 Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15) Versions of packages libx11-dev depends on: ii libc6-dev [libc-dev] 2.3.2.ds1-21GNU C Library: Development Librari ii libx11-6 4.3.0.dfsg.1-12.0.1 X Window System protocol client li ii libxext-dev 4.3.0.dfsg.1-12.0.1 X Window System miscellaneous exte pn libxi-devNot found. ii x-dev4.3.0.dfsg.1-12 X protocol development files pn xlibs-static-dev Not found. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#307844: workaround
As a quick workaround I installed the new xkb configuration files from XFree86 4.5.0. It seems to work better now, except that I still can't access the AltGr-Level from the russian keyboard layout. -- peter koellner [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#307844: xlibs: xkb int'l keyboard modifiers broken since last update
Package: xlibs Version: 4.3.0.dfsg.1-12 Severity: important since my last update of debian unstable the AltGr keyboard modification is broken. I tried for several days now to even pinpoint the problem, looking through related bug reports, trying different keyboard layout options, but nothing helps. The 'at' has vanished from AltGr-q, and the Eurosign is gone from AltGr-e. The best I can do is to do a setxkbmap -rules xfree86 -model pc105 latin+de basic complete and then I get @ and ยค on toggling LeftWin, but my additional russian keyboard layout is gone then. I have no idea which of the configuration files to look at here, and the gnome keyboard preferences do not help at all. I can install german and russian layouts there, but then I have no 'at' anywhere on the keyboard. noisydwarf[501] xprop -root | grep XKB _XKB_RULES_NAMES_BACKUP(STRING) = xfree86, pc105, de,ru, basic,winkeys, lv3:ralt_switch,grp:lwin_toggle _XKB_RULES_NAMES(STRING) = xfree86, pc105, de,ru, basic,winkeys, lv3:ralt_switch,grp:lwin_toggle noisydwarf[502] gconftool-2 -R /desktop/gnome/peripherals/keyboard/xkb layouts = [de basic,ruwinkeys] model = pc105 overrideSettings = false options = [lv3 lv3:ralt_switch,grp grp:lwin_toggle] update_handlers = [] -- xev output on pressing AltGr-q: KeyPress event, serial 28, synthetic NO, window 0x2e1, root 0x48, subw 0x0, time 3157881, (98,45), root:(111,99), state 0x0, keycode 113 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 33, synthetic NO, window 0x2e1, root 0x48, subw 0x0, time 3158673, (98,45), root:(111,99), state 0x80, keycode 24 (keysym 0x71, q), same_screen YES, XLookupString gives 1 bytes: (71) q XmbLookupString gives 1 bytes: (71) q XFilterEvent returns: False -- Package-specific info: Keyboard-related contents of XFree86 X server log file /var/log/XFree86.0.log: (==) Using config file: /etc/X11/XF86Config-4 (==) ServerLayout Default Layout (**) |--Screen Default Screen (0) (**) | |--Monitor Dell LCD 1600x1200 (**) | |--Device ATI Radeon Mobility 9000 (**) |--Input Device Generic Keyboard (**) |--Input Device Configured Mouse (**) |--Input Device Touchpad (**) FontPath set to unix/:7100,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/CID,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/cyrillic,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/75dpi (==) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules -- (II) Loading /usr/X11R6/lib/modules/drivers/ati_drv.o (II) Module ati: vendor=The XFree86 Project compiled for 4.3.0.1, module version = 6.5.5 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.6 (II) LoadModule: kbd (II) Loading /usr/X11R6/lib/modules/input/kbd_drv.o (II) Module kbd: vendor=The XFree86 Project compiled for 4.3.0.1, module version = 1.0.0 Module class: XFree86 XInput Driver ABI class: XFree86 XInput driver, version 0.4 (II) LoadModule: mouse (II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o -- (II) RADEON(0): Direct rendering enabled (==) RandR enabled (II) Initializing built-in extension MIT-SHM (II) Initializing built-in extension XInputExtension (II) Initializing built-in extension XTEST (II) Initializing built-in extension XKEYBOARD (II) Initializing built-in extension LBX (II) Initializing built-in extension XC-APPGROUP (II) Initializing built-in extension SECURITY (II) Initializing built-in extension XINERAMA (II) Initializing built-in extension XFree86-Bigfont (II) Initializing built-in extension RENDER (II) Initializing built-in extension RANDR (**) Option CoreKeyboard (**) Generic Keyboard: Core Keyboard (**) Option Protocol standard (**) Generic Keyboard: Protocol: standard (**) Option AutoRepeat 500 30 (**) Option XkbRules xfree86 (**) Generic Keyboard: XkbRules: xfree86 (**) Option XkbModel pc105 (**) Generic Keyboard: XkbModel: pc105 (**) Option XkbLayout de,ru (**) Generic Keyboard: XkbLayout: de,ru (**) Option XkbVariant basic,winkeys (**) Generic Keyboard: XkbVariant: basic,winkeys (**) Option XkbOptions lv3:ralt_switch,grp:lwin_toggle (**) Generic Keyboard: XkbOptions: lv3:ralt_switch,grp:lwin_toggle (**) Option CustomKeycodes off (**) Generic Keyboard: CustomKeycodes disabled (**) Option Protocol Auto (**) Configured Mouse: Protocol: Auto (**) Option CorePointer (**) Configured Mouse: Core Pointer (**) Option Device /dev/input/mice -- (**) Option Emulate3Buttons true (**) Touchpad: Emulate3Buttons, Emulate3Timeout: 50 (==) Touchpad: Buttons: 3 (II) XINPUT: Adding extended input device Touchpad (type: MOUSE) (II) XINPUT: Adding extended input device Configured Mouse (type: MOUSE) (II) XINPUT: Adding extended input device Generic Keyboard (type: KEYBOARD) (--) Configured Mouse: PnP-detected protocol: ExplorerPS/2 (II) Configured Mouse:
