-
-
Notifications
You must be signed in to change notification settings - Fork 19.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Official Godot binary won't run on several devices returning the same error. (32-bit Linux) #27496
Comments
CC @hpvb. Might be due to LTO. If so it's probably not a big loss to disable it on 32-bit x86. |
In my Lubuntu 18.04.2 i686 with Intel HD 3000 and Mesa 18.2.2 core profile 3.3. Linux 4.18.0-15 everything works with only this error(probably because I use Live version)
|
Live Lubuntu 18.10 i686 with Intel Core2 Intel T2500 - the issue is still present. |
Can confirm the issue: on my x86_64 system the
My system:
|
Can reproduce on Lubuntu 18.04.2 32 on GTX 970 with nouveau driver
with use_lto=no everything seems to work |
I can take a look tomorrow. |
I will try to reproduce. I haven't actually tried to run the 32bit linux binaries in a while. |
Using Lubuntu 18. Issue still present. Any workarounds? |
@JeremiahLR: Tried 3.1 or 3.1.1? |
It was 3.1.1. But you know what, I just downloaded the Mono Version with C# Support and it works on my Lubuntu! Great! |
Does it work with |
Can anyone test if the issue is still reproducible with 3.1.2 or the latest 3.2 build? Also with |
The issue is still present in 3.1.2. With
instead of three:
|
Mono builds work fine. |
Duplicate of #31743. 3.2 RC 1 should work fine (at least it does for me on Ubuntu Studio 18.04 i386). |
Godot version:
3.1-stable - 3.1.2 (Not Mono)
`
Same issue here:
#27226
OS/device including version:
Issue description:
Official 32-bit Godot binary returns the same error on several devices :
Running with
--video-driver GLES2 --verbose
doesn't change anything.But the
3.1-stable
binary compiled withscons p=x11
from the source runs fine.The text was updated successfully, but these errors were encountered: