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

--screenshot flag still broken #11

Closed
NotAShelf opened this issue Sep 5, 2022 · 17 comments
Closed

--screenshot flag still broken #11

NotAShelf opened this issue Sep 5, 2022 · 17 comments

Comments

@NotAShelf
Copy link

I have recently came across your comment on this issue in which you have announced it was fixed in version 1.6.10. However, I am experiencing this exact issue on a freshly built version of swaylock-effects-git (AUR) with package version r402.9ac172a-1

The issue is simply that 1/3 of the screen will be blank when --screenshot is passed and the screenshot will be fit inside the remaining 2/3, which is counterintuitive.

@NotAShelf
Copy link
Author

Output of swaylock -v as a followup:
swaylock version v1.6.10-1-g4b54b85 (Sep 5 2022, branch 'master')

@YHNdnzj
Copy link

YHNdnzj commented Sep 8, 2022

Running into this too on sway-git

@NotAShelf
Copy link
Author

@YHNdnzj could you confirm for me whether or not you're on a NVIDIA GPU?

I believe we have narrowed the issue down to my NVIDIA GPU or rather, the lack of proper screen capture support on it.

@YHNdnzj
Copy link

YHNdnzj commented Sep 9, 2022

@NotAShelf I'm using a laptop with NVIDIA Optimus, but manually specified WLR_DRM_DEVICES to make sway run on amdgpu.

But the whole screen is blank on my side, plus I can see and move the cursor when locked, maybe this is something else?

@NotAShelf
Copy link
Author

It could possibly be something else, yes. I am unable to reproduce the broken --screenshot behaviour on an AMD gpu.

@vfosterm
Copy link

vfosterm commented Oct 7, 2022

Seems to be an nvidia gpu issue I have the exact same issues on my side.

@xi-pinmping
Copy link

xi-pinmping commented Oct 8, 2022

Having this issue on an AMD Radeon HD 6320 as well

Edit: Was hoping the most recent wlroots-git update would fix it but it has not. It hasn't gone red screen and locked me out for a few days though. White screen on screenshot still persists

@Haze-sh
Copy link

Haze-sh commented Oct 21, 2022

I can reproduce this on a NIVIDIA GPU with wlroots-git AUR package. Sometimes it turns red screen and others white background but I can move the cursor though.

@Zeioth
Copy link

Zeioth commented Nov 27, 2022

Having the issue on AMD 6700XT too. Every other parameter apart from --screenshot seems to work fine. Tested with swaylock-effects-git.

EDIT: No idea why, but it works fine now.

@vfosterm
Copy link

For those using hyprland the hyprland-nvidia-git package on AUR resolves the issue for me.
https://aur.archlinux.org/cgit/aur.git/tree/nvidia.patch?h=hyprland-nvidia-git

@Martinits
Copy link

Martinits commented Jan 6, 2023

Have this issue on Intel i5-1260p, too. My screen is blank when locked, without screenshot. Using sway-effects-git (swaylock version v1.6.10-4-ga1cf657 (Jan 6 2023, branch 'master')) and sway(1.8) from archlinux. Get logs:

[ WARN:[email protected]] global /build/opencv/src/opencv-4.6.0/modules/videoio/src/cap_gstreamer.cpp (2401) handleMessage OpenCV | GStreamer warning: Embedded video playback halted; module source reported: Could not read from resource.
[ WARN:[email protected]] global /build/opencv/src/opencv-4.6.0/modules/videoio/src/cap_gstreamer.cpp (1356) open OpenCV | GStreamer warning: unable to start pipeline
[ WARN:[email protected]] global /build/opencv/src/opencv-4.6.0/modules/videoio/src/cap_gstreamer.cpp (862) isPipelinePlaying OpenCV | GStreamer warning: GStreamer: pipeline have not been created

update: FYI, sway 1.7-10 on archlinux has no problem. Sth wrong with sway 1.8.

@yannfill
Copy link

yannfill commented Jan 6, 2023

Same issue as @Martinits with Intel GPU on Arch and Sway 1.8. Worked in Sway 1.7.

Could it be related to this new feature?

More robust and secure screen lockers via the new ext-session-lock-v1 protocol (supported by swaylock)

@lucaslira95
Copy link

Same issue here too... (Sway 1.8, Swaylock Effects v1.6.10-4-ga1cf657)

@yannfill
Copy link

Seems fixed with latest commit/merge.

@lucaslira95
Copy link

After the last commit, the screen blink, then after one second the blur screen appears...

@Haze-sh
Copy link

Haze-sh commented Jan 13, 2023 via email

@jirutka
Copy link
Owner

jirutka commented Jan 19, 2023

Thanks for the confirmation!

@jirutka jirutka closed this as completed Jan 19, 2023
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

10 participants