Develpment: cloned sd-app fails to start

[deeplow]

Description

We're doing on-boot configuration for various qubes via systemd-triggered scripts. We decided not to use qubes' names (per Marek's suggestion) in order to be able to clone them. However, sd-app ended up being hard-coded. This should change, to enable cloning of sd-app for debugging purposes (e.g. testing with two client applications).

Steps to Reproduce

In dom0 run:

1. qvm-clone sd-app sd-app2
2. qvm-run -p sd-app2 xfce4-terminal

Expected Behavior

sd-app2 starts as usual and opens a terminal

Actual Behavior

[user@dom0 ~]$ qvm-run -p sd-app2 xfce4-terminal
2025-01-30 11:45:41.847 qrexec-client[55667]: qrexec-daemon-common.c:232:connect_unix_socket: connect /var/run/qubes/qrexec.sd-app2
2025-01-30 11:45:41.847 qrexec-client[55667]: qrexec-daemon-common.c:29:negotiate_connection_params: write daemon: Bad file descriptor

Comments

The issue is with the hard-coded sd-app name here. We should instead check that SD_MIME_HANDLING==sd-app. This way a cloned sd-app will have the same vm-config value.