Finish and OK buttons not working!!!
 

I recently updated limewire (basic) to 5.0.11 on an intel mac running leopard and every time I try to change the prefrences, the OK (or apply) button is un-clickable. I looked all over the forums and found the java thing. I made the java 6 my top and still no luck. I deleted the prefrences from my library and now in the default settings (the one that goes up when limewire is first installed) and I cant click the finish button so I cant at all go onto limewire. Sometimes it says "limewire has a run into a bug send now?" or something like that (already sent the bug report a few days ago). I dont have any firewalls blocking it, but my leopard is an upgrade instead of a new computer with it pre-installed. Could that be the problem? Please Help!!!

There was a bug with the LW 5 alpha versions not showing OK buttons however 5.0_11 fixed it. Do you have the most recent Leopard updates? Check Software Update ... option under Apple menu. There's a new Java update just released. Or perhaps that's the problem.

Did you try deleting your LW preferences folder again?

Yes, i have the most recent updates, but its not that the buttons dont show up i just press it a million times and nothing happens. Every other button works just not the ones that complete it. I don't have the alpha version though (I dont think). I did delete the preferences a few times and even re-installed limewire.

I just installed the Java update & LW 5 OK buttons seem to work fine.

Stief might have ideas.

I'd wait on LW to see if in fact it is a bug.

Which machine model are you running may I ask?

Oh a late thought, are you sure you are logged in as Admin.? If not logged into an Admin account you 'might' not have permissions to change preferences. That I"m not sure about.

I am the administrator (its not a shared computer), and its an imac (the one before the latest ones) with a 2.16 ghz intel core 2 duo processor and I have a lot of free space on it. My older limewire worked perfectly (the 4.watever one/s) so i know that its not just my computer and I did install limewire from limewire.com (the latest version).

Suggestions I could make: (a) Do a safe boot & repair permissions; SAFE Boot & Repair Permissions

(b) Set up a new account, see if the problem is the same in the 2nd account; Setting up a Test Account in OSX (click on link)

i repair the disc permissions once in a while, I'll try it on my other mac to see if its working but if it does work what do I do? I'll be back!

Well, I did permission repair and limewire works perfectly on my other mac. So I guess I'll zap it (uninstall) and reinstall it, but how can I save my items that are downloading?(i have 2 things downloading, big files)

heres the bug if it means anything to you:

LimeWire version 5.0.11
Java version 1.6.0_07 from Apple Inc.
Mac OS X v. 10.5.6 on x86_64
Free/total memory: 41547768/108253184

java.lang.ArrayIndexOutOfBoundsException: 200
at java.io.ExpiringCache.cleanup(ExpiringCache.java:1 01)
at java.io.ExpiringCache.get(ExpiringCache.java:56)
at java.io.UnixFileSystem.canonicalize(UnixFileSystem .java:137)
at java.io.File.getCanonicalPath(File.java:559)
at java.io.File.getCanonicalFile(File.java:583)
at org.limewire.util.FileUtils.getCanonicalFile(FileU tils.java:136)
at org.limewire.util.FileUtils.canonicalize(FileUtils .java:127)
at com.limegroup.gnutella.library.ManagedFileListImpl .isFolderManageable(ManagedFileListImpl.java:1341)
at com.limegroup.gnutella.library.ManagedFileListImpl .isDirectoryAllowed(ManagedFileListImpl.java:1438)
at org.limewire.core.impl.library.LibraryManagerImpl$ LibraryDataImpl.isDirectoryAllowed(LibraryManagerI mpl.java:94)
at org.limewire.ui.swing.library.manager.LibraryManag erItemImpl*****accept(LibraryManagerItemImpl.java: 86)
at java.io.File.listFiles(File.java:1134)
at org.limewire.ui.swing.library.manager.LibraryManag erItemImpl.getChildren(LibraryManagerItemImpl.java :83)
at org.limewire.ui.swing.library.manager.LibraryManag erItemImpl.getExcludedChildren(LibraryManagerItemI mpl.java:127)
at
***(says this one a million times^)


Detail: Uncaught event-thread error.

-- listing session information --
Current thread: AWT-EventQueue-0
Active Threads: 20
Uptime: 2:24
Is Connected: true
Number of Ultrapeer -> Ultrapeer Connections: 0
Number of Ultrapeer -> Leaf Connections: 0
Number of Leaf -> Ultrapeer Connections: 3
Number of Old Connections: 0
Acting as Ultrapeer: false
Acting as Shielded Leaf: true
Number of Active Uploads: 0
Number of Queued Uploads: 0
Number of Active Managed Downloads: 0
Number of Active HTTP Downloaders: 0
Number of Waiting Downloads: 0
Received incoming this session: false
Number of Managed Files: 0
Number of Mounted Friend Files: 0
Number of Shared Files: 0
Guess Capable: false
Received Solicited UDP: true
SIMPP version: 22
Port Stable: true
FWT Capable: true
Last Reported Port: 33495
External Port: 33495
IP Pongs Received: 10
Number of Content Response URNs: 0
Number of CreationTimeCache URNs: 0
VF Byte Cache Size: 0
VF Verify Cache Size: 0
VF Queue Size: 0
ByteBuffer Cache Size: 0
Number of Waiting Sockets: 0
Number of Pending Timeouts: 0
Peak Number of Thread: 30
Number of SP2 Workarounds: 0
System Load Avg: 0.84765625
Objects Pending GC: 0
Free Space In Settings: 47238381568
Free Space In Incomplete: 47238381568
Free Space In Downloads: 0
Heap Memory Usage: init = 0(0K) used = 66705416(65142K) committed = 108253184(105716K) max = 257294336(251264K)
Non-Heap Memory Usage: init = 24313856(23744K) used = 65388632(63856K) committed = 65536000(64000K) max = 138412032(135168K)
SlotManager dump:: active:0:0 1:0 2:0 queued:0:0 1:0 2:0 resumable:0:0 1:0 2:0 bw now:0.0 session avg:0.0
Number of select calls: 280
Number of immediate selects: 81
Average time in select: 481735837

-- listing threads --
JmDNS.RecordReaper: 1
AWT-AppKit: 1
Timer-0: 1
RefQueueWorker@org.apache.http.impl.conn.tsccm.Con nPoolByRoute@39bda9b9: 1
AWT-Shutdown: 1
JmDNS.SocketListener: 1
QRPPropagator: 1
device search response: 1
Deadlock Detection Thread: 1
ManualGC: 1
QueryUnicaster: 1
ContentProcessor: 1
HSQLDB Timer @59065c86: 1
Thread-8: 1
AWT-EventQueue-0: 1
MulticastService: 1
NIODispatcher: 1
RefQueueWorker@org.apache.http.impl.conn.tsccm.Con nPoolByRoute@6826d526: 1
DestroyJavaVM: 1
Message-Executor: 1


-- listing properties --
PORT=33495
RUN_ON_STARTUP=false
ACTIVE_DHT_ROUTETABLE_VERSION=1
UPDATE_DELAY=25200001
UPDATE_GIVEUP_FACTOR=49
ENABLE_DHT_ALT_LOC_QUERIES=true
FILTER_HASH_QUERIES=true
PROMOTION_SYSTEM_IS_ENABLED=true
DISABLE_DHT_NETWORK=false
MAX_ALTS_PER_RESPONSE=11
PUBLISH_ALT_LOCS=true
AVERAGE_UPTIME=115
TOTAL_UPTIME=115
SEND_LIME_RESPONSES=0.999f
MAX_UPLOAD_BYTES_PER_SEC=2
DISABLE_OOB_V2=0.999f
MIN_CONNECT_TIME=4
POSITIONS_SET=true
CONTENT_AUTHORITIES=fserv1.limewire.com:10000
COUNTRY=
WINDOW_X_V5=328
ENABLE_PASSIVE_LEAF_DHT_MODE=true
UPDATE_MIN_ATTEMPTS=1999
PRO_ADS=For Turbo-Charged searches get LimeWi...
LIBRARY_VERSION=FIVE_0_0
FILTERED_URNS_REMOTE=2AADXP4EN2P3I6GSJOS6UQ27RI2IL L4P;2CZQ...
MAX_ALTS_TO_DISPLAY=2
ENABLE_PASSIVE_DHT_MODE=true
MAX_SKIP_ACKS=2
MAX_LEAVES=40
OOB_REDUNDANCY=true
LAST_ACCEPTABLE_BUG_VERSION=4.17.6
UPDATE_RETRY_DELAY=1800001
LIME_QRP_ENTRIES=lime;wire;limewire;pro;limewirepr o
LAST_EXPIRE_TIME=1234667083060
PREVIOUS_SHUTDOWN_WAS_GRACEFUL=false
MIN_PASSIVE_LEAF_DHT_INITIAL_UPTIME=300000
MAX_DOWNLOAD_BYTES_PER_SEC=3
UPDATE_DOWNLOAD_DELAY=14400001
LAST_UPDATE_TIMESTAMP=1223920896640
DHT_BOOTSTRAP_HOSTS=76.8.67.27:6002
CRAWLER_IPS=76.8.67.27;
WINDOW_Y_V5=150
MAX_DHT_ALT_LOC_QUERY_ATTEMPTS=500
PUBLISH_PUSH_PROXIES=true
MIN_PASSIVE_LEAF_DHT_AVERAGE_UPTIME=60000
CURRENTLY_RUNNING=true
INSPECTOR_IPS=76.8.67.27
ENABLE_PUSH_PROXY_QUERIES=true
CUSTOM_FD_CRITERIA=ups;atUpSet;<;cups;cUpSet;<;OR; NOT;la...
CLIENT_ID=228A1195EB41E634B024A0C3F9EAE200
HOSTILE_IPS=119.193.124.11;119.194.203.195;121.11. ..
MIN_ACTIVE_DHT_INITIAL_UPTIME=3600000
LAST_N_UPTIMES=60
IDLE_CONNECTIONS=2
MIN_ACTIVE_DHT_AVERAGE_UPTIME=1800000

