Tiling Window Managers

Which tiling window managers are best supported by Qubes? I’ve tried both i3 (https://www.qubes-os.org/doc/i3/) and awesome (https://www.qubes-os.org/doc/awesome/), but some features are missing when you log in to them. For example, neither seem to allow disposable VMs.

I can confirm that i3 allows disposable VMs. How are you launching
things? For me, dmenu has an entry fedora-dvm: Firefox for example,
which will launch a new disposable VM running Firefox.

Thank you! I didn’t realize dvm means “disposable virtual machine” until now. I still can’t find how to do it in awesome. When I click on Application Launcher in awesome, it lists all of the VMs, but doesn’t offer the disposable VMs.

Another problem I’ve run into with awesome is when trying multi monitor, it gives the following error on the laptop monitor, but not the external monitor:

XFCE PolicyKit Agent

GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exists for the given subject.

any qubes specific configs to share? I am looking into swapping to WM asap. but I am unsure how to configure properly.

I have not used i3 or awesome before, spectrwm took care of me :slight_smile:

The only Qubes specific config I use comes from i3-settings-qubes and
the following line:

exec --no-startup-id qubes-i3-xdg-autostart

which is supposed to handle checking on transient VMs.

Other than that, it’s just a bunch of custom keybinds.

1 Like

DWM is broken ATM

I guess you mean from the menu.

Actually for awesome that menu can be customised as you wish and this way include disposable VM starting, see [1].

Personally I use awesome, but haven’t bothered opening the menu for ages. I use [2] (Mod-R and type) for everything and I guess most awesome users have something similar as one of the points of using awesome is to avoid clicking.

[1] https://www.qubes-os.org/doc/awesome/
[2] https://github.com/3hhh/qubes-terminal-hotkeys

Thanks for the responses everyone.

Do tiling window managers cause fingerprinting with the Tor Browser? Tor Browser uses a default window size that ideally users don’t touch, so they all report the same window size. If you resize the window, it adds letterboxing so the screen size you report is a multiple of 200px by 100px. If tiling window managers change the Tor Browser window so that it reports something other than the default size, how can we stop that?

Also, another thing I’ve noticed with i3 on Qubes. The audio icon disappears, so there’s no way to change the volume with the mouse.

For Qubes i3 (deafult) it mitigates that: