Yes, I'm running 10.7.1 and it just keeps scanning, never finds anything, never stops scanning. On to the next one.

I'm sorry for your trouble. It would be extremely helpful if you could open a ticket at http://trac.kismac-ng.org and post your kismac log file which can be found at ~/LIbrary/Logs/KisMAC.log

@kismac you got my vote for the most thoughtful, succinct and concise reply of the year.

Ok, ticket created. Log included with the ticket.

Please submit a crash report. Add as many details as possible about your setup. Please specifically mention iMac8,1

KisMAC 0.3+ , including 0.3.2, 0.3.3 is working fine on my MBP 4.1

let me know if I can help

the chunk below is from my mb4,1. I will post a report from my iMac8,1 when I get home.
=============================================
Date/Time: 2011-02-07 19:44:15 +0000
OS Version: 10.6.6 (Build 10J567)
Architecture: x86_64
Report Version: 7

Command: KisMAC
Path: /Users/xxxx/Desktop/KisMAC.app/Contents/MacOS/KisMAC
Version: KisMAC 0.3.3 (0.3.3)
Parent: launchd [190]

PID: 58204
Event: hang
Duration: 4.90s (sampling started after 2 seconds)
Steps: 9 (100ms sampling interval)

Pageins: 16
Pageouts: 0


Process: KisMAC [58204]
Path: /Users/xxxx/Desktop/KisMAC.app/Contents/MacOS/KisMAC
UID: 501

Thread 6fc2b7c DispatchQueue 1
User stack:
9 start + 52 (in KisMAC) [0x100002044]
9 main + 195 (in KisMAC) [0x10000210f]
9 NSApplicationMain + 364 (in AppKit) [0x7fff8070d1a8]
9 -[NSApplication run] + 395 (in AppKit) [0x7fff8071448b]
9 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 155 (in AppKit) [0x7fff8074e7a9]
9 _DPSNextEvent + 718 (in AppKit) [0x7fff8074ee64]
9 BlockUntilNextEventMatchingListInMode + 59 (in HIToolbox) [0x7fff86c2e5f8]
9 ReceiveNextEventCommon + 310 (in HIToolbox) [0x7fff86c2e73f]
9 RunCurrentEventLoopInMode + 333 (in HIToolbox) [0x7fff86c2e93a]
9 CFRunLoopRunSpecific + 575 (in CoreFoundation) [0x7fff875b4dbf]
9 __CFRunLoopRun + 6488 (in CoreFoundation) [0x7fff875b6be8]
9 __NSFireTimer + 114 (in Foundation) [0x7fff861ca8f5]
9 -[WaveScanner doChannelHop:] + 101 (in KisMAC) [0x100024cda]
9 -[WaveDriver hopToNextChannel] + 570 (in KisMAC) [0x100039073]
9 -[WaveDriverAirportExtreme setChannel:] + 150 (in KisMAC) [0x100056383]
9 sleep + 61 (in libSystem.B.dylib) [0x7fff873cadf0]
9 __semwait_signal + 10 (in libSystem.B.dylib) [0x7fff8737dfca]
Kernel stack:
9 semaphore_wait_continue + 0 [0x22a3dd]

Thread 941b7a8 DispatchQueue 2
User stack:
9 start_wqthread + 13 (in libSystem.B.dylib) [0x7fff8735d005]
9 _pthread_wqthread + 353 (in libSystem.B.dylib) [0x7fff8735d168]
9 _dispatch_worker_thread2 + 252 (in libSystem.B.dylib) [0x7fff8735d83e]
9 _dispatch_queue_invoke + 185 (in libSystem.B.dylib) [0x7fff8735dd14]
9 kevent + 10 (in libSystem.B.dylib) [0x7fff8735c16a]
Kernel stack:
9 kevent + 97 [0x473932]

Thread 8b91000
User stack:
9 start_wqthread + 13 (in libSystem.B.dylib) [0x7fff8735d005]
9 __workq_kernreturn + 10 (in libSystem.B.dylib) [0x7fff8735cf8a]
Kernel stack:
9 bsdthread_create + 1313 [0x4cd603]

