swscanner with rausb driver crashes (feisty)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
swscanner (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: swscanner
Since installing Feisty (Kubuntu), swscanner is completely broken, at least when used with the ralink driver rt2500 (rausb device).
It returns this:
"Error in SIOCSIWMODE: Operation not permitted
Warning: Driver for device rausb1 has been compiled with version 21
of Wireless Extension, while this program supports up to version 17.
Some things may be broken..."
The full output is (similar when ran as root too):
creaphot@
[1] 20332
creaphot@
Creating aplist...
Creating SWSconfig...
Creating MainWindow...
Creating gpserial...
Creating SWSystemTray...
if(lo)-
Creating scanning thread...
Error in SIOCSIWMODE: Operation not permitted
Warning: Driver for device rausb1 has been compiled with version 21
of Wireless Extension, while this program supports up to version 17.
Some things may be broken...
if(rausb1)
(27)
if(rausb1)
(49)
Error in SIOCSIFFLAGS: Permission denied
if(rausb1)
(60)
Starting a new scan thread!!
rausb1 Scan completed :
New AP found(01): 5E:58:A5:A6:97:F8
KCrash: Application 'swscanner' crashing...
QSocketNotifier: invalid socket 8 and type 'Read', disabling...
QSocketNotifier: invalid socket 4 and type 'Read', disabling...
if(rausb1)
(60)
QFile::at: Cannot set file position 0
if(rausb1)
(60)
if(rausb1)
(60)
if(rausb1)
(20)
if(rausb1)
(20)
if(rausb1)
(20)
swscanner: Fatal IO error: client killed
creaphot@
The backtrace:
(no debugging symbols found)
Using host libthread_db library "/lib/tls/
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1233099056 (LWP 20396)]
[New Thread -1239151728 (LWP 20410)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xb70391c4 in QPostEventListI
from /usr/lib/
#0 0xb70391c4 in QPostEventListI
from /usr/lib/
#1 0xb703186e in QApplication:
#2 0xb7031ba0 in QApplication:
#3 0xb6fd70dd in QEventLoop:
#4 0xb704b136 in QEventLoop:
#5 0xb704af46 in QEventLoop::exec () from /usr/lib/
#6 0xb7032609 in QApplication::exec () from /usr/lib/
#7 0x0805b502 in ?? ()
#8 0x080c07a8 in ?? ()
#9 0x080f66e0 in ?? ()
#10 0x00000001 in ?? ()
#11 0x00000000 in ?? ()
Same problem here on Feisty. The website has a note about the program crashing in Ubuntu 7.10
http:// www.swscanner. org/en/ taxonomy/ term/20+ 21