sws scanner crash whend launch wifi scan

Bug #99225 reported by toasty
This bug report is a duplicate of:  Bug #109753: [Lucid] SWScanner crashes. Edit Remove
6
Affects Status Importance Assigned to Milestone
swscanner (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: swscanner

Cette pile des appels apparaît être inutilisable.
C'est probablement dû au fait que votre paquetage a été construit d'une manière qui empêche de créer des piles d'appels corrects, ou que le cadre de pile a été sérieusement corrompu dans l'incident.

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

ProblemType: Bug
Architecture: i386
Date: Sat Mar 31 01:25:16 2007
DistroRelease: Ubuntu 7.04
Uname: Linux pioumeow 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux

Revision history for this message
Ezazazel (ezazazel) wrote : Can confirm crashing SWScaner in 7.04
Download full text (4.3 KiB)

Can confirm that Feisty always crashes when starting Scan.
Am using the restricted module Atheros Hardware Access Layer (HAL).
Worked fine in Edgy with self compiled MADWIFI Drivers.

ProblemType: Bug
Architecture: i386
Date: 02042007
DistroRelease: Ubuntu 7.04

Here's the bug report:
(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
..
(no debugging symbols found)
..
[Thread debugging using libthread_db enabled]
[New Thread -1233037616 (LWP 6439)]
[New Thread -1238135920 (LWP 6454)]
...
(no debugging symbols found)
...
0xb73a5237 in QGListIteratorList::add () from /usr/lib/libqt-mt.so.3
#0 0xb73a5237 in QGListIteratorList::add () from /usr/lib/libqt-mt.so.3
#1 0xb73a3e9b in QGListIterator::QGListIterator () from /usr/lib/libqt-mt.so.3
#2 0xb70470b2 in QPtrListIterator<QPostEvent>::QPtrListIterator ()
   from /usr/lib/libqt-mt.so.3
#3 0xb70470dc in QPostEventListIt::QPostEventListIt ()
   from /usr/lib/libqt-mt.so.3
#4 0xb703f88c in QApplication::sendPostedEvents () from /usr/lib/libqt-mt.so.3
#5 0xb703fb28 in QApplication::sendPostedEvents () from /usr/lib/libqt-mt.so.3
#6 0xb6fe50dd in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#7 0xb70590be in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#8 0xb7058ece in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#9 0xb7040591 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#10 0x0805b502 in ?? ()
#11 0x080c07a8 in ?? ()
#12 0x080feca8 in ?? ()
#13 0x00000001 in ?? ()
#14 0x00000000 in ?? ()

Some more Info from the Terminal:
 sudo swscanner
X Error: BadDevice, invalid or uninitialized input device 170
  Major opcode: 148
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 170
  Major opcode: 148
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 170
  Major opcode: 148
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 170
  Major opcode: 148
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
kbuildsycoca running...
Running SWScanner version: 0.2.2
Creating aplist...
Creating SWSconfig...
Creating MainWindow...
Creating gpserial...
Creating SWSystemTray...
if(lo)->127.0.0.1/255.0.0.0/0.0.0.0#### level: -65 noise: -208 (140)
Creating scanning thread...

Creating frmconfig...
Tables found: networks
Tables found: networks
Deleting frmconfig...
Deleting SWSconfig...
if(lo)->127.0.0.1/255.0.0.0/0.0.0.0#### level: -74 noise: -256 (232)
if(lo)->127.0.0.1/255.0.0.0/0.0.0.0#### level: -248 noise: -172 (30)
if(lo)->127.0.0.1/255.0.0.0/0.0.0.0#### level: -248 noise: -96 (30)
Warning: Driver for device ath0 has been compiled with version 21
of Wireless Extension, while this program supports up to version 17.
Some things may be broken...

if(ath0)->192.168.1.3/255.255.255.0/192.168.1.255#### level: -64 noise: -90 (26)
if(ath0)->192.168.1.3/25...

Read more...

Revision history for this message
ASF (antonio-fonseca) wrote :

Can confirm too that swscan always crash in Feisty when starting scan. I'm using Dell Latitude D610 with ipw2200 (Intel) wireless card. It worked fine with Edgy.

Architecture: i386
Date: April, 22 2007
DistroRelease: Ubuntu 7.04

Here is the generated KDE Crash Handler Backtrace log:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(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 -1232800048 (LWP 6805)]
[New Thread -1237951600 (LWP 6819)]
(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)
0xb6af885a in __pthread_mutex_unlock_usercnt ()
   from /lib/tls/i686/cmov/libpthread.so.0
#0 0xb6af885a in __pthread_mutex_unlock_usercnt ()
   from /lib/tls/i686/cmov/libpthread.so.0
#1 0xb6af8bf0 in pthread_mutex_unlock ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb73c0236 in QRecursiveMutexPrivate::lock () from /usr/lib/libqt-mt.so.3
#3 0xb73bfd4e in QMutex::lock () from /usr/lib/libqt-mt.so.3
#4 0xb70211ca in QMutexLocker::QMutexLocker () from /usr/lib/libqt-mt.so.3
#5 0xb707a8a6 in QApplication::sendPostedEvents ()
   from /usr/lib/libqt-mt.so.3
#6 0xb707a86e in QApplication::sendPostedEvents ()
   from /usr/lib/libqt-mt.so.3
#7 0xb707aba0 in QApplication::sendPostedEvents ()
   from /usr/lib/libqt-mt.so.3
#8 0xb70200dd in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#9 0xb7094136 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#10 0xb7093f46 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#11 0xb707b609 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#12 0x0805b502 in ?? ()
#13 0x080c07a8 in ?? ()
#14 0x080fd000 in ?? ()
#15 0x00000001 in ?? ()
#16 0x00000000 in ?? ()

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.