Skip to content
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.

Sign up for GitHub

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

Jump to bottom

GUI domain system configuration #4186

Open
2 of 7 tasks
marmarek opened this issue Aug 6, 2018 · 2 comments
Open
2 of 7 tasks

GUI domain system configuration #4186

marmarek opened this issue Aug 6, 2018 · 2 comments
Labels
C: gui-domain P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality.

Comments

@marmarek
Copy link
Member

marmarek commented Aug 6, 2018 •
edited
Loading

Configure graphical system in GUI domain (for GUI/Admin domain split), including required qrexec services:

  • multi-display handling, including dynamic configuration (specifically in fallback case without real GPU passthrough)
  • power reporting (battery, AC)
  • RPC for managing dom0 powerstate (shutdown, restart, etc.)
  • screen locker - choose one; if applicable - prevent vt switch
  • disable "new login" feature
  • Debian packaging for current only dom0 (Fedora) components (e.g. manager, artwork, desktop-linux-xfce4*)
  • touchpad configuration, and various other input devices configuration that isn't passed through GUI protocol / input proxy
@marmarek marmarek added the T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. label Aug 6, 2018
@marmarek marmarek added this to the Release 4.1 milestone Aug 6, 2018
@marmarek marmarek mentioned this issue Aug 6, 2018
Closed
7 tasks
@andrewdavidwong andrewdavidwong mentioned this issue Aug 26, 2018
Closed
@fepitre fepitre self-assigned this Oct 16, 2019
@fepitre fepitre mentioned this issue Oct 19, 2019
Closed
3 tasks
This was referenced Nov 6, 2019
Merged
Merged
Merged
Merged
Merged
fepitre added a commit to fepitre/qubes-desktop-linux-xfce4-xfwm4 that referenced this issue Jun 14, 2020
@fepitre
debian: initial packaging from upstream
9050155 
- add qubes-builder integration

QubesOS/qubes-issues#4186
fepitre added a commit to fepitre/qubes-desktop-linux-xfce4 that referenced this issue Jun 14, 2020
@fepitre
debian: initial packaging
26a8eff 
- clean Makefile and add 'install' target
- refactor spec according to Makefile

QubesOS/qubes-issues#4186
fepitre added a commit to fepitre/qubes-desktop-linux-xfce4-garcon that referenced this issue Jun 14, 2020
@fepitre
debian: add debian packaging from upstream
7ce8adb 
- add integration with qubes-builder
- refactor spec and makefile

QubesOS/qubes-issues#4186
fepitre added a commit to fepitre/qubes-artwork that referenced this issue Jun 15, 2020
@fepitre
debian: add packaging
fdec484 
QubesOS/qubes-issues#4186
fepitre added a commit to fepitre/qubes-artwork that referenced this issue Jun 15, 2020
@fepitre
debian: add packaging
fe28261 
QubesOS/qubes-issues#4186
fepitre added a commit to fepitre/qubes-desktop-linux-xfce4 that referenced this issue Jun 16, 2020
@fepitre
debian: initial packaging
1da7d31 
- clean Makefile and add 'install' target
- refactor spec according to Makefile

QubesOS/qubes-issues#4186
fepitre added a commit to fepitre/qubes-gui-agent-linux that referenced this issue Jun 16, 2020
@fepitre
qubes-run-xephyr: debian has another path for shmoverride.so
33e155e 
QubesOS/qubes-issues#4186
fepitre added a commit to fepitre/qubes-gui-agent-linux that referenced this issue Jun 16, 2020
@fepitre
qubes-run-xephyr: debian has another path for shmoverride.so
e108271 
QubesOS/qubes-issues#4186
fepitre added a commit to fepitre/qubes-core-admin-client that referenced this issue Jun 16, 2020
@fepitre
debian: add guivm related content
1d358c8 
QubesOS/qubes-issues#4186
fepitre added a commit to fepitre/qubes-manager that referenced this issue Jun 16, 2020
@fepitre
debian: add packaging
6fce1a9 
QubesOS/qubes-issues#4186
fepitre added a commit to fepitre/qubes-manager that referenced this issue Jun 16, 2020
@fepitre
debian: add packaging
ef2eaa7 
QubesOS/qubes-issues#4186
fepitre added a commit to fepitre/qubes-desktop-linux-common that referenced this issue Jun 16, 2020
@fepitre
debian: fix dependency names
4b550a1 
QubesOS/qubes-issues#4186
fepitre added a commit to fepitre/qubes-desktop-linux-common that referenced this issue Jun 16, 2020
@fepitre
debian: fix dependency names
404297b 
QubesOS/qubes-issues#4186
This was referenced Jun 16, 2020
Merged
Merged
fepitre added a commit to fepitre/qubes-manager that referenced this issue Jun 16, 2020
@fepitre
debian: add packaging
d8de88b 
QubesOS/qubes-issues#4186
fepitre added a commit to fepitre/qubes-meta-packages that referenced this issue Jun 17, 2020
@fepitre
debian: sync with spec file and add guivm pkg
f85402b 
QubesOS/qubes-issues#4186
fepitre added a commit to fepitre/qubes-meta-packages that referenced this issue Jun 17, 2020
@fepitre
debian: sync with spec file and add guivm pkg
0451222 
QubesOS/qubes-issues#4186
marmarek added a commit to marmarek/qubes-core-qrexec that referenced this issue May 21, 2021
@marmarek
Use generic 'guivm' service to tell if running inside GUI VM
2f0d37a 
... instead of specific guivm-gui-agent.