Thread ac2b3d4
User stack:
9 thread_start + 13 (in libSystem.B.dylib) [0x7fff8737c3e9]
9 _pthread_start + 331 (in libSystem.B.dylib) [0x7fff8737c536]
9 __NSThread__main__ + 1429 (in Foundation) [0x7fff861750a5]
9 -[WaveScanner doScan:] + 152 (in KisMAC) [0x100024c3a]
9 -[WaveScanner doPassiveScan:] + 972 (in KisMAC) [0x100025be4]
9 -[WaveDriverAirportExtreme nextFrame] + 53 (in KisMAC) [0x100055f79]
9 pcap_next + 37 (in libpcap.A.dylib) [0x10021cd9b]
9 read + 10 (in libSystem.B.dylib) [0x7fff8734d9c6]
Kernel stack:
9 lo64_unix_scall + 77 [0x2a143d]
9 unix_syscall64 + 617 [0x4f13be]
9 read_nocancel + 158 [0x498faa]
9 write + 312 [0x49882e]
9 utf8_encodelen + 3711 [0x2f319c]
9 VNOP_READ + 157 [0x2fe14d]
9 spec_read + 104 [0x30b5f2]
9 bpfread + 215 [0x316e99]
9 tsleep + 105 [0x48a634]
9 wakeup + 786 [0x48a20d]
9 thread_block + 33 [0x2272e7]
9 thread_block_reason + 331 [0x227259]
9 thread_dispatch + 1966 [0x226fba]
9 machine_switch_context + 753 [0x2a8a6e]

Thread d1df7a8
User stack:
9 thread_start + 13 (in libSystem.B.dylib) [0x7fff8737c3e9]
9 _pthread_start + 331 (in libSystem.B.dylib) [0x7fff8737c536]
9 select$DARWIN_EXTSN + 10 (in libSystem.B.dylib) [0x7fff87386e92]
Kernel stack:
9 sleep + 52 [0x48a3f9]

Binary Images:
0x100000000 - 0x10009cfff org.kismac-ng.kismac KisMAC 0.3.3 (0.3.3) /Users/yiyu/Desktop/KisMAC.app/Contents/MacOS/KisMAC
0x100205000 - 0x100238ff7 libpcap.A.dylib ??? (???) /usr/lib/libpcap.A.dylib
0x7fff8070b000 - 0x7fff81101fff com.apple.AppKit 6.6.7 (1038.35) /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x7fff86164000 - 0x7fff863e7ff7 com.apple.Foundation 6.6.4 (751.42) /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x7fff86c00000 - 0x7fff86efefe7 com.apple.HIToolbox 1.6.4 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
0x7fff87342000 - 0x7fff87503fff libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib
0x7fff87569000 - 0x7fff876e0fe7 com.apple.CoreFoundation 6.6.4 (550.42) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation

my settings:
general options: tick, tick
filter: none
sounds: none
driver:
Apple Airport Extreme card, passive mode
Channel 1~14
Keep everything
Hopping frequency: 0.25s
GPS: do not use
Traffic: tick, tick, 2
Advanced: 100, 0, 2, untick

Quick questionS
Why does the path says "desktop" in "Path: /Users/xxxx/Desktop/KisMAC.app/Contents/MacOS"

and most importantly...
Are you in the US, Europe or Japan?

I think I have your issue fixed ....

no offence to the developer, but I don't keep unusable apps in my Applications folder - where KisMAC 0.2.99 is. It's decompressed onto my desktop so I can quickly delete after testing it.

sorry I forgot to answer your most important question: I'm in the UK

"no offence to the developer, but I don't keep unusable apps in my Applications folder"

Bah, you will not offend them. You'll make them smile...
Here is why:

1)
When you delete the App, you don't delete the preference file(s) associated with it. I would HIGHLY suggest to use APP Cleaner to remove all pref files and restart with a ~proper~ install.

