Daniel Moerner:
> I've been using i3 in dom0 for about a month now, and I wanted to share a few 
> tips and tricks (partly so I can have them in a centralized place for 
> reference):
> 
> 1. To lock the screen on suspend and resume, you need to add a systemd target 
> in /etc/systemd/system. This has to use your username (or supposedly 
> xss-lock, which I haven't bothered figuring out how to use). I use the 
> following content, substituting for $USER:
> 
> [Unit]
> Description=Lock screen on suspend
> 
> [Service]
> User=$USER
> Type=forking
> Environment=DISPLAY=:0
> ExecStart=/usr/bin/i3lock -d -c 000000
> 
> [Install]
> WantedBy=suspend.target
> 
> 2. Volume keys: Install pulseaudio-utils. Then put the following in 
> .i3/config:
> 
> bindsym XF86AudioRaiseVolume exec --no-startup-id pactl set-sink-volume 1 +5%
> bindsym XF86AudioLowerVolume exec --no-startup-id pactl set-sink-volume 1 -5%
> bindsym XF86AudioMute exec --no-startup-id pactl set-sink-mute 1 toggle
> 
> I then customize the qubes-i3status command by adding: (I know this awk/sed 
> mixture is awful, and it's hard-coded for my system, which has two pulseaudio 
> sinks)
> 
> status_volume() {
>    local muted=$(pactl list sinks | awk -F ' ' '/Mute/ {print $2}' | sed -s 
> 's/ //g' -e '2q;d')
>    if [[ $muted == 'yes' ]]; then
>        json volume "Volume: 0%"
>    else
>        local volume=$(pactl list sinks | awk -F ' ' '/Volume/ {print $2}' | 
> sed -s 's/ //g' -e '3q;d')
>        json volume "Volume: $volume"
>    fi
> }
> 
> And then add a local volume variable to the main() call. I update every 
> second.
> 
> 3. A few minor tweaks to the config file: See this pull request, which has 
> already been merged: https://github.com/QubesOS/qubes-desktop-linux-i3/pull/5 
> 
> A few more personal thoughts: Personally, I change the navigation to use vim 
> keys, and then remap horizontal split to 'b'. I also remap 'focus child' to 
> 'c', since I find it to be a useful shortcut. Originally I disabled 
> fullscreen, on the model of Xfce4, but I had to reenable it as part of a 
> workaround for https://github.com/QubesOS/qubes-issues/issues/1502
> 
> I'm sure I'm missing a few things, but I wanted to share this, since I 
> sometimes see people asking about i3, especially on IRC.
> 
> Best,
> Daniel 
> 

Thanks for this. I've used i3 on other OSes and I like it a lot. I
probably won't use it on Qubes however because of an issue that I'll
note here since it may or may not affect other users.

In i3 it is rather difficult to control the size of a window with fine
granularity, and in particular it is very difficult to restore the exact
size a window would have been created with. This is a problem for users
of Tor Browser, because websites and exit nodes can query the browser
window's size even when you have JavaScript disabled. This makes you an
easy fingerprinting target.

If anyone knows of any workarounds for this, perhaps forcing certain
kinds of windows to be created in floating mode and keep their original
size, please share them.

-------------------------------------------------

ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the 
NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!  
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!  

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/bab51d99-56d2-af1e-96bd-0483eebd2653%40vfemail.net.
For more options, visit https://groups.google.com/d/optout.

Reply via email to