QubesOS/qubes-issues#4186
@marmarek marmarek mentioned this issue May 21, 2021
Merged
marmarek added a commit to marmarek/qubes-core-admin that referenced this issue May 21, 2021
@marmarek
Use generic 'guivm' qvm-service to detect GUI VM
d51c1cb 
... instead of a specific guivm-gui-agent (which mean a hybrid one).

QubesOS/qubes-issues#4186
marmarek added a commit to marmarek/qubes-desktop-linux-manager that referenced this issue May 21, 2021
@marmarek
Start widgets only in dom0 and guivm
6fabe3d 
Other VMs do not have appropriate Admin API access, which will result in
log spamming (and a lot of notifications).

QubesOS/qubes-issues#4186
@marmarek marmarek mentioned this issue May 21, 2021
Merged
marmarek added a commit to marmarek/qubes-mgmt-salt-dom0-virtual-machines that referenced this issue May 22, 2021
@marmarek
sys-gui: do not intercept copy/paste key combos at dom0, let sys-gui …
1d528c8 
…see them

QubesOS/qubes-issues#4186
marmarek added a commit to marmarek/qubes-mgmt-salt-dom0-virtual-machines that referenced this issue May 25, 2021
@marmarek
sys-gui: do not intercept copy/paste key combos at dom0, let sys-gui …
edb5394 
…see them

QubesOS/qubes-issues#4186
marmarek added a commit to marmarek/qubes-mgmt-salt-dom0-virtual-machines that referenced this issue May 30, 2021
@marmarek
Do not disable xscreensaver in sys-gui
1d20b65 
Something needs to lock the screen. Lets do it from inside sys-gui (also
the hybrid one), for consistency. This way it will be also easier to
manage.

QubesOS/qubes-issues#4186
@marmarek marmarek mentioned this issue May 30, 2021
Merged
This was referenced May 30, 2021
Closed
Closed
@qubesos-bot qubesos-bot mentioned this issue Jun 17, 2021
Closed
Closed
@marmarek marmarek mentioned this issue Jun 25, 2021
Open
@qubesos-bot qubesos-bot mentioned this issue Jul 1, 2021
Closed
@qubesos-bot qubesos-bot mentioned this issue Jul 9, 2021
Closed
@qubesos-bot qubesos-bot mentioned this issue Aug 1, 2021
Closed
@qubesos-bot qubesos-bot mentioned this issue May 30, 2022
Closed
@fepitre fepitre removed their assignment Jul 11, 2023
@andrewdavidwong andrewdavidwong added the P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. label Aug 13, 2023
@andrewdavidwong andrewdavidwong removed this from the Release 4.2 milestone Aug 13, 2023
@marmarek marmarek mentioned this issue Sep 18, 2023
Closed
6 tasks
@marmarek marmarek moved this to Todo in GUI domain Sep 19, 2023
@xyhhx
Copy link

xyhhx commented Nov 1, 2024 •
edited
Loading

i just set up sys-gui-gpu (and sys-gui but i dont feel like using that), and noticed a few quirks or would-be nice-to-haves:

  • gui domains are based on the default template, which means they don't adopt dom0's desktop environment settings. the user has to configure keyboard shortcuts, panel configuration, etc again.
    • this might be considered a feature, as visual cues make it more obvious which domain is being used (dom0 or gui domain)
    • that said, a user might want to have consistency. perhaps a separate salt formula should handle this to make it opt-in?
  • the gui domain can't run as many admin commands as dom0 (for example qvm-run doesn't let you use -u $user from gui domain)
  • running qubes-sync-appmenus for every domain is kind of a bummer
  • qubes updater doesn't work from the gui domain as it doesn't have a netvm

i'll jot down more notes as i think of them

@marmarek
Copy link
Member Author

marmarek commented Nov 1, 2024

  • gui domains are based on the default template, which means they don't adopt dom0's desktop environment settings. the user has to configure keyboard shortcuts, panel configuration, etc again.

If you come from customized dom0, yes. But the plan is to have GUI domain from the very start, eventually.

running qubes-sync-appmenus for every domain is kind of a bummer

This is needed only once, though.

the gui domain can't run as many admin commands as dom0 (for example qvm-run doesn't let you use -u $user from gui domain)

Right, -u doesn't work from non-dom0. But --service ... qubes.VMRootShell should (I guess -u root could be translated to it automatically).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C: gui-domain P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality.
Projects
GUI domain
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
4 participants
@marmarek @andrewdavidwong @fepitre @xyhhx