NEWT errors when closing sketch on Linux

[benfry]

When running a static mode sketch with the current build, or when hitting the close box on a sketch with a draw() method, getting a lot of error messages:

Smooth is not supported by this hardware (or driver)
X11Util.Display: Shutdown (JVM shutdown: false, open (no close attempt): 4/4, reusable (open, marked uncloseable): 0, pending (open in creation order): 4)
X11Util: Open X11 Display Connections: 4
X11Util: Open[0]: NamedX11Display[:0.0, 0x910d458, refCount 1, unCloseable false]
X11Util: Open[1]: NamedX11Display[:0.0, 0x94b5340, refCount 1, unCloseable false]
X11Util: Open[2]: NamedX11Display[:0.0, 0x98a4890, refCount 1, unCloseable false]
X11Util: Open[3]: NamedX11Display[:0.0, 0x90e2470, refCount 1, unCloseable false]
X11Util.Display: Shutdown (JVM shutdown: true, open (no close attempt): 4/4, reusable (open, marked uncloseable): 0, pending (open in creation order): 4)
X11Util: Open X11 Display Connections: 4
X11Util: Open[0]: NamedX11Display[:0.0, 0x910d458, refCount 1, unCloseable false]
X11Util: Open[1]: NamedX11Display[:0.0, 0x94b5340, refCount 1, unCloseable false]
X11Util: Open[2]: NamedX11Display[:0.0, 0x98a4890, refCount 1, unCloseable false]
X11Util: Open[3]: NamedX11Display[:0.0, 0x90e2470, refCount 1, unCloseable false]

Might just be related to issue #1648.This is Ubuntu 10.04 (32-bit) under VMware.

[benfry]

Perhaps not a problem anymore?

[kles4enko]

I have the same problem.

I always see this when put "Esc" button for exit:

NEWT X11 Key: keyCode 0x9 keySym 0xFF1B (shifted: 0xFF1B), keyChar '�', javaVKey[US 0x1B, NN 0x1B]
X11Util.Display: Shutdown (JVM shutdown: false, open (no close attempt): 4/4, reusable (open, marked uncloseable): 0, pending (open in creation order): 4)
X11Util: Open X11 Display Connections: 4
X11Util: Open[0]: NamedX11Display[:1.0, 0x7ff5680c25f0, refCount 1, unCloseable false]
X11Util: Open[1]: NamedX11Display[:1.0, 0x7ff5680cf190, refCount 1, unCloseable false]
X11Util: Open[2]: NamedX11Display[:1.0, 0x7ff5542f5a40, refCount 1, unCloseable false]
X11Util: Open[3]: NamedX11Display[:1.0, 0x7ff5699aab60, refCount 1, unCloseable false]
X11Util.Display: Shutdown (JVM shutdown: true, open (no close attempt): 4/4, reusable (open, marked uncloseable): 0, pending (open in creation order): 4)
X11Util: Open X11 Display Connections: 4
X11Util: Open[0]: NamedX11Display[:1.0, 0x7ff5680c25f0, refCount 1, unCloseable false]
X11Util: Open[1]: NamedX11Display[:1.0, 0x7ff5680cf190, refCount 1, unCloseable false]
X11Util: Open[2]: NamedX11Display[:1.0, 0x7ff5542f5a40, refCount 1, unCloseable false]
X11Util: Open[3]: NamedX11Display[:1.0, 0x7ff5699aab60, refCount 1, unCloseable false]

---

OS: openSuse 12.3 x64

[aengelke]

The problem occours also by pressing the close button of the window or Alt+F4.

---

OS: Fedora 18 32bit

[codeanticode]

On Ubuntu 12.10 64bit, Radeon HD 6670, latest GL drivers, and AWT as windowing toolkit. Closing the sketch from the PDE pressing the stop button doesn't generate any errors, while closing the sketch by hitting the close button on the output window of the sketch give the following message:

X11Util.Display: Shutdown (JVM shutdown: false, open (no close attempt): 1/1, reusable (open, marked uncloseable): 1, pending (open in creation order): 2)
X11Util: Open X11 Display Connections: 1
X11Util: Open[0]: NamedX11Display[:0.0, 0x7fc94c1c0f50, refCount 1, unCloseable true]

I don't really know why this message is shown, and tried a couple of things to make it go away (removing the GLProfile.shutdown() call in PGL for example). Running a simple JOGL sample program (https://github.com/codeanticode/jogl2-tests/blob/master/src/test/animator/AnimatorAWT.java) generates the same error message, which seems to be generated by the GLProfile.shutdown() call itself. However, this call appears happen regardless of whether is invoked explicitly or not in the code, so it seems JOGL does it automatically. My conclusion is that the error is due to some issue in JOGL itself, so I'm unable to fix it in Processing.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.