# P2D/P3D sketches won’t start on Ubuntu 20.04

**URL:** <https://discourse.processing.org/t/p2d-p3d-sketches-won-t-start-on-ubuntu-20-04/22186>\
**Category:** Processing\
**Created:** [June 26, 2020, 9:12pm UTC](https://discourse.processing.org/t/p2d-p3d-sketches-won-t-start-on-ubuntu-20-04/22186 "2020-06-26T21:12:33Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![villares](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/villares/32/3166_2.png) [@villares](https://discourse.processing.org/u/villares)\
**Post date:** [June 26, 2020, 9:12pm UTC](https://discourse.processing.org/t/p2d-p3d-sketches-won-t-start-on-ubuntu-20-04/22186/1 "2020-06-26T21:12:33Z")

</div>

This looks similar to an older issue: [[SOLVED] P2D/P3D sketches won't start on fresh Ubuntu 18.04 installation](https://discourse.processing.org/t/solved-p2d-p3d-sketches-wont-start-on-fresh-ubuntu-18-04-installation/3568)

```auto
Profile GL4bc is not available on X11GraphicsDevice[type .x11, connection :0.0, unitID 0, handle 0x7f74d401d970, owner true, ResourceToolkitLock[obj 0x1524728a, isOwner true, <111bf4f6, 541978b1>[count 1, qsz 0, owner <main-FPSAWTAnimator#00-Timer0>]]], but: [GLProfile[GL4ES3/GL4.hw], GLProfile[GL2ES2/GL4.hw], GLProfile[GL4/GL4.hw], GLProfile[GL4/GL4.hw], GLProfile[GL3/GL4.hw], GLProfile[GL2GL3/GL4.hw]]

```

I wonder if anyone else is experiencing it and I might try to find/file an issue…

This seems relevant but I don’ t understand enough to act on it:  
[http://forum.jogamp.org/Crash-after-latest-mesa-driver-update-from-ppa-oibaf-td4040300.html](http://forum.jogamp.org/Crash-after-latest-mesa-driver-update-from-ppa-oibaf-td4040300.html)

Hardware is a Lenovo V310 with HD Graphics 620:

```auto
$ glxinfo -B
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel (0x8086)
    Device: Mesa Intel(R) HD Graphics 620 (KBL GT2) (0x5916)
    Version: 20.0.4
    Accelerated: yes
    Video memory: 3072MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) HD Graphics 620 (KBL GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 20.0.4
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.0.4
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 20.0.4
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

```

Opened an issue: [https://github.com/processing/processing/issues/6061](https://github.com/processing/processing/issues/6061)

---

<div class="post-metadata">

**Author:** ![villares](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/villares/32/3166_2.png) [@villares](https://discourse.processing.org/u/villares)\
**Post date:** [June 27, 2020, 9:46pm UTC](https://discourse.processing.org/t/p2d-p3d-sketches-won-t-start-on-ubuntu-20-04/22186/2 "2020-06-27T21:46:34Z")

</div>

There is this workaround I found reading the older related issue:

```auto
void settings() {
System.setProperty("jogl.disable.openglcore", "true");
size(400, 400, P3D);
}

```

`false` as in

```auto
System.setProperty("jogl.disable.openglcore", "false");

```

also works!

But there is no `System` in Python Mode so I’m out of luck for now ☹

---

<div class="post-metadata">

**Author:** ![GoToLoop](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/gotoloop/32/86_2.png) [@GoToLoop](https://discourse.processing.org/u/GoToLoop)\
**Post date:** [June 27, 2020, 10:08pm UTC](https://discourse.processing.org/t/p2d-p3d-sketches-won-t-start-on-ubuntu-20-04/22186/3 "2020-06-27T22:08:50Z")

</div>

> [@villares](#):
>
> But there is no System on “Python Mode” so I’m out of luck for now ☹

- [System (Java SE 11 & JDK 11 )](http://Docs.Oracle.com/en/java/javase/11/docs/api/java.base/java/lang/System.html#setProperty(java.lang.String,java.lang.String))
- [GLProfile (JOGL, NativeWindow and NEWT APIs)](http://JogAmp.org/deployment/jogamp-next/javadoc/jogl/javadoc/com/jogamp/opengl/GLProfile.html#disableOpenGLCore)

```auto
from java.lang import System

OPENGL_CORE_PROP = 'jogl.disable.openglcore'
BOOL = 'true'

print System.getProperty(OPENGL_CORE_PROP)
System.setProperty(OPENGL_CORE_PROP, BOOL)
print System.getProperty(OPENGL_CORE_PROP)

def settings():
    size(400, 400, P3D)
    smooth(8)
    noLoop()

def setup():
    print g.OPENGL_VENDOR
    print g.OPENGL_RENDERER
    print g.OPENGL_VERSION
    print g.GLSL_VERSION

```

---

<div class="post-metadata">

**Author:** ![villares](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/villares/32/3166_2.png) [@villares](https://discourse.processing.org/u/villares)\
**Post date:** [June 27, 2020, 10:23pm UTC](https://discourse.processing.org/t/p2d-p3d-sketches-won-t-start-on-ubuntu-20-04/22186/4 "2020-06-27T22:23:27Z")

</div>

Oh! Thank you so much! @GoToLoop as usual saves the day! 😃  
I tried some clumsy java imports and gave up!

---

<div class="post-metadata">

**Author:** ![sinistergeek](https://avatars.discourse-cdn.com/v4/letter/s/ee59a6/32.png) [@sinistergeek](https://discourse.processing.org/u/sinistergeek)\
**Post date:** [August 23, 2020, 3:03am UTC](https://discourse.processing.org/t/p2d-p3d-sketches-won-t-start-on-ubuntu-20-04/22186/5 "2020-08-23T03:03:41Z")

</div>

Profile GL4bc is not available on X11GraphicsDevice[type .x11, connection :0, unitID 0, handle 0x7fd0f40227c0, owner true, ResourceToolkitLock[obj 0x62851b75, isOwner true, \<27878941, 24f938ec\>[count 1, qsz 0, owner \<main-FPSAWTAnimator#00-Timer0\>]]], but: [GLProfile[GLES1/GLES1.hw], GLProfile[GLES2/GLES3.hw], GLProfile[GL2ES1/GLES1.hw], GLProfile[GL4ES3/GL4.hw], GLProfile[GL2ES2/GL4.hw], GLProfile[GL4/GL4.hw], GLProfile[GLES3/GLES3.hw], GLProfile[GL4/GL4.hw], GLProfile[GL3/GL4.hw], GLProfile[GL2GL3/GL4.hw]]

---

<div class="post-metadata">

**Author:** ![villares](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/villares/32/3166_2.png) [@villares](https://discourse.processing.org/u/villares)\
**Post date:** [August 23, 2020, 9:30pm UTC](https://discourse.processing.org/t/p2d-p3d-sketches-won-t-start-on-ubuntu-20-04/22186/6 "2020-08-23T21:30:50Z")

</div>

Hi @sinistergeek,

I didn’t understand you. Is this an error message?  
Which mode are you working with, Java or Ptyhon, and what is your system like?  
I could make it work both on Java an Python with the tips from this thread.

Cheers!

---

<div class="post-metadata">

**Author:** ![sinistergeek](https://avatars.discourse-cdn.com/v4/letter/s/ee59a6/32.png) [@sinistergeek](https://discourse.processing.org/u/sinistergeek)\
**Post date:** [August 25, 2020, 5:11am UTC](https://discourse.processing.org/t/p2d-p3d-sketches-won-t-start-on-ubuntu-20-04/22186/7 "2020-08-25T05:11:11Z")

</div>

Thanks for the Reply!! Well i managed to solved it

---

<div class="post-metadata">

**Author:** ![villares](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/villares/32/3166_2.png) [@villares](https://discourse.processing.org/u/villares)\
**Post date:** [October 11, 2020, 4:50pm UTC](https://discourse.processing.org/t/p2d-p3d-sketches-won-t-start-on-ubuntu-20-04/22186/8 "2020-10-11T16:50:35Z")

</div>

My original issue was closed as duplicate of [https://github.com/processing/processing/issues/5476](https://github.com/processing/processing/issues/5476), but I’m a bit worried this is not going forward ☹

It got worse today (trying to track if there was some mesa driver update on my system yesterday), the ` System.setProperty("jogl.disable.openglcore", "true");` workaround doesn’t work anymore and I can’t work on P3D or P2D sketches on my machine.

UPDATE: after some driver updates, the workaround works again 🙂