Secondly,
Channel 14 is for Japan only.
Microwaves, Baby transmitter and other electronic are close to the RF range of 2.484 (ch14)

Because of the way WIFI was set up, channels overlap. This is why everybody uses 1,6,or 11

As a try, Delete [properly] KisMAC. Make clean reinstall, and uncheck ch 14

I would even suggest you to try with 1-11 for a start, then add 12,13 if Ok. Leave 14 alone.

here is a short and clearer explanation of the WIFI overlapping thingy.
http://kismaxx.blogspot.com/2007/11/wifi-signal.html

After that, you'll realize that it was not only KisMAC fault ;-)
You also could leave a little apology for calling KisMAC (in so many word) a piece of junk.
- you would be very surprised what I can do with KisMAC
;-)

I think the Ch14 issue will fix your issue and change your mind.

Best regards

many thanks to JoeNoname, my problem is solved by unchecking ch14. I was being greedy and had KisMAC to sniff all channels for me :)

KisMAC 0.3.3 is now in my Applications folder :)
But why 0.2.99- had no problem with ch14 before?

I would be tempted to say: Ask your microwave, but from here I could no swear on it.

I still don't see the small apology that the KisMAC developer(s) are entitled to ;-)

Well, trace back to all my posts, I never called, or implied that KisMAC is piece of anything.

It's an excellent program and I've been using it for years. Even when 0.3.0/1/2/3 crashed on my machines, I still gave it a 4-start rating and rolled back to 0.2.99. I'm thankful for the developer's effort in maintaining this project, but I'm not sorry for anything or anyone.

On the other hand, I'd appreciate it if the developer would investigate why scanning ch14 worked fine with 0.2.99 and before, but stopped working since 0.3.0. CH13/14 isn't used in some regions, but it doesn't mean the WiFi card can not scan it. It's obviously a new bug since KisMAC 0.3.0, because 0.2.99- could cope with ch14, on my same machines, with no problem.

This is actually very helpful feedback, thanks for taking the time to respond with details. I will investigate the issue with channel 14 and it will be fixed for the next release.

Duly noted.
As for the investigation, it's simply impossible.
You have to understand that you have to do so with a spectrum analyzer, and "on the spot"
Your neighbors could be the cause,

There is maybe something that makes kisMAC not responding properly on Ch14 with interferences, nevertheless, it seems that you were missing some important information on how WIFI and/or KisMAC works.
I am glad that your issue is fixed.

Here's more info that may be helpful:

I'm in a computer lab where no neighbour is nearby. I only run my experiments on 802.11n. According to my analogue spectrum analyser, CH14 isn't occupied. I use KisMAC as an additional digital scanner to monitor 802.11b/g usages near my test-bed.

I am also glad that I can finally keep up with the latest KisMAC. And thanks to JoeNoname gain, for the fix.

ok, thanks for the update,
Then now, with the additional info, it smells like a bug.
In that case, can you put a ticket or a post on the KisMAC-ng website?

Thanks in advance

Done. Ticket #806

Can anyone answer this?

You need to select either the airport active, or airport passive drivers. In the preferences, remove all drivers you might already have in the list. From the dropdown menu, choose AirPort Active and click add.

I tried all that. No luck.

That's probably because you have no wireless device with Orinoco or PrismII chipset in use, but just an Airport card or something. And such a device is not supported by KisMAC as far as I know.

From the developer's website.

"KisMAC supports several third party PCMCIA cards - Orinoco, PrismII, Cisco Aironet, Atheros and PrismGT. USB Prism2 is supported as well, and USB Ralink support is in development. All of the internal AirPort hardware is supported as well."

You have to delete the preferences first, then launch up KisMAC, i think it is a safety measure on KisMac's part so that goverment officials don't know how to use it =P.

All you have to do is delete the preferences file and then relaunch.

i've got the exact same problem with my 12" 1.5GHz Powerbook