-
Notifications
You must be signed in to change notification settings - Fork 17
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
xkb config makes waynergy crash with: wl_display@1 no memory #71
Comments
Further info: Logs are unchanged from previous post.
|
Sorry for the lack of an initial response (this seemed to slip through the email cracks as it were) I'll definitely be having a go at reproducing this. The error is ultimately coming from the compositor side so I'll need to trace it in sway itself, though dumping core after registering the error indicates a clear failure on the waynergy side as well. |
Looking at sway's debug logging, this is due to xkbcommon 1.5's restrictions on user configuration for even slightly-privileged processes. swaywm/sway#7326 fixes this. |
Previously, calling Exit or ExitOrRestart to deal with a fatal Wayland error would attempt to call the cleanup() function... which would then try to close the Wayland connection gracefully, which would then trigger another fatal error and crash waynergy in the process. By defining a new status enum we can indicate when an error originates as a fatal wayland error and avoid this. Fixes our half of #71.
c4c0d94 resolves the core dumping bit, at the very least. As a workaround until the sway commit ends up in release, compile the keymap fully using xkbcomp (which can be told to respect includes); from within
|
Hello !
I've had an issue since this morning. No clue what it means, I tried to document all I could find.
Logs:
The text was updated successfully, but these errors were encountered: