Limewire Pirated Edition doesn't respond to Mac OS Lion
 

Hey there:

I've been having issues with Limewire (PE) since I've upgraded to Mac 10.7 (Lion) and I've re-installed it several times with no luck. Limewire will load as it normally does but as soon as I type something in the search box, it crashes giving me this error:
LimeWire cannot be opened because of a problem:
Process: LimeWire [1671]
Path: /Applications/LimeWire.app/Contents/MacOS/LimeWire
Identifier: com.limegroup.gnutella
Version: 0.0.3.9 (LimeWire 0.0.3.9)
Code Type: X86 (Native)
Parent Process: launchd [157]

Date/Time: 2011-09-11 11:26:30.465 -0700
OS Version: Mac OS X 10.7 (11A390)
Report Version: 8

Interval Since Last Report: 48871 sec
Crashes Since Last Report: 14
Per-App Interval Since Last Report: 481 sec
Per-App Crashes Since Last Report: 10
Anonymous UUID: 4F16EAF3-E2AC-4A8B-9E6B-61D6A451F998

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000

Application Specific Information:
objc[1671]: garbage collection is OFF

Dyld Error Message:
Symbol not found: __TSMWouldEventBeProcessedByPressAndHold
Referenced from: /System/Library/Frameworks/JavaVM.framework/Versions/A/Frameworks/JavaRuntimeSupport.framework/Versions/A/JavaRuntimeSupport
Expected in: /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon

Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 dyld 0x8fe01071 dyld_fatal_error + 1
1 dyld 0x8fe04c5f dyld::fastBindLazySymbol(ImageLoader**, unsigned long) + 140
2 libdyld.dylib 0x91b9384c dyld_stub_binder_ + 20
3 com.apple.java.JavaRuntimeSupport 0x02f3a569 -[NSEvent(JavaRuntimeSupport) willBeHandledByComplexInputMethod] + 41
4 libawt.jnilib 0x1b0bb210 -[NSViewAWT keyDown:] + 129
5 com.apple.AppKit 0x9a927a35 -[NSWindow sendEvent:] + 8068
6 XUL 0x2fc95588 JSD_GetValueForObject + 745249
7 libawt.jnilib 0x1b0b7777 -[CocoaAppWindow sendEvent:] + 181
8 com.apple.AppKit 0x9a843cca -[NSApplication sendEvent:] + 4227
9 com.apple.AppKit 0x9a7d8e4c -[NSApplication run] + 993
10 libawt.jnilib 0x1b08c0d0 +[AWTStarter startAWT:] + 2019
11 libawt.jnilib 0x1b08b89d -[CPerformer perform] + 259
12 com.apple.CoreFoundation 0x95abf771 -[NSObject performSelector:withObject:] + 65
13 com.apple.Foundation 0x917d2e24 __NSThreadPerformPerform + 503
14 com.apple.CoreFoundation 0x95a7e63f __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FU NCTION__ + 15
15 com.apple.CoreFoundation 0x959bfd26 __CFRunLoopDoSources0 + 246
16 com.apple.CoreFoundation 0x959bf688 __CFRunLoopRun + 1112
17 com.apple.CoreFoundation 0x959bee1c CFRunLoopRunSpecific + 332
18 com.apple.CoreFoundation 0x959becc8 CFRunLoopRunInMode + 120
19 com.apple.JavaApplicationLauncher 0x00007fd2 startupJava(LauncherArgsStruct*) + 304
20 com.apple.JavaApplicationLauncher 0x0000af58 launchJavaApplicationWithJVMInfo + 1440
21 com.apple.JavaApplicationLauncher 0x0000767b launchJavaApplication + 39
22 com.limegroup.gnutella 0x00001e8e 0x1000 + 3726
23 com.limegroup.gnutella 0x00001cf0 0x1000 + 3312
24 com.limegroup.gnutella 0x00001c1d 0x1000 + 3101

Thread 1:
0 libsystem_kernel.dylib 0x9024102e __workq_kernreturn + 10
1 libsystem_c.dylib 0x94741d59 _pthread_wqthread + 773
2 libsystem_c.dylib 0x9474316e start_wqthread + 30

Thread 2:
0 libsystem_kernel.dylib 0x9024102e __workq_kernreturn + 10
1 libsystem_c.dylib 0x94741d59 _pthread_wqthread + 773
2 libsystem_c.dylib 0x9474316e start_wqthread + 30

Thread 3 name: Dispatch queue: com.apple.libdispatch-manager
Thread 3:
0 libsystem_kernel.dylib 0x9024190a kevent + 10
1 libdispatch.dylib 0x99eb21bd _dispatch_mgr_invoke + 966
2 libdispatch.dylib 0x99eb3198 _dispatch_queue_invoke + 55
3 libdispatch.dylib 0x99eb299f _dispatch_worker_thread2 + 187
4 libsystem_c.dylib 0x94741bae _pthread_wqthread + 346
5 libsystem_c.dylib 0x9474316e start_wqthread + 30

Thread 4:
0 libsystem_kernel.dylib 0x9023ec3a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9023e20e mach_msg + 70
2 libjvm.dylib 0x02a86f31 0x2800000 + 2649905
3 libjvm.dylib 0x028143f6 0x2800000 + 82934
4 libjvm.dylib 0x02a7b149 0x2800000 + 2601289
5 libjvm.dylib 0x02a7b218 0x2800000 + 2601496
6 libjvm.dylib 0x02813ed7 0x2800000 + 81623
7 libjvm.dylib 0x028b9dfe 0x2800000 + 761342
8 libjvm.dylib 0x028b995c 0x2800000 + 760156
9 com.apple.JavaApplicationLauncher 0x00009fb6 startJavaApplication + 8034
10 com.apple.JavaApplicationLauncher 0x00008052 runJava(LauncherArgsStruct*) + 83
11 com.apple.JavaApplicationLauncher 0x00007ff7 _ZL14java_main_stubPv + 22
12 libsystem_c.dylib 0x9473ff63 _pthread_start + 335
13 libsystem_c.dylib 0x9474314e thread_start + 34...................

Thanks for reading :)

I have not upgraded to Lion yet. Even though Lion is so cheap, the local reviews of people who had tried it was poor. Plus I am not keen on losing Rosetta which allows programs designed to run on PowerPC processors, to run on later OSX versions such as intel macs. Lion dropped the option for Rosetta. :( Thus I'd lose the ability to use several programs.

Are you booted into 32 or 64 bit OSX?

Here's one thing to try, Get Information for LimeWire (command i), check the option for running in 32 bit. I know my LW only runs properly on my Snow Leopard in this mode. Else like you, it crashes soon after opening.
Else if it is already checked, try unchecking the 32 bit option.

I notice a part of the error refers to Carbon. I didn't think Lion supported Carbon now. I am not too bright sometimes lol.

Have you checked for Java updates? One thought is you have upgraded Lion overtop of an earlier OSX. LW may run properly if on a fresh Lion installation with no prior OSX installation history.

Another thing to try is to do a SAFE boot (ie: hold down shift key as you boot until you see the apple face), then use Disk Utility to repair permissions. This is recommended after any OSX updates (or adobe for that matter.) . (On that topic, I hate Micro$oft & Adobe installing their junk all over the system.)

Just figured it out... Upgrading to Lion didn't have anything to do with it... it was upgrading my wireless keyboard (which I've regretted buying for quite sometime now lol) after installing Lion that started this. I used a wired keyboard (an ugly black one) and worked just fine. I found it really funny Limewire would only crash after I typed anything in the search box so I experimented with copying and pasting via mouse and worked like a charm. So... I still want to use my Mac wireless keyboard but I'm going to need to downgrade... I think... so I'm going to google on how to do so lol...

Upgrade the software/drive for the wireless keyboard is what I did that messed it up...

Thanks for letting us know what happened (& that LW is working ok otherwise.) :) I bought a wireless keyboard & mouse with my mac, I use neither, I dislike them. The bluetooth card on my mac might be buggy. I've read many reports about similar issues with continually losing connection with mouse or keyboard. Wired is safe for me. :D

Black keyboard, does not sound like a mac brand. Sounds like a 3rd party one.

I want to get a new keyboard, but Mac online are fast to remove older models, the newer one designed for use with Lion. :( I don't need all that connect online stuff or whiz bang F key options. I like what I have, don't wish to lose those button abilities for sound, monitor & disk tray or hide all to show desktop. I spilt water on my keyboard some days back, now my control & shift-lock keys don't work, just as well my keyboard has dual keys for control.

I think that the developers of Limewire Pirate Edition are not the ones responsible for developing the original LimeWire, and also I think that the Pirate Edition will have only the faintest shadow of the original limewire.