deleted every trace if limewire, reinstalled it and still no luck

I'll see if I can get an opinion on this. But looks like a specific computer case.

You could go back to LW 4.18; just choose Old versions link from the download page. ;) But you would need to remove the install limewire.pkg file from receipts folder if you did, otherwise the older version would not install; Receipts folder sample image

BTW did you try setting up an alternate account to test LW out?

well, i didnt set up a different account, but i tried it on my other mac and it worked, so i guess its my comp.

Well I tell you an oddity, on my intel macpro I am unable to run 4.18 or LW 5. So I installed OSX afresh onto a different drive & 4.18 & LW 5 worked fine. (BTW I had reinstalled OSX a few times over past 12 months on the main drive but only archive installs, not reformatting the drive.)

Setting up a test account was just an idea. You can always delete the account anytime. :) Thing is if LW does work fine there, then it points to a problem in the main account rather than the computer itself.

There might be a problem with your Java installation. Perhaps one of the installations was partially corrupt or related issues. Perhaps Java preferences corruption. Sometimes solutions to LW problems on OSX was reinstalling Java using the offline installer, as compared to software update. Or even the OSX version itself.

BTW you upgraded to Leopard right? What type of installation did you do, an archive instal or ... ?

I'm back. Limewire used to work (the 4.xxx version/s) but when I installed the newest one, it didn't. I think it's just a coding problem in one of the limewires I installed. How can I find all the files incorporated with the limewire program to fully delete them (I tried app zapper but didn't work after re-installation)? Thanks for all the help.

You need to remove the install limewire.pkg file from receipts folder; Receipts folder sample image

erm .. might be worth deleting your LW preferences: Deleting LW Preferences folder in OSX

I also occasionally had same problem when trying to update to LW 4.18 or 5 on my main OSX system, in that LW 4.16 would not work any more after downgrading. But it did after deleting a few items.

If that does not work, lower the Java 6 level priority below Java 5 in Java preferences: Setting up Java for Leopard.

(hmm I wonder if your LW 5 issue was related to the order of your Java preferences. Difficult to say.)

Ooh yeah, and it does work on the other account (the test one)

It does ? Meaning no problems with OK buttons? And that's with LW 5?

If that's the case then issue would be moving certain preferences across to the main account. I'll get Stief to have a quick look here see if he has any advice.

Yea, everything's fine in the other one. I'll still try deleting everything, reorder java, and re-install everything and give it a go.

Dam, still no luck. I'm sill not able to get past the preferences because of the "Finish" button. Also still getting that same bug.

hmm .. wait until Stief gets here, he might have a word of advice.

I've had same problems of LW 4.16 not running as I suggested, but I changed Java settings & deleted LW prefs to solve the issue. Java settings might mean just one movement in position of java version ... or more ... so play around with it in meantime. ;)

The fact you had another account work fine with LW 5 is a major plus. Even I was unable to achieve that. I had to install OSX afresh on a different drive. Thus I need to reboot into that drive in order to use LW 5.

BTW Java settings as for which version is higher or lower is account specific.

sorry, no idea. Since all works well with a test account on the same computer, the problem lies in the home account's preferences.

Since you deleted all LW prefs from the home account library (with no benefit), some other pref is the culprit.

As LOTR knows, finding that pref is VERY difficult.

Have you tried deleting all the java .plist preferences in the home account library? (NOT the ones in the main Library found when opening just the hard drive). IIRC, that was the last trick LOTR tried, with no success, so I doubt this will work here either.

As for the error report, I see an uncaught exception. So, try posting it over at Bugs and Beta Testing - LimeWire Forums where it can get the attention of the developers.

best wishes

Alright, thanks for the help, I'll post it up there.

Just wanted to let you guys know that the update fixed everything. Thanks for all your help!