OESF Portables Forum

Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Sharp ROMs => Topic started by: cmpayc on March 15, 2005, 04:16:59 am

Title: Kismet Client: Segmentation Fault
Post by: cmpayc on March 15, 2005, 04:16:59 am

Hi All,

I installed Kismet 2005-01-R1 from the feed on Cacko 1.22a and can't get it running.
The Kismet server seems to run well, it writes the log-files with the informations about my home-AP.
But starting of kismet_client causes "Segmentation fault" and my bash-session is not usable amymore.
I'm using C860 with SanDisk Wifi-card. The "normal" WiFi-connection to my AP works properly. Wellenreiter from the Cacko-feed works properly and detects my home-AP.

Any suggestion is very appreciated

Best regards

Cmpayc

Title: Kismet Client: Segmentation Fault
Post by: Sniffer on March 16, 2005, 05:42:11 am

Im not sure if this (http://www.irongeek.com/i.php?submenu=zaurus/zaurusheader&page=zaurus/wardrivingapps) is any help as your using cacko, and its written for OZ but im guessing the same principal of what is done is the same.

Title: Kismet Client: Segmentation Fault
Post by: stupkid on March 17, 2005, 11:25:54 am

Are you running kismet from the "Kismet" icon under Network?  If you really have to run it from your own konsole instance take a look at the /opt/QtPalmtop/bin/kismet.sh script.

Title: Kismet Client: Segmentation Fault
Post by: cmpayc on March 18, 2005, 03:26:41 am

Kismet does not start from icon under Network.
If I try this, the new shell-window comes up, I can read a couple of messages ( the latest are "Segmentation fault", "Stopping WLAN sniffer", "Stopping WLAN Card") and the shell-window closes.
The script /opt/QtPalmtop/bin/kismet.sh basically calls the script /opt/QtPalmtop/bin/k.sh, so I can IMHO start it from the shell directly.
I think something is going wrong on starting of kismet_client, because the kismet server seems to run.
Any idea?

Title: Kismet Client: Segmentation Fault
Post by: prospere on April 10, 2005, 04:15:08 pm

I have the same error with the cacko 1.22a ..

My Kismet_client create a segmentation fault ... when i launch in "panel" mode.

When I try to launch the kismet client with the ncurses mode .. Everything is OK

Title: Kismet Client: Segmentation Fault
Post by: speculatrix on May 02, 2005, 04:23:18 am

Quote

I have the same error with the cacko 1.22a ..

My Kismet_client create a segmentation fault ... when i launch in "panel" mode.

When I try to launch the kismet client with the ncurses mode .. Everything is OK
[div align=\"right\"][a href=\"index.php?act=findpost&pid=74476\"][{POST_SNAPBACK}][/a][/div]

weird, under cacko-full the QT front end never worked, now, in cacko-lite I can get the QT front end to work but the ncurses version crashes out (kismet_client segfaults). I've got other bluetooth network problems in cacko-lite, so I might return to the full version.

sigh.

Paul

Title: Kismet Client: Segmentation Fault
Post by: speculatrix on May 02, 2005, 02:14:36 pm

Quote

Quote

I have the same error with the cacko 1.22a ..
My Kismet_client create a segmentation fault ... when i launch in "panel" mode.
When I try to launch the kismet client with the ncurses mode .. Everything is OK
[div align=\"right\"][a href=\"index.php?act=findpost&pid=74476\"][{POST_SNAPBACK}][/a][/div]

weird, under cacko-full the QT front end never worked, now, in cacko-lite I can get the
QT front end to work but the ncurses version crashes out (kismet_client segfaults). I've got other bluetooth network problems in cacko-lite, so I might return to the full version.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=77832\"][{POST_SNAPBACK}][/a][/div]

I've now reflashed back to cacko-full-fat-cream from lite (back to where I started), and now kismet ncurses works again!
still got bluetooth problems.