First result:
when you launch scilab, it is a shell script that launch the gui.
This gui is composed of one "console" = zterm and of one "menu" = scilex.
If you launch scilab by hand, i.e. :
$ /usr/lib/scilab/bin/zterm -f arial -e /usr/lib/scilab/bin/scilex
then scilab works.
There is a
The idea "wait for version N+1 to remove this bug" is not the good way
to think !
Version N+1 will come with new features, with new bugs and *maybe* with fix for
your bug discussed here.
This is a common behaviour in Open Source communities : escape ahead...
The good way to think is then : how d
Please not misunderstand me :
- community will not debug this driver because we would prefer that Nvidia
release it in [L]GPL form ;o)...
- and because we have, technically, little access to its internals...
And about my question about the test cases: I'm searching for a method
to circumvent thi
I have a similar problem.
Community wil certainly have not the skill / time to debug the
nvidia.ko
How to identify that theses oops are caused by the nvidia proprietary
driver ?
- I ran memtest86 during several minutes and no problemo
- I ran Xorg with driver nv and no problemo
- My computer
