I have no idea why, but ANY program that uses Java 3d completely freezes up my Intel 965GM laptop. This ALWAYS happens when starting or going fullscreen. X windows freezes. I have all the latest packages installed on my laptop via several Repositories. I checked all the relations to Java3d and re-installed all of them. I also deleted my /etc/X11/xorg.conf, and had SAX2 create a new file. SAME DEAL! This really sucks. Hopefully there is someone on this board who is very good, and knows what to look for/do. Cannot use, "makehuman", or "SweetHome3D".

Thanks for any & all help.

Not sure if I can help, but...

First things first:

Video card?
Driver for said video card?
What does glxgears do in terminal?
Can you possibly fire up the program in question via terminal and give us the output?

Also, another odd question...what audio are you using, and have you had any issues with sound as well?

Cheers,
Ghost

Video card - Intel 965GM - X3100
glxgears works perfectly
Alsa audio. Works just fine.


xorg.conf>

Section "Device"
BoardName "965 GM"
BusID "0:2:0"
Driver "intel"
Identifier "Device[0]"
Option "SaXDualHead"
Option "XAANoOffscreenPixmaps" "true"
Option "monitor-LVDS" "Monitor[0]"
Option "SaXDualMonitorVendor" "--> VESA"
Option "SaXDualOrientation" "LeftOf"
Option "SaXDualResolution" "1024x768"
Option "SaXDualMode" "Clone"
Option "SaXDualHSync" "31-50"
Option "SaXDualMonitorModel" "1024X768@60HZ"
Option "SaXDualVSync" "50-60"
Option "SaXExternal" "Identifier&EXT+DisplaySize&+VendorName&--> VESA+PreferredMode&1024x768+HorizSync&31-50+ModelName&1024X768@60HZ+VertRefresh&50-60"
Screen 0
VendorName "Intel"


Running in terminal is useless. Once the freeze occurs, I have to reboot.


The problem is obviously a conflict with my xorg.conf and java3d or java. I wish I knew what it was.
Thanks.

Or possibly the fact that you're running an Intel based video card and have no 3d capabilities in Linux?

I'm not 100% certain, but I believe 3D java requires you to have 3D capability.

Cheers,
Ghost

Everything worked just fine in Suse 10.3. I upgraded to 11.0 and the problem arose. Next time I will just save my /home partition and install the newer version that way, rather than update. Updating works, but not flawless. Something from my old version is clashing with the new updated version. I even ripped out all my old packages and re-installed all of them with the new 11.0 repositories. Strange.

Hmmm...if everything worked in 10.3 and not in 11.0, then it could be a number of things.

As you pointed it out, it could be something clashing (It's one of the reasons I flat out refuse to install anything that's not on my repository lists - I have smooth and simple upgrades every six months without a hitch) and if that's the case, you may very well need to do a backup of your /home and reinstall.

It might also behoove you to check and see if there's something they dropped in 11.0 that they had support for previously in 10.3, like your video card driver, etc.

It could also be something as simple as a new location for the file(s) needed for the program to run. New releases sometimes go, "We don't like that group of files in /etc/bin/ anymore, so now you'll find them in /opt/bin/" or something of that ilk.

Sometimes a symlink is the only thing standing between you and a stable OS.

I'm afraid however that I dropped out of the SuSE deal when I discovered Ubuntu, and I haven't been back in quite awhile.

But, my guess is that if you find someone who's knowledgeable in SuSE, or check their site, you'll find your answer rather quickly.

Cheers,
Ghost