As a workaround for 3D Desktop Effects, I created a simple startup script. This should get rid of the blank grey windows:
launch_vpuml.sh
!#/bin/sh
export AWT_TOOLKIT=MToolkit
sh "/opt/VP_Suite3.1/launcher/run_vpuml"
Replace the location in the last line with the location of the file ‘run_vpuml’ if you installed in a different location.
The main workaround is the export line.
Make the file executable with “chmod +x launch_vpuml.sh” or right-click->properties->permissions->Allow executing file as program.
Then edit your Applications menu and make a new item, the command should be "sh /home/username/launch_vpuml.sh"
The icon is located in “/opt/VP_Suite3.1/.install4j” and named “run_vpuml.png”
Note: this can happen in many Java programs. This workaround usually works for all Java apps with this problem.
[quote=Anonymous]As a workaround for 3D Desktop Effects, I created a simple startup script. This should get rid of the blank grey windows:
launch_vpuml.sh
!#/bin/sh
export AWT_TOOLKIT=MToolkit
sh "/opt/VP_Suite3.1/launcher/run_vpuml"
Replace the location in the last line with the location of the file ‘run_vpuml’ if you installed in a different location.
The main workaround is the export line.
Make the file executable with “chmod +x launch_vpuml.sh” or right-click->properties->permissions->Allow executing file as program.
Then edit your Applications menu and make a new item, the command should be "sh /home/username/launch_vpuml.sh"
The icon is located in “/opt/VP_Suite3.1/.install4j” and named “run_vpuml.png”
Note: this can happen in many Java programs. This workaround usually works for all Java apps with this problem.[/quote]
Hello!
Thank you very much by the tips! I've been running lately with the same issue. Fixed now with that yours script. I just wanted to know what does that export line does to make it work. I'm just asking you this just because I'm newbie and is always good to know something more.
This is a Beryl issue, and therefore inherited by compiz-fussion also; Beryl causes Java Swing components to not be displayed. Basically this is a fix for Beryl to properly handle Java apps that use Swing Toolkit as their look and fell engine. The default value for AWTToolkit variable is the old AWT Toolkit used by Java apps. It should be explicitly set to MToolkit for Beryl to “enable” Swing support, or in other words, to properly handle Swing based Java apps.
I would like to let you know that the resource page regarding to this issue in Linux is available now. You may visit the page at the following link and I hope the article would help.