Bug 26704 - scilab fails with an error creating the main java class
Summary: scilab fails with an error creating the main java class
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-05-29 13:39 CEST by Bernard SIAUD
Modified: 2021-09-07 14:11 CEST (History)
1 user (show)

See Also:
Source RPM: scilab-6.1.0-1.mga7.x86_64.rpm
CVE:
Status comment:


Attachments

Description Bernard SIAUD 2020-05-29 13:39:51 CEST
[troumad@localhost info]$ scilab
Impossible de créer une classe principale de Scilab. Erreur :
Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> profileImpl GL4bc !!! not mapped 
	at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
	at com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1924)
	at com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
	at com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1843)
	at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
	at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
	at java.security.AccessController.doPrivileged(Native Method)
	at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
	at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
	at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
	at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
	at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
	at org.scilab.modules.gui.SwingView.<init>(Unknown Source)
	at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
	at org.scilab.modules.core.Scilab.<init>(Unknown Source)

Scilab ne peut pas créer la classe principale Java Scilab (Impossible de trouver la classe Scilab principale. Vérifiez si les paquets Scilab et thirdparty sont accessibles).
[troumad@localhost info]$
Comment 1 Dave Hodgins 2020-05-29 15:55:41 CEST
It's working on my system, so that rules out a problem with scilab itself.
It's failure on that system may be due to an rpm package that I have installed,
that isn't installed on that system, a configuration issue, or something related
to the hardware drivers. There are other possible causes, but those are the
first that come to mind.

Easiest one of those possibilities to eliminate is a configuration issue.
Please create a new user on that system, log out of the current user, log in
as the new user, and check to see if scilab works for the new user.

Following info added, just for information.

While https://www.mathworks.com/matlabcentral/answers/407942-what-does-this-mean-when-i-run-matlab-in-ubuntu-16-04 is for matlab rather then scilab, the error message is the same.
Unfortunately doesn't have an option to force software opengl rendering, like
matlab does.

Summary: Can't run => scilab fails with an error creating the main java class
CC: (none) => davidwhodgins

Comment 2 Bernard SIAUD 2020-05-29 16:17:18 CEST
same error with a new user.

I have sarch a java rpm with opengl. I have not found.

With opengl, I have only this rpm :
lib64qt5opengl-devel
lib64qt5opengl5
lib64qt5opengl4
python3-opengl
Comment 3 Dave Hodgins 2020-05-29 16:27:09 CEST
I have the following opengl rpm packages installed, though I doubt it's a
missing package causing the problem.
$ rpm -qa|grep opengl|sort
lib64qt5opengl5-5.12.6-3.mga7
lib64qtopengl4-4.8.7-26.1.mga7
libqtopengl4-4.8.7-26.1.mga7
python2-qt4-opengl-4.12.3-4.mga7
python2-qt5-opengl-5.12.1-2.mga7
python3-opengl-3.1.3b2-1.mga7
python3-qt5-opengl-5.12.1-2.mga7
python-opengl-3.1.3b2-1.mga7
vlc-plugin-opengl-3.0.10-1.mga7.tainted

Most likely it's a graphic driver issue. On my system ...
# lspcidrake -v|grep Card
Card:ATI Radeon HD 5000 to HD 6300 (radeon/fglrx): Advanced Micro Devices, Inc. [AMD/ATI]|Cedar [Radeon HD 5000/6000/7350/8350 Series] [DISPLAY_VGA] (vendor:1002 device:68f9 subv:1043 subd:03ca)
Comment 4 Bernard SIAUD 2020-05-29 17:39:47 CEST
I have a computer with Cauldron, scilab work.

But, it's besser !
With this computer, I do a ssh in my computer with mga7 and run scilab : it's run !

[troumad@localhost SE]$ ssh 192.168.XXX
Password:
Last login: Fri May 29 17:31:44 2020 from 192.168.1.15
[troumad@localhost ~]$ scilab
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
X Error of failed request:  GLXBadContext
  Major opcode of failed request:  150 (GLX)
  Minor opcode of failed request:  6 (X_GLXIsDirect)
  Serial number of failed request:  54
  Current serial number in output stream:  53
libEGL warning: DRI2: failed to authenticate
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
Caught handled GLException: X11GLXDrawableFactory - Could not initialize shared resources for X11GraphicsDevice[type .x11, connection localhost:10.0, unitID 0, handle 0x0, owner false, ResourceToolkitLock[obj 0x1164e7fe, isOwner false, <5c2d4a41, 76710445>[count 0, qsz 0, owner <NULL>]]] on thread main-SharedResourceRunner
    [0]: jogamp.opengl.x11.glx.X11GLXDrawableFactory$SharedResourceImplementation.createSharedResource(X11GLXDrawableFactory.java:306)
    [1]: jogamp.opengl.SharedResourceRunner.run(SharedResourceRunner.java:353)
    [2]: java.lang.Thread.run(Thread.java:748)
