PDA

View Full Version : Xgl/Compiz: problems with Java/Swing


dennism
November 14th, 2006, 06:23 AM
After installing XGL/Compiz I can't see the concent of my Java-applications. I can see the frame but not the elements in it - thing it's problems with Swing.
Eg. netbeans have the same problem.

I have:
Suse 10.1
xgl cvs_060522-0.13@i586
compiz cvs_060616-1.16@i586

RAOF
November 14th, 2006, 10:20 AM
This is a known problem, due to Java assuming stuff about the window manager. As far as I'm aware, it's been fixed for a couple of months. Updating to a more recent compiz package should fix it. I've never run Suse, so I don't know where you'd find such a package, but it shouldn't be too hard :)

sblantipodi
November 14th, 2006, 05:36 PM
This is a known problem, due to Java assuming stuff about the window manager. As far as I'm aware, it's been fixed for a couple of months. Updating to a more recent compiz package should fix it. I've never run Suse, so I don't know where you'd find such a package, but it shouldn't be too hard :)

I've got the latest package for Fedora Core 6 and this problem is not solved.
Are you sure that it's been fixed?
I don't think so.

sblantipodi
November 15th, 2006, 11:38 AM
I hope that they'll solve soon this problem :(

No one knows when they should solve this problem?

RYX
November 15th, 2006, 01:29 PM
You can try to run compiz with the option " --indirect-rendering" - it solved some black-window issues for me ... maybe it works.

:)

delphinen
November 15th, 2006, 01:38 PM
what the "--indirect-rendering" option does? it solved many problems for me, and the speed is the same, if not faster than without the parameter

RYX
November 15th, 2006, 01:46 PM
I cannot say for sure, delphinen - afaik it is something like double-buffering. I think everything gets rendered to an off-screen bitmap and then rendered to the screen (so it gets rendered indirect, not directly to the screen). It solves some issues with the nvidia-driver ...

:)

sblantipodi
November 15th, 2006, 06:46 PM
indirect rendering doesn't solve the java problem :(

bijoux
November 15th, 2006, 08:48 PM
this is an annoying bug since i use netbeans for work. anyway this is the fix:

export AWT_TOOLKIT=MToolkit

you can add that line in your /etc/environment
tha should fix your problem

RYX
November 15th, 2006, 09:09 PM
Maybe you can also use:XLIB_SKIP_ARGB_VISUALS=1 <appname>
That disables compiz for certain apps afaik ...

sblantipodi
November 15th, 2006, 09:23 PM
this is an annoying bug since i use netbeans for work. anyway this is the fix:

export AWT_TOOLKIT=MToolkit

you can add that line in your /etc/environment
tha should fix your problem

this not works for me even with netbeans

sblantipodi
November 15th, 2006, 09:25 PM
Maybe you can also use:XLIB_SKIP_ARGB_VISUALS=1 <appname>
That disables compiz for certain apps afaik ...

where I need to put this code?
from the consolle if I write
XLIB_SKIP_ARGB_VISUALS=1 "appname" I've got the some problem.

RYX
November 15th, 2006, 09:34 PM
Sorry, then I have no clue (I meant running the program from console by entering something like "XLIB_SKIP_ARGB_VISUALS=1 netbeans"). But did you try bijoux's proposal?

(It was wrong to say "disables compiz" - it disables the argb-visuals for certain apps (as the name implies)) ...

sblantipodi
November 15th, 2006, 09:48 PM
Sorry, then I have no clue (I meant running the program from console by entering something like "XLIB_SKIP_ARGB_VISUALS=1 netbeans"). But did you try bijoux's proposal?

(It was wrong to say "disables compiz" - it disables the argb-visuals for certain apps (as the name implies)) ...

hey :) I understood what you meant :)
I've got some problem with both method, yours and bijoux's method.

RYX
November 15th, 2006, 09:50 PM
What does "compiz --version" output?

sblantipodi
November 16th, 2006, 11:02 AM
What does "compiz --version" output?

some as other topic :)
0.0.13

RYX
November 16th, 2006, 01:16 PM
The current (development but quite stable) version is 0.3.2 so it seems you have to download the sources from go-compiz.org and compile compiz yourself ... sorry, but apparently there are no up-to-date packages for Fedora atm.

sblantipodi
November 16th, 2006, 01:29 PM
The current (development but quite stable) version is 0.3.2 so it seems you have to download the sources from go-compiz.org and compile compiz yourself ... sorry, but apparently there are no up-to-date packages for Fedora atm.

ok, thanks RYX

bratsever
December 11th, 2006, 06:14 PM
So, how can I solve this problem. I have the same problem, compiz version 0.3.5

ksc91u
December 23rd, 2006, 03:59 PM
It is a bug in java, and fixed in jdk6u1 b01.

See here for more:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6429775

Haisen
December 23rd, 2006, 04:38 PM
It is a bug in java, and fixed in jdk6u1 b01.

See here for more:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6429775

I'm running jdk 6 and have the same problem.

ksc91u
December 23rd, 2006, 04:49 PM
I'm running jdk 6 and have the same problem.

You should download JDK 6 update 1 build b01 from http://jdk6.dev.java.net

Haisen
December 23rd, 2006, 08:30 PM
I'm running jdk 6 and have the same problem.

You should download JDK 6 update 1 build b01 from http://jdk6.dev.java.net

Thanks. It's working now.

oimel
January 27th, 2007, 11:03 AM
There are still some issues with the latest Java that aren't as critical, but just for info:

Sometimes Java windows are much too big with just a little rectangle in which the GUI appears. After closing and reopening the window the size is correct in most cases. Very hard to reproduce this error, but it appears from time to time.

Java Fullscreen Mode is broken for compiz (as with some other window managers). The KDE/Gnome control bars are in front of the Java Fullscreen window. This is bug 6500686 (http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6500686) in Sun's bug database.

PS: I posted the wrong bug number. Now corrected.

oliver1974
August 8th, 2007, 08:25 AM
I'm afraid I'll have to revive this thread...

what's the status of this bug? Sun sees this as closed..

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6429775

...but it isn't.. every now and then, dialogs in swing break and get rendered with
grey-only content, get resized without reason, change position from time to time and so on...

You can reproduce this behaviour with Netbeans 5.5.1 and 6.0 M10 (preview version)
and (especially) the often used "Find" dialog.

Well, actually you need some time to reproduce this, because 10-15 times the "Find" dialog
gets rendered ok.... the 16th time it breaks.

Yes, I use the latest JVM....

This is annoying as hell.

With Sun regarding this as closed und no activity here either (regarding Java/Swing/Compiz)
we're left alone in the cold?

I know the old hack AWT_TOOLKIT=MToolkit... but this never REALLY worked for me.. because every now and then,
the keyboard was rendered useless (in Java apps), with the latest Java VM it kills the keyboard at once, at least
for me.

derkosak
September 5th, 2007, 09:58 PM
none of these solutions work, at least not using XGL+ATI on Ubuntu =/
anything else we can do?
You should download JDK 6 update 1 build b01 from http://jdk6.dev.java.net
what is the version reported by your java installation?