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

i3bar is shown in i3lock lock screen when it is positioned at the bottom with picom running #347

Closed
denppa opened this issue Aug 14, 2023 · 3 comments

Comments

@denppa
Copy link

denppa commented Aug 14, 2023

I'm submitting a…

[x ] Bug
[ ] Feature Request
[ ] Other (Please describe in detail)

Current Behavior

i3's default bar i3bar is shown on top of the i3lock lock screen when it is positioned at the bottom with picom running.

Expected Behavior

The i3lock lock screen / color should hide everything on the desktop.

Reproduction Instructions

Buggy config:

bar {
        status_command i3status
        position bottom
}

Replace bottom with top and it is hidden in the lock screen.

Environment

Output of i3lock --version:

i3lock: version 2.14.1 © 2010 Michael Stapelberg

Debian Bookworm, i3wm v 4.22

@stapelberg
Copy link
Member

Typically, i3lock raises its lock screen window above any other X11 window that obscures the lock screen (such as i3bar).

However, i3lock cannot raise its windows above a compositor.

The only known solution is to stop the compositor before running i3lock, then restarting the compositor afterwards: #333 (comment)

@denppa
Copy link
Author

denppa commented Aug 20, 2023

Thanks @stapelberg . I thought of this as well, though I feel like this constant restarting will drain the battery a lot quicker on laptops.

@denppa denppa closed this as completed Aug 20, 2023
@stapelberg
Copy link
Member

though I feel like this constant restarting will drain the battery a lot quicker on laptops.

I doubt it will be noticeable. Starting a compositor is not a heavy operation.

@orestisfl orestisfl closed this as not planned Won't fix, can't repro, duplicate, stale Sep 4, 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

3 participants