Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Vuze 5.7.1.0 console UI
#1
I am getting semi-continuous warnings

***WARNING: Display must be created on main thread due to Cocoa restrictions.


How do I make these stop?

These started when I updated to 5.7.1.0 from 5.7.0.0

To use the console ui, I copied commons-cli.jar, libOSXAccess.jnilib, log4j.jar, and libOSXAccess_10.5.jnilib
from its previous location in vuze.app to the new location of azureus2.jar which I found in
/Users/Shared/Library/Application Support/Vuze

Everything worked as normal and I even got fewer warnings on startup then before.
But after a few minutes the terminal screen fills up with cocoa restrictions warning.

Help is greatly appreciated!
Reply
#2
Not sure of the cause, but if you have swt.jar on your classpath then try removing it.
Reply
#3
Sorry for the question, but how do I know what is on my classpath?
How do I find out?

I am running OSX 10.11.3.

swt.jar was in the old vuze (7.1.0.0)
but is not in the new directory with azureus2.jar.

The command I use to run vuze is:

java -Dazureus.config.path=/Users/username/Library/Application\ Support/Vuze -jar Azureus2.jar --ui=console

This is run from the /Users/Shared/Library/Application Support/Vuze directory
where the Azureus2.jar file is located.

Any additional advice is welcome!
Reply
#4
Hmm, if swt.jar isn't in 

/Users/Shared/Library/Application Support/Vuze

then I'm not sure of the cause. The error is most likely being generated by the SWT UI library (which is used by the non-console version of Vuze). This isn't required for console mode but if it was getting initialized somehow then I could see it generating the message.
Reply
#5
I may have been wrong.

it seems swt.jar WAS in the directory
/Users/Shared/Library/Application Support/Vuze

For now, I moved it out of there.
Its been about 15 min, and no warnings, so my fingers are crossed.
They were coming every few minutes before.

Is swt.jar needed for anything?
Will I still be able to run the gui?

Thanks for your help.
Reply
#6
I may have answered my own question.

The GUI won't run without the swt.jar and with it, the console ui generates errors.

For now, I created a separate directory (in shared) for running
the console.

seems to work, though a fix so that the console ui doesn't care about
swt.jar being in the directory. (it never used to).

Thanks again to pointing me to that file.
Reply
#7
Current VUZE simply doesn't work with 10.11.3 Mine freezes, Quits, and won't even use the BTGuard Proxy settings. Too bad there is no support for VUZE any more, it used to be a decent program.
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
Bug Unable to start console UI on Linux soulkris 5 1,391 03-05-2016, 10:59 AM
Last Post: soulkris
  IllegalArgumentException in console column cicku 1 998 12-04-2015, 04:14 PM
Last Post: parg



Users browsing this thread: 1 Guest(s)