Scilab does not start after some upgrades on Ubuntu Xenial
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mesa |
Won't Fix
|
High
|
|||
libjogl2-java (Ubuntu) |
Fix Released
|
Undecided
|
Timo Aaltonen | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Artful |
Fix Released
|
Undecided
|
Unassigned | ||
mesa (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Xenial |
Invalid
|
Undecided
|
Unassigned | ||
Artful |
Invalid
|
Undecided
|
Unassigned | ||
scilab (Debian) |
Fix Released
|
Unknown
|
|||
scilab (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Xenial |
Invalid
|
Undecided
|
Unassigned | ||
Artful |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[Impact]
Software that use libjogl2-java (Scilab, Matlab,...) fail to run, because Mesa dropped 'Gallium' from the renderer string.
[Test case]
Steps to reproduce:
1. have installed Scilab on Ubuntu Xenial system
2. install system updates
3. try to launch Scilab from GUI - it does not start
4. try to launch Scilab from terminal - it does not start with the following output in the terminal:
$ scilab
Could not create a Scilab main class. Error:
Exception in thread "main" java.lang.
at com.jogamp.
at com.jogamp.
at com.jogamp.
at com.jogamp.
at com.jogamp.
at com.jogamp.
at java.security.
at com.jogamp.
at com.jogamp.
at com.jogamp.
at com.jogamp.
at com.jogamp.
at org.scilab.
at org.scilab.
at org.scilab.
Scilab cannot create Scilab Java Main-Class (we have not been able to find the main Scilab class. Check if the Scilab and thirdparty packages are available).
Expected results:
Scilab works normally on Ubuntu 16.04 LTS system.
Actual results:
see error above.
[Regression potential]
The fix is a simple oneliner that allows libjogl2-java to detect Mesa with both new and original version of Mesa.
Changed in scilab (Debian): | |
status: | Unknown → New |
Changed in mesa: | |
importance: | Unknown → High |
status: | Unknown → Confirmed |
no longer affects: | scilab |
Changed in scilab (Debian): | |
status: | New → Fix Released |
Changed in scilab (Ubuntu): | |
status: | Confirmed → Invalid |
Changed in scilab (Ubuntu Xenial): | |
status: | Confirmed → Invalid |
Changed in scilab (Ubuntu Artful): | |
status: | Confirmed → Invalid |
Changed in mesa (Ubuntu): | |
status: | Confirmed → Invalid |
Changed in mesa (Ubuntu Xenial): | |
status: | Confirmed → Invalid |
Changed in mesa (Ubuntu Artful): | |
status: | Confirmed → Invalid |
description: | updated |
Changed in mesa: | |
status: | Confirmed → Won't Fix |
Software rendering with recent mesa (either LLVMPipe, softpipe or swr) breaks matlab.
Seen with MATLAB 2016a on Kubuntu 17.04 with the latest (git) mesa as of today.
Graphic commands (e.g. plot) hang and make it impossible to close Matlab cleanly.
On llvmpipe the 'opengl info' matlab command crashes with
Error using hgopengl RuntimeExceptio n: Waited 5000ms for: <38d5ebf2, 64757a04>[count 2 [ add. 0, orig 2], qsz 0, owner SharedResourceR unner] - <main> common. util.locks. RecursiveLockIm pl01Unfairish. lock(RecursiveL ockImpl01Unfair ish.java: 198) opengl. GLProfile. initSingleton( GLProfile. java:199) opengl. GLProfile. getDefaultDevic e(GLProfile. java:2003) opengl. GLCapabilities. <init>( GLCapabilities. java:84) hg.uij. OpenGLUtils$ MyGLListener. getGLInformatio n(OpenGLUtils. java:320) hg.uij. OpenGLUtils$ MyGLListener. getGLData( OpenGLUtils. java:498) hg.uij. OpenGLUtils. getGLData( OpenGLUtils. java:78)
Java exception occurred:
java.lang.
<Startup Class Loader>, add.owner Startup Class Loader-
at jogamp.
at com.jogamp.
at com.jogamp.
at com.jogamp.
at com.mathworks.
at com.mathworks.
at com.mathworks.
Error in hgopengl
On softpipe, the same command hangs.
This is curious because matlab has itself a software rendering mode, that seems to rely on mesa X11. The opengl info for it returns
SupportsDep
So, it looks like mesa was supporting matlab 2016a just fine at the time of 10.5.2 and that we are now facing a regression.