Caused[0] by GLException: main-SharedResourceRunner: Unable to create temp OpenGL context(1) on thread main-SharedResourceRunner
    [0]: jogamp.opengl.x11.glx.X11GLXContext.createImpl(X11GLXContext.java:390)
    [1]: jogamp.opengl.GLContextImpl.makeCurrentWithinLock(GLContextImpl.java:765)
    [2]: jogamp.opengl.GLContextImpl.makeCurrent(GLContextImpl.java:648)
    [3]: jogamp.opengl.GLContextImpl.makeCurrent(GLContextImpl.java:586)
    [4]: jogamp.opengl.x11.glx.X11GLXDrawableFactory$SharedResourceImplementation.createSharedResource(X11GLXDrawableFactory.java:277)
    [5]: jogamp.opengl.SharedResourceRunner.run(SharedResourceRunner.java:353)
    [6]: java.lang.Thread.run(Thread.java:748)

For the config of the computer with mga7 :
[root@localhost ~]# lspcidrake -v|grep Card
Card:Intel 810 and later: Intel Corporation|3rd Gen Core processor Graphics Controller [DISPLAY_VGA] (vendor:8086 device:0166 subv:1028 subd:057d) (rev: 09)
sdhci_pci       : O2 Micro, Inc.|OZ600FJ0/OZ900FJ0/OZ600FJS SD/MMC Card Reader Controller (vendor:1217 device:8221 subv:1028 subd:057d) (rev: 05)
[root@localhost ~]# rpm -qa|grep opengl|sort
lib64qt5opengl5-5.12.6-3.mga7
lib64qt5opengl-devel-5.12.6-3.mga7
lib64qtopengl4-4.8.7-26.1.mga7
python3-opengl-3.1.3b2-1.mga7


The computer with Cauldron :
[root@localhost ~]# lspcidrake -v|grep Card
Card:Intel 810 and later: Intel Corporation|3rd Gen Core processor Graphics Controller [DISPLAY_VGA] (vendor:8086 device:0166 subv:1028 subd:057d) (rev: 09)
sdhci_pci       : O2 Micro, Inc.|OZ600FJ0/OZ900FJ0/OZ600FJS SD/MMC Card Reader Controller (vendor:1217 device:8221 subv:1028 subd:057d) (rev: 05)
[root@localhost ~]# rpm -qa|grep opengl|sort
lib64qt5opengl5-5.12.6-3.mga7
lib64qt5opengl-devel-5.12.6-3.mga7
lib64qtopengl4-4.8.7-26.1.mga7
python3-opengl-3.1.3b2-1.mga7



scilab run, but the message are not the same (the last is not good) :
[troumad@localhost photos]$ scilab

(scilab-bin:2428827): Gtk-WARNING **: 17:38:24.966: Theme parsing error: colors.css:71:44: Invalid number for color value

(scilab-bin:2428827): Gtk-WARNING **: 17:38:24.966: Theme parsing error: colors.css:72:44: Invalid number for color value

(scilab-bin:2428827): Gtk-WARNING **: 17:38:24.966: Theme parsing error: colors.css:74:53: Invalid number for color value

(scilab-bin:2428827): Gtk-WARNING **: 17:38:24.966: Theme parsing error: colors.css:75:53: Invalid number for color value

(scilab-bin:2428827): Gtk-WARNING **: 17:38:24.966: Theme parsing error: colors.css:76:56: Invalid number for color value

(scilab-bin:2428827): Gtk-WARNING **: 17:38:24.966: Theme parsing error: colors.css:77:65: Invalid number for color value
/usr/bin/scilab : ligne 1008 : 2428827 Erreur de segmentation  (core dumped)"$SCILABBIN" "$@"
[troumad@localhost photos]$
Comment 5 Bernard SIAUD 2020-05-29 17:41:20 CEST
Error : the config with the Cauldron :
[root@localhost ssh]# rpm -qa|grep opengl|sort
lib64qt5opengl5-5.14.1-9.mga8
lib64qt5opengl-devel-5.14.1-9.mga8
python3-opengl-3.1.3b2-4.mga8
[root@localhost ssh]# lspcidrake -v|grep Card
Card:NVIDIA GeForce 635 series and later: NVIDIA Corporation|GK106 [GeForce GTX 660] [DISPLAY_VGA] (vendor:10de device:11c0 subv:1462 subd:2872) (rev: a1)
Comment 6 Lewis Smith 2020-06-01 19:03:38 CEST
Trying Mageia 7 with:
 scilab-6.1.0-1.mga7
 java-1.8.0-openjdk-1.8.0.252-1.b09.1.mga7 
 lib64qt5opengl5-5.12.6-3.mga7
 lib64qtopengl4-4.8.7-26.1.mga7
 python3-opengl-3.1.3b2-1.mga7
