-
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
i3blocks (i3bar) shows when using bar mode hidden in i3 #173
Comments
Hi! Thanks for reporting the issue. However I cannot reproduce it using your configuration and latest |
That's odd, i do not know how to get the same detailed version str, but running |
Can confirm, but the problem only persists if a compositor is running(in my case compton).
Edit: I just noticed that notifications are also not hidden when compton is active. (Notification daemon: dunst) |
I have the same issue, also just when running compton:
|
I also had a floating window pop up, while it was locked. That was shown, too. |
This issue is tracked in #204 |
Related issues are ongoing and I tried some solutions like using I did not leave a message on the ongoing issues because I'm using forks but I wanted to leave my solution here for this specific usage. ContextI use i3wm with i3status-rust (i3bar), picom (compton fork) and betterlockscreen based on i3lock-color (i3lock fork).
SolutionMy solution is to use a script to run the lock, check the i3bar mode in the script and toggle it before/after the lock: # check if the i3bar is currently visible
i3bar_mode=$(i3-msg -t get_tree | jaq '.. | objects | select(.class | contains("i3bar"))')
# if i3bar is hidden makes it visible
if [[ -z "$i3bar_mode" ]]; then
i3-msg -q bar mode toggle
fi
... run i3lock or any alternative here...
# hide i3bar when leaving lock
if [[ -z "$i3bar_mode" ]]; then
i3-msg -q bar mode toggle
fi |
I use |
The bar is showing when locked and mod4 is pressed(which is set to display the bar).
spesific config
bar { mode hide hidden_state hide modifier $mod }
Where $mod is Mod4.This is probably not a huge problem, but thought i'd mention it.
Regards
The text was updated successfully, but these errors were encountered: