Sys-gui Customization: Minimal Fedora and Alternate Desktop Environments / Window Managers (DE/WMs)

Original forum link
https://forum.qubes-os.org/t/27093
Original poster
XMachina
Editors
fsflover, gonzalo-bulnes, XMachina
Created at
2024-06-18 05:32:37
Last wiki edit
2025-02-17 22:32:18
Revisions
15 revisions
Posts count
4
Likes count
1
Tags
configuration, customization, sys-gui, ux

Guide:

  1. Start with latest Fedora template (works with Fedora, Fedora Minimal, and Fedora XFCE). In sys-gui template, install necessary packages and shutdown template:

  2. GUIVM packages: gui-templ# dnf install qubes-manager qubes-linux-desktop-manager qubes-vm-guivm dummy-psu-module dummy-psu-receiver dummy-backlight-vm

  3. Create sys-gui with the template you just created, and these modifications:

  4. no NetVM
  5. autostart on boot
  6. allow fullscreen

  7. and the services:

  8. In dom0, further modify sys-gui from command line: dom0$ qvm-prefs sys-gui guivm dom0 dom0$ qvm-prefs sys-gui audiovm dom0 dom0$ qvm-features sys-gui gui-secure-copy-sequence none dom0$ qvm-features sys-gui gui-secure-paste-sequence none

  9. In sys-gui, open a Xen console, login as user. In sys-gui terminal set XSESSION variable and create ~/.xinitrc. Replace <your de/wm> with the command to launch your DE/WM. sys-gui$ echo "exec <your de/wm>" | tee ~/.xinitrc 1> /dev/null sys-gui$ XSESSION=<your de/wm>

  10. In dom0 terminal, execute: dom0$ qubes-prefs default_guivm sys-gui

  11. Restart QubesOS and select GUIVM session in display manager menu.

Important Notes and Current Issues:

Summary:

Anyone using this guide should be mindful that there may be small tweaks needed, and that this guide isn't a guide on how to get your favorite window manager to work. This will get your packages installed and minimally working, but configuration, bells, and whistles aren't covered. You should be able to get anything you want working just how you would if you were running this in a regular Fedora workstation, with the caveat that you are in an unprivileged virtual environment. Certain things, like accessing hardware directly, will not work, but qrexec policy can be used as a workaround.

As of this moment, there are still minor problems that persist: - sys-gui is labeled as dom0 in the window manager, - there is a several seconds' wait with a black screen while the window manager loads, and - notifications for sys-gui are sent to dom0 (this is an upstream problem that cannot be fixed with just configuration).

I plan to expand this to be OS independent, but right now Debian is posing some problems that I need to diagnose. It will be more of a priority for me if this gets likes and constructive replies; however, my schedule is unpredictable and I may have to shelf this if things come up.