scilab cannot create scilab java main class что делать
Scilab не может создавать Java Main-Class на Ubuntu 17.10 [duplicate]
Я установил Ubuntu 16.04.3 LTS на компьютер с AMD A4-4000 APU with Radeon(tm) HD Graphics и установил Scilab 5.5.2 здесь из официального репозитория (версия пакета 5.5.2-2ubuntu3).
Он работал нормально на 2017- 12-24, но сломано некоторым последним обновлением. Я могу опубликовать dpkg-log, но кажется, что он связан с MESA:
$ cat /var/log/dpkg.log* | grep «status installed.*mesa» 2018-01-11 14:51:08 status installed libglapi-mesa:amd64 17.2.4-0ubuntu1
16.04.2 2018-01-11 14:51:09 status installed libglapi-mesa:i386 17.2.4-0ubuntu1
16.04.2 2018-01-11 14:51:10 status installed libgl1-mesa-dri:amd64 17.2.4-0ubuntu1
16.04.2 2018-01-11 14:51:11 status installed libgl1-mesa-dri:i386 17.2.4-0ubuntu1
16.04.2 2018-01-11 14:51:16 status installed libegl1-mesa:amd64 17.2.4-0ubuntu1
16.04.2 2018-01-11 14:51:17 status installed libwayland-egl1-mesa:amd64 17.2.4-0ubuntu1
16.04.2 2018-01-11 14:51:18 status installed libosmesa6:amd64 17.2.4-0ubuntu1
16.04.2 2018-01-11 14:51:18 status installed libosmesa6:i386 17.2.4-0ubuntu1
16.04.2 2018-01-11 14:51:19 status installed libgl1-mesa-glx:amd64 17.2.4-0ubuntu1
16.04.2 2018-01-11 14:51:20 status installed libgl1-mesa-glx:i386 17.2.4-0ubuntu1
16.04.2 2018-01-11 14:51:20 status installed libgles2-mesa:amd64 17.2.4-0ubuntu1
16.04.2 2018-01-11 14:51:21 status installed mesa-vdpau-drivers:amd64 17.2.4-0ubuntu1
16.04.2 2018-01-12 12:24:25 status installed mesa-va-drivers:amd64 17.2.4-0ubuntu1
Моя системная информация:
In Software & amp; Обновления software-properties-gtk У меня есть только одно предложение об установке пакета amd64-microcode. Его установка не помогает.
Scilab does not start after some upgrades on Ubuntu Xenial
Bug Description
Software that use libjogl2-java (Scilab, Matlab. ) fail to run, because Mesa dropped ‘Gallium’ from the renderer string.
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.
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
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
Version: ‘2.1 Mesa 10.5.2’
Vendor: ‘Brian Paul’
Renderer: ‘Mesa X11’
MaxTexture Size: 16384
Visual: ‘Visual 0x72, (RGBA 32 bits (8 8 8 8), Z depth 16 bits, Hardware acceleratio…’
Software: ‘true’
HardwareS upportLevel: ‘none (known graphics driver issues)’
SupportsGraphi csSmoothing: 0
SupportsDep thPeelTranspare ncy: 1
SupportsAlignVe rtexCenters: 0
Extensions: <151x1 cell>
MaxFrameBuffer Size: 16384
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.
I won’t be looking at the issue, I’m afraid yet here’s a couple of ideas/suggestions that should help:
I’ll try to work on the last point aka get more verbose information.
In any case, my intent was mostly to assure that a trace of the problem is present on the bug tracker, in case other users run into the issue and possibly to guide them if they need to get new hardware with the need to run Matlab on it.
Unfortunately the Matlab experience on Linux is sad. Not working with nouveau. Not working with soft rendering, either. Working with its own soft rendering, but with many limitations. Fortunately, it seems OK on intel graphics.
Sergio, I installed the 30-day trial of Matlab r2017b and typed ‘opengl info’ in the command window. I did not get a java exception. I got an error message that reads:
«»»
MATLAB has experienced a low-level graphics error, and may not have drawn correctly.
Read about what you can do to prevent this issue at Resolving Low-Level Graphics Issues then restart MATLAB.
To share details of this issue with MathWorks technical support,
please include this file with your service request.
«»»
I don’t see that issue when using NVIDIA’s driver.
I used apitrace to create a trace of Matlab’s GL calls with llvmpipe and with NVIDIA’s linux driver. It looks like Matlab begins by trying to find the highest supported GL version of the core profile. With NVIDIA’s driver it finds 4.5. With llvmpipe it finds 3.3.
Then, it also tries to create compatibility profile context. With NVIDIA’s driver it again gets a 4.5 context. With llvmpipe, we don’t have such profiles and Matlab stops after getting a GL 3.1 context.
Finally, with llvmpipe, Matlab tries to create a 3.3 compatibility profile and fails. It then successfully creates a legacy context with glXCreateNewCon text(). It calls glGetIntegerv( GL_MAJOR/ MINOR_VERSION) then destroys the context.
As far as I an tell, Matlab simply doesn’t accept llvmpipe’s context/version offerings. Either that’s by design or there’s some sort of logic bug in MatLab that gives up on GL support after failing to create a particular kind of context.
You could try installing some older versions of Mesa to see if Matlab 2016a works/fails. But Matlab 2017b seems to act differently.
thanks for testing! Indeed, I think that Matlab 2016 is fine with the NVIDIA proprietary driver. However, I cannot use it because I have a KDE desktop and the nvidia proprietary drivers hang the konsole as per
Furthermore, I prefer the free drivers when my graphics card copes with them.
The different response to the opengl info may be related to a slightly different mesa/graphics stack combination. Incidentally, it is unclear to me whether you got the «MATLAB has experienced a low-level graphics error» with llvmpipe or the hardware driver.
Matlab seems to use some java library to interact with opengl and I do not know if it is something commercial or something open source that MathWorks has adapted to its needs. In the latter case, testing might be easier.
. looks like also scilab has issues with the software renderer. With LIBGL_ALWAYS_ SOFTWARE= 1, scilab cannot plot (shows empty plot windows). May be a totally unrelated issue, but I think that scilab and matlab have in common the use of jogamp for graphics rendering.