Bug 110955 - Mesa 18.2.8 implementation error: Invalid GLSL version in shading_language_version()
Summary: Mesa 18.2.8 implementation error: Invalid GLSL version in shading_language_ve...
Status: NEW
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/nouveau (show other bugs)
Version: 18.2
Hardware: x86 (IA32) Linux (All)
: medium minor
Assignee: Nouveau Project
QA Contact: Nouveau Project
URL:
Whiteboard:
Keywords: have-backtrace
Depends on:
Blocks:
 
Reported: 2019-06-21 17:11 UTC by power.cyan
Modified: 2019-08-07 16:58 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Wine output from trying to run windemic.exe, it happens also with LauncherFallour.exe. It dosen't seems to be a wine issue if I run in 64-bit machine with same OS(Xubuntu 18.04) it works. (2.86 KB, text/plain)
2019-06-21 17:11 UTC, power.cyan
Details
Print GL profile and unknown GLSL version. (672 bytes, patch)
2019-06-28 15:01 UTC, Emil Velikov
Details | Splinter Review
glxinfo (19.42 KB, text/plain)
2019-07-10 14:50 UTC, power.cyan
Details
patched with both suggested patches (6.53 KB, text/plain)
2019-07-10 17:37 UTC, power.cyan
Details
Patched with just the latest suggested patch. (4.56 KB, text/plain)
2019-07-10 17:39 UTC, power.cyan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description power.cyan 2019-06-21 17:11:04 UTC
Created attachment 144606 [details]
Wine output from trying to run windemic.exe, it happens also with LauncherFallour.exe. It dosen't seems to be a wine issue if I run in 64-bit machine with same OS(Xubuntu 18.04) it works.
Comment 1 Emil Velikov 2019-06-21 17:41:23 UTC
AFAICT there's a couple of things here:
 - the crash
Most likely a wine bug, since the GL spec clearly says that glGetString (the only API which can give this message) can return 0/NULL on error.

 - nouveau/mesa complains about unknown GLSL version

That should not happen. What hardware are you running on, do you have any changes to your drirc?
Comment 2 Emil Velikov 2019-06-21 17:42:30 UTC
s/wine/wine or application/
Comment 3 Emil Velikov 2019-06-28 15:01:07 UTC
Created attachment 144675 [details] [review]
Print GL profile and unknown GLSL version.

Forgot the more constructive parts:
 - please attach (plain-text) the output of glxinfo
 - if you can build mesa - what's the output of wine with the attached patch
Comment 4 power.cyan 2019-07-10 14:50:45 UTC
Created attachment 144753 [details]
glxinfo

Attached the output of glxinfo, tryed to build mesa from src it was successfull, but havem't patched yet.
Comment 5 Ilia Mirkin 2019-07-10 14:53:20 UTC
That patch is missing the actual version... given that this is a NV18, this should be fixed by

https://cgit.freedesktop.org/mesa/mesa/commit/?id=0349bc3ce2b399082593ddcf1d28782a4566bc08
Comment 6 power.cyan 2019-07-10 17:37:05 UTC
Created attachment 144754 [details]
patched with both suggested patches

I tried to compile with the patches and I get errors, the output of the build is attached. First patched with the getstring.patch and context.patch.
Comment 7 power.cyan 2019-07-10 17:39:12 UTC
Created attachment 144755 [details]
Patched with just the latest suggested patch.

Tried without getstring.patch instead used the latest suggested patch for context.patch. It error out to, the output is attached.
Comment 8 Ilia Mirkin 2019-07-10 18:14:25 UTC
../src/mesa/main/context.c:2:7: error: invalid suffix "d81f1..2734693" on integer constant
 index 03d81f1..2734693 100644

Looks like your patch-application skills require some work.

You should just be able to build mainline now -- it will have the change in question already.
Comment 9 power.cyan 2019-07-10 20:00:28 UTC
That is true my patching skills are horrible. I see I try the patching again let see if its builds, just because some practice can't hurt, if fails again I go with the mainline that has already been patched.
Comment 10 power.cyan 2019-07-10 20:04:09 UTC
Oh almost forget tank you for the quick response to my problem.
Comment 11 Juan A. Suarez 2019-08-07 16:58:34 UTC
This should be fixed in Mesa 19.1.4.

Can you try?


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.