JRViewer Error: failed to create a pipe screen for i965

Problems with Java, jogl, etc?
Post Reply
amw
Posts: 1
Joined: Wed 8. May 2013, 23:21

JRViewer Error: failed to create a pipe screen for i965

Post by amw » Wed 8. May 2013, 23:26

Hello,

my newly checkout trunk version of jreality does not show the scenegraph.

The console holds the following output:

Code: Select all

libEGL warning: failed to create a pipe screen for i965
JOGL3Viewer constuctor called
Native[GL4bc false, GL4 false, GL3bc true [3.1 (Compatibility profile, arb, ES2 compatible, FBO, hardware)], GL3 true [3.1 (Compatibility profile, arb, ES2 compatible, FBO, hardware)], GL2 true [3.1 (Compatibility profile, arb, ES2 compatible, FBO, hardware)], GL2ES1 true, GLES1 true [1.0 (ES profile, FBO, hardware)], GL2ES2 true, GLES2 true [2.0 (ES profile, ES2 compatible, FBO, hardware)]], Profiles[GLProfile[GL2ES2/GL3bc.hw], GLProfile[GL2ES1/GL3bc.hw], GLProfile[GL2/GL2.hw], GLProfile[GL3/GL3.hw], GLProfile[GL3bc/GL3bc.hw], GLProfile[GLES2/GLES2.hw], GLProfile[GLES1/GLES1.hw], GLProfile[GL2GL3/GL3bc.hw], GLProfile[GL3bc/GL3bc.hw], , default GLProfile[GL3bc/GL3bc.hw]]
calling JOGLViewer.dispose()
Info: Nativewindow X11 Error: 3 - BadWindow (invalid Window parameter), dpy 0x7f0c88334070, id 4200013, # 3966: 20:0 X_GetProperty
Info: Nativewindow X11 Error: 3 - BadWindow (invalid Window parameter), dpy 0x7f0c88334070, id 4200013, # 3967: 20:0 X_GetProperty
How can I remove this error and start running the JRviewer?

Regards
amw

System
Ubuntu 13.04 64bit
openjdk-7-jdk
Eclipse 4.2

benjamin.kutschan
Posts: 48
Joined: Mon 16. May 2011, 16:29

Re: JRViewer Error: failed to create a pipe screen for i965

Post by benjamin.kutschan » Fri 10. May 2013, 13:43

Maybe try sun jdk.
Looks like a jogamp bug to me.

Andre
Posts: 226
Joined: Fri 18. Sep 2009, 11:30

Re: JRViewer Error: failed to create a pipe screen for i965

Post by Andre » Mon 12. Aug 2013, 09:15

One of us had the same problems and we have updated our jogl.jars to latest release. Can you confirm this Bug solved?!?

Post Reply