[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#257895: marked as done (kwifimanager issues wrong wireless requests)

Your message dated Tue, 27 Mar 2007 09:48:06 -0400
with message-id <9f694b820703270648k4d22d476gbe3befb68b17691e@mail.gmail.com>
and subject line very old bug, do yuo still have the problem ?
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: kwifimanager
Version: 4:3.2.2-1

I'd like to use kwifimanager to manage the configurations of different
Wireless Networks. However something goes wrong when kwifimanger passes
parameters to the driver. I'm getting the error message

Error for wireless request "Set Encode" (8B2A) :
    invalid argument "key".

when I click Apply or Activate Configuration in the Configuration Editor.
When I switch cryptography off the message is

Error: unrecognised wireless request "auto"

and with the speed set to 2 MBit/s the error is, guess what:

Error: unrecognised wireless request "2M"

Finally with power management enabled it is:

Error for wireless request "Set Power Management" (8B2C) :
    invalid argument "power".

I can see these messages in the terminal from which I start kwifimanager as
root.

I'm using the orinico drivers that come with the 2.4.25-1-386 kernel of the
Debian testing distribution. I can configure the wireless link with iwconfig
(wireless-tools 26/27pre22-1) and the kwifimanager Main Window reports
changes in link status correctly.

--- End Message ---
--- Begin Message --- 
Submitter was asked to provide more information about this bug
( http://bugs.debian.org/257895 ) four weeks ago.

Since more info was not provided, we are closing the bug.
Feel free to reopen this bug if you are still experiencing this issue
and you have extra information on how reproduce the issue.

Thanks,
Olivier

--- End Message ---
Reply to: