Random Usability Request

[otter2]

It doesn’t fulfill your request, but I hope it will improve the situation.

@dispuser

You have to go then to “Q” again and find VM, now in different place, and find settings.

You don’t need to go to the qubes app menu to access settings. If you’re running xfce, you can use xfce4-appfinder (call it with alt+F3) and just search for it.

If that doesn’t fit your workflow, you can keep qube manager window open and call setting from there.

Another alternative would be to edit shutdown script from the quality of life guide to open settings after shutting down a qube, and assign it to a hotkey or alias, your imagination is the limit:

#!/bin/bash
# Thanks tasket!

CUR_WIN_ID=`xdotool getwindowfocus`
CUR_VM=`xprop _QUBES_VMNAME -id $CUR_WIN_ID |cut -d \" -f2`

qvm-run $CUR_VM 'xdotool search --name "Mozilla Firefox" key ctrl+q'
qvm-run $CUR_VM 'xdotool search --name "Mozilla Thunderbird" key ctrl+q'
sleep 4
/usr/bin/qvm-shutdown $CUR_VM  --wait --timeout=40 && \
qubes-vm-settings $CUR_VM # Open settings if qvm-shutdown is successful

@dispuser

Sometimes I have multiple VMs and will use Nvidia device attached to one then move to Nvidia to another Qube. Sometimes use beta software and new version has problem, requires 5 restart when setting up.

If qubes that need nvidia device passed to them are not going to run simultaneously, you can assign the device to all of them. Passthrough happens on start of a domain, so there will be no conflict.

Edit:

@dispuser

However, during this process if the VM is shutting down, the VM name will often go from top of list to just completely disappear. You have to go then to “Q” again and find VM, now in different place, and find settings.

You can change this behaviour in Qubes Menu Settings.