Vuze 5.5 UI Issue

[parg]

Please double check that you have 

export SWT_GTK3=0   # things don't work well with the preliminary GTK3 SWT support


in your startup script.

[hairydan]

Please double check that you have 

export SWT_GTK3=0   # things don't work well with the preliminary GTK3 SWT support


in your startup script.

 

is this correct?

#!/bin/bash

######## CONFIGURATION OPTIONS ########
SWT_GTK3=0
SCRIPT_NOT_CHANGED=0    # change this to 1 if you don't want your script overwritten!
JAVA_PROGRAM_DIR=""     # use full path to java bin dir, ex. "/usr/java/j2sdk1.4.2/bin/"
#PROGRAM_DIR="/home/username/apps/azureus"      # use full path to Azureus bin dir
JAVA_ARGS="-Xmx128m"



 

[hairydan]

Please double check that you have 

export SWT_GTK3=0   # things don't work well with the preliminary GTK3 SWT support


in your startup script.


 

is this correct?

#!/bin/bash

######## CONFIGURATION OPTIONS ########
SWT_GTK3=0
SCRIPT_NOT_CHANGED=0    # change this to 1 if you don't want your script overwritten!
JAVA_PROGRAM_DIR=""     # use full path to java bin dir, ex. "/usr/java/j2sdk1.4.2/bin/"
#PROGRAM_DIR="/home/username/apps/azureus"      # use full path to Azureus bin dir
JAVA_ARGS="-Xmx128m"



 

 

Actually, adding 'export" in front of SWT_GTK3=0 seems to have fixed the UI.
Now the 2nd problem is popping up: infinite loop reminder that a New Vuze Startup Script is available.

 

[parg]

You would need to either

1) use the script provided by Vuze
2) change that line in your script that says SCRIPT_NOT_CHANGED=0 to 1 (as per the comment)

Also I'd increase the memory available to Vuze by setting

JAVA_ARGS="-Xmx245m"

Not sure why Vuze isn't overwriting your script given the current SCRIPT_NOT_CHANGED value, is it read-only?

[hairydan]

You would need to either

1) use the script provided by Vuze
2) change that line in your script that says SCRIPT_NOT_CHANGED=0 to 1 (as per the comment)

Also I'd increase the memory available to Vuze by setting

JAVA_ARGS="-Xmx245m"

Not sure why Vuze isn't overwriting your script given the current SCRIPT_NOT_CHANGED value, is it read-only?

 

Yes, it wasn't world readable. I've replaced the vuze startup script from the latest installer package. that did the trick. Thank you!
 

[MrQuade]

Another CentOS 6.6 user here having exactly the same problem.

The line:
export SWT_GTK3=0 # things don't work well with the preliminary GTK3 SWT support

is in my startup script

I run the OS as a VM Guest under a CentOS 6.6 Host running KVM. I access the client via desktop sharing using VNC, but corruption is present if I view the console using virt-manager (spice) as well.

[smithgcovert]

The problem with CentOS 6.6 and the latest version of Vuze is definitely caused by the upgrade to SWT, and not Vuze 5.5 itself.

To confirm this: I downgraded to Vuze 5.4, and then let it upgrade to Vuse 5.5, but did not upgrade SWT. Vuze 5.5, with the older SWT, ran fine.

I then allowed Vuze to upgrade the SWT level -- and immediately after the problem with UI corruption occurred.

I have since moved back to just plain old Vuze 5.4, and disabled all automatic upgrading.

My start script did have the specified SWT_GTK3=0 export line, but that had no effect. (on or off, I tried both ways just to make sure.)

[jeffsedlak]

I have not used VUZE for a while. After my torrent completed, when I right clicked on the file row in the library, I get a selection of options, there was a move option where I could click and select the desktop to move my new file. Now, this MOVE option is not in the list of options. How do I move or copy my newly created file out of VUZE

[parg]

Advanced->Files->Move Data Files...

[dzumwald]

using current PCLinuxOS and the interface is also blank just like this 5.5, disappeared after the forced upgrade occurred.
the left hand column, is blank however, it is possible to click items in the column, and change between library and download view in the main portion of the window. this is the reason forced upgrade is not always a good idea.

I hope you force an upgrade of something that works properly soon

[MrQuade]

Forced upgrade implies something that is non-optional.  Vuze updates can be turned off, so they are just "Automatic", not "Forced".

You can manually download and install the previous version from here:
http://sourceforge.net/projects/azureus/...Vuze_5400/

And then you can disable automatic updates from:
Options->Interface->Start

and untick the following two items:
"Check for latest when Vuze starts"
"Check for latest version periodically"

[jeffsedlak]

Thanks!
Works great.
jeff

Advanced->Files->Move Data Files...

 

 

[melvintmelvin]

I think I was able to fix the issue by installing the 32-bit libraries, and 32-bit version of Oracle JVM 7. Seems to be working well. Was completely borked on 64bit. Centos 6.6 x64.

Thanks!
Works great.
jeff

Advanced->Files->Move Data Files...


 

 

 

 

[Bekar]

Problem appears to persist in 5.6.0.0 (no swt update).

[dzumwald]

Forced upgrade implies something that is non-optional.  Vuze updates can be turned off, so they are just "Automatic", not "Forced".

You can manually download and install the previous version from here:
http://sourceforge.net/projects/azureus/...Vuze_5400/

And then you can disable automatic updates from:
Options->Interface->Start

and untick the following two items:
"Check for latest when Vuze starts"
"Check for latest version periodically"




 

yes, that would be a great idea, IF, I could read the text in the (Options-> Interface-> Start) section.
It is blank just as the left hand column on Vuze., in fact all of the advanced user options are blank. I had it working after a downgrade to 4.9.0, then Vuze updated automatically, and voila' everything went blank again. I was not aware of the option to stop upgrades, in the future I shall make certain both are 'ticked'
 

 

 

 

[parg]

Could it be http://wiki.vuze.com/w/Known_Issues#Linux_UI_Issues ?