-
-
Notifications
You must be signed in to change notification settings - Fork 167
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
XWayland coredumps on FreeBSD 14.1-RELEASE #722
Comments
Uhhhhhh? No idea honestly |
This looks like what is going on here, but instead of the compositor crashing its just Xwayland: hyprwm/Hyprland#6408 this also seems related: https://reviews.freebsd.org/D26642 |
Trying to nest sway in niri causes this to happen, too: |
After testing out a ton of stuff, apparently nesting niri on.. niri... makes it work! - its just the tty backend that doesnt like Xwayland for some reason |
Does this still happen? |
Feel free to reopen with more info if you think this is a niri issue. |
Hello! Sorry for not answering earlier, I completely forgot about it. This is most likely an upstream issue. I tried manually updating |
I am just testing FreeBSD 14.2 and this is still happening with Xwayland as well as e.g. cage when invoked from niri. This is very probably due to dev_t in libc crate having different definitions depending on which FreeBSD version it targets (see pop-os/cosmic-comp#1028 and referenced smithay fix at https://github.com/Smithay/client-toolkit/blob/25079ae75cb6952b0542aa343bd5a52c81d135d4/src/dmabuf.rs#L15-L19), I think this could also be worked around in niri freebsd port |
For some reason Xwayland just coredumps on a failed assertion when running niri on FreeBSD 14.1 with drm-515-kmod, absolutely no idea what causes it tho. Doesnt seem to happen on Sway
System Information
Distro: FreeBSD 14.1-RELEASE-p5 with PkgBase
APU: AMD Ryzen 3 2200g with Vega 8 integrated graphics
The text was updated successfully, but these errors were encountered: