Failure after termux arm64 upgrade

[ddkwork]

sudo pacman -S go xorg-server-devel libxcursor libxrandr libxinerama libxi

[ddkwork]

arch linux latest tested

[andydotxyz]

Can you please share what device this is? It does not look like a standard arm64 linux computer

[ddkwork]

Can you please share what device this is? It does not look like a standard arm64 linux computer

wubantu also not work

[ddkwork]

Can you please share what device this is? It does not look like a standard arm64 linux computer

termux proot linux

[ddkwork]

it seem like the opengl version is wrong.

I was tested 3 linuxs:
Wubantu,arch,manjaro.

Fyne was working Some days ago, some one day not work when exec command "apt upgrade".

[andydotxyz]

It sounds like your upgrade somehow removed or disabled the MIT-SHM X11 extension

[ddkwork]

It sounds like your upgrade somehow removed or disabled the MIT-SHM X11 extension

Hello you, what i should apt install?

[ddkwork]

Nothing search found.

[andydotxyz]

I don't know - I have never worked with that combination.
All I can suggest is you go through the setup instructions again so all the right libraries are installed.

[ddkwork]

I don't know - I have never worked with that combination.
All I can suggest is you go through the setup instructions again so all the right libraries are installed.

I was reinstall system and exec this:

sudo pacman -S go xorg-server-devel libxcursor libxrandr libxinerama libxi

sudo apt-get install golang gcc libgl1-mesa-dev xorg-dev

But not working.

[andydotxyz]

Is it exactly the same error? I see in your previous messages errors about gl missing as well, so it's not entirely clear at what stage things are failing...

[ddkwork]

Is it exactly the same error? I see in your previous messages errors about gl missing as well, so it's not entirely clear at what stage things are failing...

gioui was working with Wayland.

[andydotxyz]

You can test Fyne wayland support (not yet on by default) using go run -tags wayland ..
If your platform is not X this may help a lot!

[ddkwork]

You can test Fyne wayland support (not yet on by default) using go run -tags wayland ..
If your platform is not X this may help a lot!

Fyne still not working use wayland, gio was working. But i love fyne only.

I was input this command :

go run . -tags wayland

[andydotxyz]

You are not managing to run the wayland tags. Your file name is in the wrong position.

go run -tags wayland main.go - apologies if my earlier message was not clear

[ddkwork]

You are not managing to run the wayland tags. Your file name is in the wrong position.

go run -tags wayland main.go - apologies if my earlier message was not clear

[andydotxyz]

Thanks, it's not moved to Wayland then ;)

[Bluebugs]

If I remember correctly, the x11 shm extension is for a software backend. Something mesa would fallback to if the gpu driver isn't installed. As you are mentioning arm and also Wayland, what is your gpu and are you using x11 or Wayland for the display system?

[ddkwork]

If I remember correctly, the x11 shm extension is for a software backend. Something mesa would fallback to if the gpu driver isn't installed. As you are mentioning arm and also Wayland, what is your gpu and are you using x11 or Wayland for the display system?

X11, 10 days ago fyne is working.

This system is based on Android termux proot container， seem like docker.

[andydotxyz]

Are you certain it is still X11? It is possible the system upgrade changed things...
Can you run something like Xeyes to test?

[ddkwork]

Are you certain it is still X11? It is possible the system upgrade changed things...
Can you run something like Xeyes to test?

Xeyes ？ how to do？

[ddkwork]

Are you certain it is still X11? It is possible the system upgrade changed things...
Can you run something like Xeyes to test?

Xeyes ？ how to do？

not found

[ddkwork]

Are you certain it is still X11? It is possible the system upgrade changed things...
Can you run something like Xeyes to test?

Xeyes ？ how to do？

yes， x11 still, used x11 vnc connet it.

[andydotxyz]

Are you certain it is still X11? It is possible the system upgrade changed things...
Can you run something like Xeyes to test?

Xeyes ？ how to do？

Sorry, we are not able to help you work with your package manager - no idea how termux searches and installs software.

[andydotxyz]

I would recommend:

• remove all Go cache
• update system packages
• reboot
• compile again

According to some other internet posts this has helped other apps - as there seems to be a mismatch between your X, the memory manager, and the app binary...

[ddkwork]

I would recommend:

• remove all Go cache
• update system packages
• reboot
• compile again

According to some other internet posts this has helped other apps - as there seems to be a mismatch between your X, the memory manager, and the app binary...

Ok, wait me.

[ddkwork]

It is not clear what command you issues to fix this and/or why it worked - the OpenGL information you posted seems to be consistent.

mesa 22.2.3 update to 22.3.1
compare two picture

all in one steps is update all x11 about，i am sure that problem is .o file version number check.

The error info serial number 209 and need 210，i don't how to get this value from glfw，but i believe it will be return from .o file，so we need add version check.

[ddkwork]

It is not clear what command you issues to fix this and/or why it worked - the OpenGL information you posted seems to be consistent.

so，if we add version check in this command will be better.

sudo pacman -S go xorg-server-devel libxcursor libxrandr libxinerama libxi

[andydotxyz]

If no version numbers were specified I wonder why your system did not have the latest versions installed?
If the issue was "upgrade to latest packages" then I don't think there is an issue here

[ddkwork]

If no version numbers were specified I wonder why your system did not have the latest versions installed?
If the issue was "upgrade to latest packages" then I don't think there is an issue here

I'm a little confused. Is there really such a big gap between Chinese and English? If I can solve this problem by updating the version when I publish the discussion, will I still discuss it here? Mesa just released it a few days ago, and I can only provide the solution here according to the process I handled. As for whether you will fix this kind of problem, it's up to you.

[andydotxyz]

It sounds like you solved it by upgrading.
So I don't know what we can do to fix it...
Our documentation does not specify install versions, so they should always be latest.
What else can we specify?

[Bluebugs]

I would like to point out that all the output returned by glxinfo indicate a software renderer and not a GPU based one. This might create some problem.