-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
sigsegv on wayland compiled executable #3517
Comments
The library version stated does not match the stack trace... maybe just a typo, but I wanted to check. |
Yes, you are right, i updated the env and tried again:
|
I cannot replicate. |
@Jacalz you marked this as verified - can you replicate? |
Hmm. Actually not. Sorry about that. Don’t know why I removed unverified |
Can you replicate on Wayland desktop? I'm not sure if I can follow your steps without a Librem device... |
i have no running wayland on my desktop but will try to create an installation on the weekend. @andydotxyz : if you tell me how to get that environment information i can easily send it or i could run special fyne versions or programs to debug if you could tell me what and how. |
Oh I think I just realised - this is not Android like the original report, but PureOS then? I'm not sure why yet but it seems to be a crash inside the GLFW C code in https://github.com/glfw/glfw/blob/41d8da1cea55732867b5c3a7159215071b87b790/src/wl_window.c#L2342 (_glfwCreateStandardCursorWayland). Perhaps the wayland implementation on PureOS/Librem5 does not support cursors fully? I wonder if we can test PureOS without a Librem? |
i am not sure about wayland but PureOS running on a desktop wont have the same composer, right? on the librem its phosh i assume? does |
today i set up a pure wayland box to test the issue. this is strange:
and the program runs but doesnt show a window (i use sway as the compositor)
which looks like its trying X11 (which isnt there, DISPLAY is not set) the compile with only the wayland tag set shows some warning which the compile with both flags doesnt:
|
The first Wayland PlatformErrors are expected because our support isn't complete, I think. Those glfw warnings are also more or less expected, see go-gl/glfw#359. No window is strange though. |
|
I think I might have encountered a similar issue a while ago running Go/GLFW/Wayland apps on embedded systems. I found this resolved my issue - https://github.com/glfw/glfw/pull/2361/files Are you able to confirm if making that change fixes things for you? |
The segfault only occurs on keyboard input, so i doubt. |
Sorry, I was referring to the original segv:
and the comment mentioned in #3517 (comment). It probably doesn't apply to the issue in |
For me, compling gnoll with
|
Like mentioned further up the thread, those compiler warnings are not a problem and tracked in go-gl/glfw#359 already. |
Can anyone still see this with latest develop? |
I have Supersonic users who are building with |
I'm not sure that we can or should keep this open based on others experiencing a SEGV. |
I agree. Let's close this for now and open a new one if it pops up again. |
Checklist
Describe the bug
when compiling for wayland (
go build -tags wayland .
) the executable coredumps on start while the X11 variant works fine.How to reproduce
-tag wayland
Screenshots
No response
Example code
Fyne version
v2.3.0
Go compiler version
10.2.1
Operating system
Android
Operating system version
buster/sid
Additional Information
this is on a Librem5
The text was updated successfully, but these errors were encountered: