Go back to topic: Sys-gui Customization: Minimal Fedora and Alternate Desktop Environments / Window Managers (DE/WMs)
| # This Guide Now Works for AwesomeWM AND i3WM + fedora-40-minimal | |
| 1. Start | 1. Start with latest Fedora template (works with Fedora, Fedora Minimal, and Fedora XFCE). In sys-gui template, install necessary packages and shutdown template: - GUIVM packages: `gui-templ# dnf install qubes-manager qubes-linux-desktop-manager qubes-vm-guivm dummy-psu-module dummy-psu-receiver dummy-backlight-vm` - AwesomeWM: `gui-templ# dnf install awesome` - i3WM: `gui-templ# dnf install i3wm i3-settings-qubes` - KDE: `gui-templ# dnf install @kde-desktop-qubes` - Any other Desktop Environment or Window Manager should work. 2. Create `sys-gui` with the template you just created, and these modifications: - no NetVM - autostart on boot - allow fullscreen - and the services: - `guivm` - `gui-vm-agent` - `dummy-psu` - `dummy-backlight` 3. 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` 4. 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>` |
| # Notes and Current Issues | # Important Notes and Current Issues: |
| 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. |
| # This Guide Now Works for AwesomeWM AND i3WM + fedora-40-minimal # Guide: | |
| 6. Restart QubesOS and select GUIVM session in display manager menu. # Notes and Current Issues | |
| 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. [/details] |
| # | # This Guide Now Works for AwesomeWM AND i3WM + fedora-40-minimal ## TL;DR: 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). |
| [details="This guide is here currently for anyone who would like to join me in doing the work. The Guide will be updated when I have actionable information. I'm doing my best to keep clutter out of the guide. It will likely go through several iterations, but it will be turned into a working guide when I am finished. "]
| [details="This guide is here currently for anyone who would like to join me in doing the work. The Guide will be updated when I have actionable information. I'm doing my best to keep clutter out of the guide. It will likely go through several iterations, but it will be turned into a working guide when I am finished. "] |
| Updates will be removed when the guide is finalized. There will also likely be a visual overhaul. | Updates will be removed when the guide is finalized. There will also likely be a visual overhaul. |
| # TL;DR: | # !! This Guide Now Works for AwesomeWM + fedora-40-minimal ## TL;DR: |
| # Caveat lector (Work In Progress): | ## Caveat lector (Work In Progress): |
| This is currently a WIP and will be updated as I figure it out. | This is currently a WIP and will be updated as I figure it out. My goal is to make this work with as few and as simple changes as possible so as to be easy to configure and maintain, so work may be slow as I pinpoint exact issues. As of this moment, sys-gui terminal (and most likely all applications) are labeled as dom0 in the wm, it is too slow for comfort when logging in and starting the wm, and notifications for sys-gui are sent to dom0 (such as policy notifications; this is an upstream problem that I cannot fix with just configuration). However, it is definitely working and workable with AwesomeWM in Fedora 40 Minimal! I plan to expand this to be OS and DE/WM independent, but I'm working to that eventually. Debian is posing some problems that I don't yet understand. Lastly, I am very busy and may not post regular updates. My schedule is unpredictable and I may get this done quickly or I may be very slow. I will do what I can when I can, and I will update when significant progress (or failure) is made. Any help is appreciated! |
| [details="**Working Guide:** AwesomeWM on Fedora Minimal Template:"] 1. Start completely fresh with new sys-gui and clean fedora-40-minimal template. (Delete old and reinstall with salt formula.) 2. In sys-gui template ("`fedora-40-minimal`" if unmodified), install necessary packages and shutdown template: - GUIVM packages: `gui-templ# dnf install qubes-manager qubes-linux-desktop-manager qubes-vm-guivm lightdm-gtk dummy-psu-receiver dummy-psu-module dummy-vm-backlight` - AwesomeWM: `gui-templ# dnf install awesome` 3. Switch sys-gui template to the one just created and start sys-gui. 3. In sys-gui, open a Xen console, login as `user`. In sys-gui terminal execute: `sys-gui$ echo "exec awesome" | tee ~/.xinitrc 1> /dev/null` `sys-gui$ XSESSION=awesome` `sys-gui$ mkdir ~/.config/awesome/ && sudo cp /etc/xdg/awesome/rc.lua .config/awesome/` (The above command is unnecessary, but it moves the Awesome config to user dir to avoid errors from editing it should you do so. I personally consider it a part of correctly configuring Awesome, but it will run fine without.) 5. In dom0 terminal, execute: `dom0$ qubes-prefs default_guivm sys-gui` 6. Restart QubesOS and select GUIVM session in display manager menu. [/details] [details=" Work in progress: AwesomeWM/Debian Minimal:"] | |
| [/details] [details="**Working Guide:** AwesomeWM on Fedora XFCE Template:"] 1. Start completely fresh with new sys-gui and clean fedora-39-xfce template. (Delete old and reinstall with salt formula.) 2. In sys-gui template (fedora-39-xfce if unmodified), install awesome package. Copy `/usr/share/awesome/lib/qubes.lua` to this template from dom0 and move to same place in template as it was in dom0. Shutdown template. 3. In sys-gui, open a Xen console, login as `user`. Alternatively login to GUI session and open a terminal. This will confirm that there are no problems so far. 4. In sys-gui terminal execute: `sys-gui$ echo "exec awesome" | tee ~/.xinitrc 1> /dev/null` `sys-gui$ XSESSION=awesome` `sys-gui$ mkdir ~/.config/awesome/ && sudo cp /etc/xdg/awesome/rc.lua .config/awesome/` (The above command is unnecessary, but it moves the Awesome config to user dir to avoid errors from editing it should you do so. I personally consider it a part of correctly configuring Awesome, but it will run fine without.) 5. In dom0 terminal, execute: `dom0$ qubes-prefs default_guivm sys-gui` `dom0$ | |
| # | # The current roadmap: |
| 1. [Done] Get everything functioning correctly in fedora-40-xfce based sys-gui. This will mostly be a Qubes thing, since that should already function perfectly.
2. [Done] Get AwesomeWM functioning perfectly in fedora-40-xfce based sys-gui. I don't anticipate problems.
3. [ | 1. [Done!] Get everything functioning correctly in fedora-40-xfce based sys-gui. This will mostly be a Qubes thing, since that should already function perfectly. 2. [Done!] Get AwesomeWM functioning perfectly in fedora-40-xfce based sys-gui. I don't anticipate problems. 3. [Done!] Get AwesomeWM working in fedora-40-minimal based sys-gui. This will just be a matter of figuring out which packages are necessary and which aren't. 4. [In-progress] Get i3wm working in sys-gui. |
| Steps one through three are done! |
| # TL;DR: This is a work in progress, may not be updated quickly or regularly, but I will update it when I make progress. This will eventually be a complete and OS/WM/DE independent guide, but it is here to see if anyone else wants this and/or is willing to help. 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. I will be working on when and where I can. 99% of what is here is based off the salt formula and [this topic](https://forum.qubes-os.org/t/using-another-de-wm-in-sys-gui/27085/4). | |
| This | [details="This guide is here currently for anyone who would like to join me in doing the work. The Guide will be updated when I have actionable information. I'm doing my best to keep clutter out of the guide. It will likely go through several iterations, but it will be turned into a working guide when I am finished. "] This is currently a WIP and will be updated as I figure it out. Currently, I am figuring out if there are any packages listed in the salt configs for sys-gui template that will solve any problems. My goal is to make this work with as few and as simple changes as possible so as to be easy to configure and maintain, so work may be slow as I pinpoint exact issues. As of this moment, qube applications will not launch, sys-gui terminal (and most likely all applications) are labeled as dom0 in the wm, there is no systray or widgets, and it is too slow for comfort when logging in and starting the wm. Who knows what else; I'm tackling the issues as they arise. This guide is for debain-12-minimal and AwesomeWM, because that is what I am using; I plan to expand this to be OS and DE/WM independent. Lastly, I am very busy and may not post regular updates. My schedule is unpredictable and I may get this done quickly or I may be very slow. I will do what I can when I can, and I will update when significant progress (or failure) is made. Any help is appreciated! [/details] |
| [details="Progress in AwesomeWM/Debian Minimal:"] | |
| `sys-gui# | `sys-gui# XSESSION=awesome` |
| [/details] [details="**Working Guide:** AwesomeWM on Fedora XFCE Template:";] 1. Start completely fresh with new sys-gui and clean fedora-39-xfce template. (Delete old and reinstall with salt formula.) 2. In sys-gui template (fedora-39-xfce if unmodified), install awesome package. Copy `/usr/share/awesome/lib/qubes.lua` to this template from dom0 and move to same place in template as it was in dom0. Shutdown template. 3. In sys-gui, open a Xen console, login as `user`. Alternatively login to GUI session and open a terminal. This will confirm that there are no problems so far. 4. In sys-gui terminal execute: `sys-gui$ echo "exec awesome" | tee ~/.xinitrc 1> /dev/null` `sys-gui$ XSESSION=awesome` `sys-gui$ mkdir ~/.config/awesome/ && sudo cp /etc/xdg/awesome/rc.lua .config/awesome/` (The above command is unnecessary, but it moves the Awesome config to user dir to avoid errors from editing it should you do so. I personally consider it a part of correctly configuring Awesome, but it will run fine without.) 5. In dom0 terminal, execute: `dom0$ qubes-prefs default_guivm sys-gui` `dom0$ [/details] # Here is the current roadmap: | |
| 1. Get everything functioning correctly in fedora-40-xfce based sys-gui. This will mostly be a Qubes thing, since that should already function perfectly. 2. Get AwesomeWM functioning perfectly in fedora-40-xfce based sys-gui. I don't anticipate problems. 3. Get AwesomeWM working in fedora-40-minimal based sys-gui. This will just be a matter of figuring out which packages are necessary and which aren't. | 1. [Done] Get everything functioning correctly in fedora-40-xfce based sys-gui. This will mostly be a Qubes thing, since that should already function perfectly. 2. [Done] Get AwesomeWM functioning perfectly in fedora-40-xfce based sys-gui. I don't anticipate problems. 3. [In-progress] Get AwesomeWM working in fedora-40-minimal based sys-gui. This will just be a matter of figuring out which packages are necessary and which aren't. |
| Note: I don't plan to port this to Debian soon. It is in the plans, but I have absolutely no clue what is going on there. I will cross that bridge when I get to it. As far as DEs/WMs other than AwesomeWM and i3wm, they shouldn't be any different to get working than in dom0 if both Awesome and i3 work, so I'll just link those guides (if they exsit) when this is through. [/details] | Note: I don't plan to port this to Debian soon. It is in the plans, but I have absolutely no clue what is going on there. I will cross that bridge when I get to it. As far as DEs/WMs other than AwesomeWM and i3wm, they shouldn't be any different to get working than in dom0 if both Awesome and i3 work, so I'll just link those guides (if they exsit) when this is through. Updates will be removed when the guide is finalized. There will also likely be a visual overhaul. [/details] |
| This is a work in progress, may not be updated quickly or regularly, but I will update it when I make progress. This will eventually be a complete and OS/WM/DE independent guide, but it is here to see if anyone else wants this and/or is willing to help. 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. I will be working on when and where I can. 99% of what is here is based off the salt formula and [this topic](https://forum.qubes-os.org/t/using-another-de-wm-in-sys-gui/27085/4). The Guide will be updated when I have actionable information. I'm doing my best to keep clutter out of the guide. Here is the current roadmap: [details="Summary:"] 1. Get everything functioning correctly in fedora-40-xfce based sys-gui. This will mostly be a Qubes thing, since that should already function perfectly. 2. Get AwesomeWM functioning perfectly in fedora-40-xfce based sys-gui. I don't anticipate problems. 3. Get AwesomeWM working in fedora-40-minimal based sys-gui. This will just be a matter of figuring out which packages are necessary and which aren't. 4. Get i3wm working in sys-gui. Note: I don't plan to port this to Debian soon. It is in the plans, but I have absolutely no clue what is going on there. I will cross that bridge when I get to it. As far as DEs/WMs other than AwesomeWM and i3wm, they shouldn't be any different to get working than in dom0 if both Awesome and i3 work, so I'll just link those guides (if they exsit) when this is through. [/details] |
| Step two is | Step two is done. AwesomeWM currently works with no (major) problems. I will update with a list of minor problems soon. |
| This is a work in progress, may not be updated quickly or regularly, but I will update it when I make progress. This will eventually be a complete and OS/WM/DE independent guide, but it is here to see if anyone else wants this and/or is willing to help. 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. I will be working on when and where I can. 99% of what is here is based off the salt formula and [this topic](https://forum.qubes-os.org/t/using-another-de-wm-in-sys-gui/27085/4). | This is a work in progress, may not be updated quickly or regularly, but I will update it when I make progress. This will eventually be a complete and OS/WM/DE independent guide, but it is here to see if anyone else wants this and/or is willing to help. 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. I will be working on when and where I can. 99% of what is here is based off the salt formula and [this topic](https://forum.qubes-os.org/t/using-another-de-wm-in-sys-gui/27085/4). # Update: Step one of the roadmap is complete after a reinstall of sys-gui. Step two is well on the way with AwesomeWM working in sys-gui (fedora-39-xfce) with only one major problem: qubes-core-admin-client is crashing. I replicated the problem on XFCE after AwesomeWM, so I'm kicking this up the chain as I have looked and don't have a clue what's happening. |