I do not get the error reported. SciLab starts:
 $ scilab
Exception in thread "AWT-EventQueue-0" java.lang.ArrayIndexOutOfBoundsException: 20
       at org.scilab.modules.ui_data.filebrowser.ScilabFileBrowserModel.getChild(Unknown Source)
...
 (but the extent to which it works is iffy).

This is under LxQt desktop, but noting the last errors in comment 4, I will re-try under a Gtk desktop.

CC: (none) => lewyssmith

Comment 7 Lewis Smith 2020-06-01 20:27:25 CEST
Trying under LXDE (which I think is Gtk). In the previous comment, I cited only the first of very many console messages - but I am unsure now whether I simply started SciLab, or played a bit. Now, just launching the application:
 $ scilab
there are no immediate console messages. I had to poke a bit before they started pouring out:-
Exception in thread "AWT-EventQueue-0" com.jogamp.opengl.GLException: Caught GLException: AWT-EventQueue-0: createImpl ARB n/a but required, profile > GL2 requested (OpenGL >= 3.1). Requested: GLProfile[GL3bc/GL3bc.hw], current: 3.1 (Compat profile, compat[ES2, ES3], FBO, hardware) - 3.1 Mesa 20.0.7
	at com.jogamp.opengl.awt.GLJPanel$OffscreenBackend.initialize(GLJPanel.java:1795)

My graphics:
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7310] (prog-if 00 [VGA controller])
	Kernel driver in use: radeon
	Kernel modules: radeon

As usual, getting it to work is enigmatic. But no crash. There are other bugs open for SciLab, it does not seem solid at all.
I do not see what more we can ask. The only computer cited with this problem has Intel video (comment 4, "the computer with mga7"). I do not think this is yet in a state to assign, before better pinning down the error.
---------
@Dave : you have several computers, any with Intel graphics?
Comment 8 Dave Hodgins 2020-06-01 21:21:13 CEST
I've tested on two Mageia 7 x86_64 systems, and scilab is working on both of
them.

# lspcidrake -v|grep Card
Card:ATI Radeon HD 5000 to HD 6300 (radeon/fglrx): Advanced Micro Devices, Inc. [AMD/ATI]|Cedar [Radeon HD 5000/6000/7350/8350 Series] [DISPLAY_VGA] (vendor:1002 device:68f9 subv:1043 subd:03ca)

]# lspcidrake -v|grep Card
Card:Intel 810 and later: Intel Corporation|82G33/G31 Express Integrated Graphics Controller [DISPLAY_VGA] (vendor:8086 device:29c2 subv:103c subd:2a6f) (rev: 02)

So it's not all Intel systems where it's failing, just newer ones. The intel
system I have where it's working has a bios date of 01/17/2008. The radeon
one has 10/16/2012.
Comment 9 Lewis Smith 2020-06-03 21:43:01 CEST
> So it's not all Intel systems where it's failing, just newer ones
We have to believe this for the moment, despite just 1 example.

Assigning to NicolasS for Scilab.

CC: lewyssmith => (none)
Assignee: bugsquad => nicolas.salguero

Comment 10 Nicolas Salguero 2020-06-05 10:51:23 CEST
Hi,

In fact the OpenGL errors come from the package jogl2.  That package is only used by scilab so all the other java packages that use OpenGL are not affected by issues with that package.

In Mageia 7 and Cauldron, I updated a patch to make jogl2 work with recent gallium drivers too (nouveau, Intel iris) but I think that Mesa 20.1, which is only available in Cauldron, broke something again in the Mesa/Gallium detection.

Best regards,

Nico.
Nicolas Salguero 2021-01-20 15:40:42 CET

Assignee: nicolas.salguero => pkg-bugs

Comment 11 Aurelien Oudelet 2021-07-06 13:15:13 CEST
Mageia 7 is EOL since July 1st 2021.
There will not have any further bugfix for this release.

You are encouraged to upgrade to Mageia 8 as soon as possible.

@reporter, if this bug still apply with Mageia 8, please let us know it.

@packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead.

This bug report will be closed OLD if there is no further notice within 1st September 2021.
Comment 12 Marja Van Waes 2021-09-07 14:11:04 CEST
Hi bug reporter and hi assignee and others involved,

Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly.

This report is being closed as OLD because it was filed against Mageia 7, for which  support ended on June 30th 2021.

Thanks,
Marja

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.