-
-
Notifications
You must be signed in to change notification settings - Fork 410
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
Problem with starting eww under musl #253
Comments
Just to be exactly clear: the log command is still running alongside the open command, and no further output appeared? Is eww still running? Does |
Are you using X or Wayland? Seems like daemon does not start. I'd guess that it stucks at line number 57. Lines 41 to 60 in 9c12a31
Which distro you are using, does it have gtk? |
Yes, eww logs is still running in a separate shell. I am using Wayland in Void Linux with gtk installed. Unfortunately, I have no debugging experience in Rust. |
Read the eww documentation on Wayland specifically |
I can confirm this happens to me in voidlinux with similar output
|
I forgot to mention, this only happens in musl. Works fine with glibc in void. |
Hmmmmmmm, I'm not all that familiar with the differences between glibc and musl in these contexts, but that's definitely weird. Any more hints at what could cause this would be appreciated, these types of edge-cases are somewhat outside of my area of expertise ^^ |
I'm able to use eww on musl (and freebsd libc), requires compiling gtk3 from source, some musl distros are shipping "shared packages" instead of rebuilding them. I'm using Carbs but even on Void with musl it was working fine for me. |
No need anyways, you just need to specify the target for |
Same issue here, running Void Linux with X, the /run/user/1000/eww-server_... file gets deleted after |
It runs fine for me tho. |
Can confirm that. So building gtk3 from source works ? as @heavyrain266 said ? i will give it a try |
So i built gtk3 referring the PKGBUILD from AUR on void musl , eww still doesnt create the socket , or it gets deleted right after |
GTK3 doesn't matter, you need to build eww from source with |
And thats exactly what i did. How else would the binary even run for me to report EDIT1 : Perhaps thats not exactly what i did |
So does this just work? Or is there still anyone having issues when specifying the target explicitly |
It works for me, but not sure about others. |
Does not work for me...
|
Same segfault with kisslinux (musl too) |
just like in #362 , you need |
Nope, the issue has not been magically resolved... Even with new YUCK configuration language.
And then I then:
With following contents of
${XDG_CONFIG_DIR}/eww/eww.yuck
:Originally posted by @mitinarseny in #203 (comment)
The text was updated successfully, but these errors were encountered: