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

Effects relying on laptop hardware crash #162

Open
4JX opened this issue Jun 29, 2024 · 5 comments
Open

Effects relying on laptop hardware crash #162

4JX opened this issue Jun 29, 2024 · 5 comments

Comments

@4JX
Copy link
Owner

4JX commented Jun 29, 2024

Having the same issue here on Hyprland, on the Legion 5 Pro 16ARX8. Can't open gui with the same error, but also (this might be related) trying to set the AmbientLight, Fade or Ripple effect from the terminal also crashes, and just sets the keyboard rgb to off.
RUST_BACKTRACE=full doas legion-kb-rgb set --effect Fade

doas (rabaimor@legion) password: 
Authorization required, but no authorization protocol specified

The application panicked (crashed).
Message:  Could not connect to a X display
Location: /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/device_query-1.1.3/src/device_state/linux/mod.rs:38

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
The application panicked (crashed).
Message:  called `Result::unwrap()` on an `Err` value: Any { .. }
Location: app/src/effects/mod.rs:151

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

Originally posted by @rabaimorp in #152 (comment)

@4JX
Copy link
Owner Author

4JX commented Jun 29, 2024

CC @rabaimorp, is it only those three?

Fade/Ripple need to access to keyboard input events which I just haven't found a way to gracefully handle yet on wayland. There's a library I previously tested but didn't quite like.

Should at least hide those for wayland users in the meantime though. Although for me it doesn't outright crash on GNOME, but rather just stops responding to input events if I don't focus the app.

Hyprland
Could not connect to a X display

Are you maybe running the program through XWayland? It may be having some trouble there.

@4JX
Copy link
Owner Author

4JX commented Aug 29, 2024

Closing due to lack of responses from OP

@4JX 4JX closed this as not planned Won't fix, can't repro, duplicate, stale Aug 29, 2024
@rabaimorp
Copy link

Closing due to lack of responses from OP

Sorry, haven't got notified the first time. I tried it on x11 as well, same issue. I'll try to replicate it in any enviroment you want, to see if it could work

@4JX 4JX reopened this Sep 2, 2024
@4JX
Copy link
Owner Author

4JX commented Sep 2, 2024

Sorry, haven't got notified the first time

Weird, I assumed the pings would reach you.

I tried it on x11 as well, same issue

Still crashes with that same error on X11? What DE/WM? Can you provide logs for both with RUST_BACKTRACE=full?

@rabaimorp
Copy link

Sorry, haven't got notified the first time

Weird, I assumed the pings would reach you.

I tried it on x11 as well, same issue

Still crashes with that same error on X11? What DE/WM? Can you provide logs for both with RUST_BACKTRACE=full?

Yes, the same error. I used x11 on kde plasma.

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

No branches or pull requests

2 participants