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

Gtklock/hyprlock red screen issue #341

Closed
sioodmy opened this issue May 13, 2024 · 2 comments
Closed

Gtklock/hyprlock red screen issue #341

sioodmy opened this issue May 13, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@sioodmy
Copy link

sioodmy commented May 13, 2024

Every time I try to lock my session using gtklock or hyprlock the entire screen turns red.

I know it's most likely my misunderstanding, but I haven't found any information about lockers in docs.
Also I Couldn't find anything useful in niri logs.

niri: locking session
backend::tty: pausing session
backend::tty: device is inactive
backend::tty: device is inactive
backend::tty: device is inactive
backend::tty: device is inactive

Just to clarify, I can confirm my current gtklock setup used to work on wayland perfectly fine. same with hyprlock. Maybe it's because of some unimplemented protocol?

System Information

  • niri version:
    niri unstable 2024-05-12 (commit 55e5502)

thinkpad x1

@sioodmy sioodmy added the bug Something isn't working label May 13, 2024
@YaLTeR
Copy link
Owner

YaLTeR commented May 14, 2024

What seems to happen is that niri disconnects the client. Need to look into it; it may be that Smithay posts a protocol error when it shouldn't somewhere.

@YaLTeR
Copy link
Owner

YaLTeR commented May 17, 2024

Fixed with a Smithay update.

@YaLTeR YaLTeR closed this as completed May 17, 2024
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