Skip to content
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

Ludusavi crashes immediately on startup #297

Closed
kekonn opened this issue Dec 20, 2023 · 2 comments
Closed

Ludusavi crashes immediately on startup #297

kekonn opened this issue Dec 20, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@kekonn
Copy link
Contributor

kekonn commented Dec 20, 2023

Ludusavi version

v0.21.0

Operating system

Linux

Installation method

Other

Description

After the latest update, when I open ludusavi, it crashes immediately after it shows the window. Logs attached. Ludusavi installed from the AUR.

Logs

interface 'wl_surface' has no event 2
warning: queue 0x7f3e14000ca0 destroyed while proxies still attached:
zwp_primary_selection_device_v1@51 still attached
zwp_primary_selection_device_manager_v1@47 still attached
wl_data_device@50 still attached
wl_seat@44 still attached
wl_data_device_manager@36 still attached
wl_registry@46 still attached
warning: queue 0x55ca19455dc0 destroyed while proxies still attached:
xdg_wm_base@23 still attached
wl_output@15 still attached
wp_fractional_scale_manager_v1@14 still attached
xdg_activation_v1@13 still attached
zwp_text_input_manager_v3@12 still attached
zwp_relative_pointer_manager_v1@11 still attached
zwp_pointer_constraints_v1@10 still attached
zxdg_decoration_manager_v1@9 still attached
wl_seat@8 still attached
wp_viewporter@7 still attached
wl_subcompositor@6 still attached
wl_compositor@5 still attached
wl_shm@4 still attached
wl_registry@2 still attached

@kekonn kekonn added the bug Something isn't working label Dec 20, 2023
@mtkennerly
Copy link
Owner

Hi! This will be fixed in the next release. It was also reported here: #294

In the meantime, you can work around it by setting WINIT_UNIX_BACKEND=x11 in your environment variables.

@kekonn
Copy link
Contributor Author

kekonn commented Dec 20, 2023

Yup, the env var fixed it!

@kekonn kekonn closed this as completed Dec 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants