-
Notifications
You must be signed in to change notification settings - Fork 46
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
Merge upstream #86
base: master
Are you sure you want to change the base?
Merge upstream #86
Conversation
mako does something similar.
Initializing to 1 is incorrect when the surface scale is > 1.
We incorrectly used the buffer size instead of the surface size. Let's not bother and just damage the maximum region.
Signed-off-by: Elyes HAOUAS <ehaouas@noos.fr>
An odd value of fe.height lead to the indicator disappearing. This was due to the buffer size no longer being a multiple of the buffer scale. This commit fixes the issue by checking both height and width to be a multiple of scale. This is done early to avoid excessive re-calls of create_buffer if the buffer_height != new_height in render.c line 314 (now 318).
The next commit will need that version. Adjust the build to not trigger deprecation warnings.
This allows building swaylock with a local wayland-protocols.
This is a new protocol to lock the session [1]. It should be more reliable than layer-shell + input-inhibitor. [1]: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/131
More consistent with our code style.
Mostly irrelevant today.
We don't actually require xdg-shell support.
I think it needs some work to support ext-session-lock-v1. Did you test the PR? On my try, the lock crashes and only session lock remains. |
I did test it and for me it worked but as far as I remember with river not sway, might very well be that I missed something. Edit: still works for me with sway, debug output:
Edit2: I think the screenshot plugin is broken though since the effects are applied after the lock was acquired. The order would have to be switched here to make it work again. |
@David96 did you run on latest sway master?
I tried to merge upstream yesterday but I got the error like ext_session_lock_surface not configured. I think currently swaylock-effects only uses xdg_output's surface, not ext_session_lock's surface |
Yeah the issue seems to be the fade-in plugin, when removing that from the command line everything works for me. I guess setting alpha on a lock surface doesn't make any sense since the protocol makes sure that as soon as the lock is acquired the compositor doesn't composite anything else. |
Ok, the fade thing was an actual merge mistake that should be fixed now. Still the fade in won't work properly due to the nature of the sessionlock protocol but at least it shouldn't crash anymore. |
The main change is the added support for ext-session-lock-v1 I think.