-
Notifications
You must be signed in to change notification settings - Fork 403
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
Half height of the external display (left rotated) remains unlocked. #44
Comments
What’s the output of |
Are you running a compositor? Does not running it fix it? |
With latest I mean i3lock 2.7:
Where
No compositor is running but I will check with it as soon as I get the opportunity. |
Please run Then, compress |
(If xtrace prints “Error parsing xauth list data”, add the |
The xtrace log is available here: https://www.dropbox.com/s/2bw2gv5901gguyt/xtrace.log.bz2?dl=0 |
From the logfile, i3lock creates a 3120x1920 window:
From the xrandr output you provided, that matches up the X server’s root window size:
Hence, I think i3lock is behaving correctly here. I’m not sure why you are running into the problem you’ve described. Could you boot from a live linux distribution and run i3lock there to make sure it’s not something in your setup? |
Closing due to inactivity. |
The issue affects the latest release of i3lock and has not been tested on previous releases.
I use i3 and i3lock on xubuntu 14.04 (Trusty Tahr) with 2 displays:
If the external display is rotated 90° to left, i3lock does not draw its overlay in a good way on it. In particular, the overlay is perfectly drawn on the laptop display but it only covers 50% of the height of the external display.
Since only half of the external display is "locked", i3lock does not completely secure the underlying tiles/windows.
However, as soon as a key is pressed and the password validation routine starts working, the new overlay containing the login animation finally occupies the entire screen.
To have an unsecure lockscreen again it is enough to login with the correct password and then lock the screen again.
The text was updated successfully, but these errors were encountered: