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

Desktop Linux Crash #7

Closed
nametable opened this issue Jan 10, 2024 · 3 comments
Closed

Desktop Linux Crash #7

nametable opened this issue Jan 10, 2024 · 3 comments

Comments

@nametable
Copy link

When I compile and run cuprous on my desktop, I am seeing a crash

$ cargo run
interface 'wl_surface' has no event 2
warning: queue 0x7f3cd4000ca0 destroyed while proxies still attached:
  zwp_primary_selection_offer_v1@4278190082 still attached
  zwp_primary_selection_offer_v1@4278190081 still attached
  wl_data_offer@4278190080 still attached
  zwp_primary_selection_device_v1@42 still attached
  zwp_primary_selection_device_manager_v1@25 still attached
  wl_data_device@41 still attached
  wl_seat@40 still attached
  wl_data_device_manager@39 still attached
  wl_registry@37 still attached
warning: queue 0x562751da6f80 destroyed while proxies still attached:
  xdg_wm_base@30 still attached
  wl_output@17 still attached
  wl_output@16 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

I'm on Arch Linux running Hyprland, with AMD Radeon graphics. I'm gonna try to investigate further to see if I can figure out the problem. I have the same error when I run the prebuilt binary.

@nametable
Copy link
Author

I don't understand the real issue yet, but after running cargo update, I can cargo run and it starts fine. Must be an bug fixed in one of the dependencies.

@Ved-s
Copy link
Owner

Ved-s commented Jan 10, 2024

I updated eframe to 0.25.0, it resulted in smithay-client-toolkit being v0.18.0, which should solve the issue

@nametable
Copy link
Author

Yup, upgrading eframe fixes the issue also

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants