% sudo journalctl -e | tee /tmp/log >/dev/null
% grep -i 'cannot remove' /tmp/log
If it was a disposable (you mentioned dispX above), then:
</tmp/log grep X
Where X is the qube name you want to grep.
After trying to follow the docs, everything is working fine, so I don’t think my answer should be the solution (or I should remove the first sentence). Let’s see how it goes with the logs.
Jul 24 03:11:03 dom0 qubesd[3367]: INFO: vm.disp9618: Preload startup waiting ‘qubes.WaitForRunningSystem’ with ‘60’ seconds timeout
Jul 24 03:11:03 dom0 qubesd[3367]: WARNING: protocol error for call b’admin.vm.device.webcam.Attached’+b’’ (b’dom0’ → b’disp9618’) with payload of 0 bytes
Jul 24 03:11:03 dom0 qrexec-policy-daemon[4512]: qrexec: qubes.GetDate+nanoseconds: disp9618 → @default: allowed to dom0
Jul 24 03:11:04 dom0 qubesd[3367]: INFO: vm.disp9618: Preload startup completed ‘qubes.WaitForRunningSystem’
Jul 24 03:11:04 dom0 qubesd[3367]: INFO: vm.disp9618: Setting qube memory to pref mem
Jul 24 03:11:04 dom0 qubesd[3367]: INFO: vm.disp9618: Preloading completed
Jul 24 03:11:04 dom0 qubesd[3367]: INFO: vm.disp9618: Paused preloaded qube
Jul 24 05:14:26 dom0 qubesd[3367]: INFO: vm.default-dvm: Removing excess qube(s) from preloaded list because there may be absent qubes: ‘disp9618, disp5318’
Jul 24 05:14:28 dom0 qubesd[3367]: INFO: Removing appmenus for ‘disp9618’ in ‘dom0’
Jul 24 05:14:29 dom0 qubesd[3367]: INFO: vm.disp9618: Removing volume root: qubes_dom0/vm-disp9618-root
Jul 24 05:14:29 dom0 qubesd[3367]: INFO: vm.disp9618: Removing volume private: qubes_dom0/vm-disp9618-private
Jul 24 05:14:29 dom0 qubesd[3367]: INFO: vm.disp9618: Removing volume volatile: qubes_dom0/vm-disp9618-volatile
Jul 24 05:14:29 dom0 qubesd[3367]: INFO: vm.disp9618: Removing volume kernel: 6.18.35-1.fc41
The other nada returns nothing.
[@dom0 ~]$ sudo journalctl -e | tee /tmp/log >/dev/null
[@dom0 ~]$ grep -i 'cannot remove' /tmp/log
[@dom0 ~]$ </tmp/log grep disp5718
wait typo
Jul 24 03:11:00 dom0 qubesd[3367]: WARNING: protocol error for call b’admin.vm.device.webcam.Attached’+b’’ (b’dom0’ → b’disp5318’) with payload of 0 bytes
Jul 24 03:11:01 dom0 qrexec-policy-daemon[4512]: qrexec: qubes.GetDate+nanoseconds: disp5318 → @default: allowed to dom0
Jul 24 03:11:01 dom0 qubesd[3367]: INFO: vm.disp5318: Preload startup completed ‘qubes.WaitForRunningSystem’
Jul 24 03:11:01 dom0 qubesd[3367]: INFO: vm.disp5318: Setting qube memory to pref mem
Jul 24 03:11:03 dom0 qubesd[3367]: INFO: vm.disp5318: Preloading completed
Jul 24 03:11:03 dom0 qubesd[3367]: INFO: vm.disp5318: Paused preloaded qube
Jul 24 05:14:26 dom0 qubesd[3367]: INFO: vm.default-dvm: Removing excess qube(s) from preloaded list because there may be absent qubes: ‘disp9618, disp5318’
Jul 24 05:14:28 dom0 qubesd[3367]: INFO: Removing appmenus for ‘disp5318’ in ‘dom0’
Jul 24 05:14:29 dom0 qubesd[3367]: INFO: vm.disp5318: Removing volume root: qubes_dom0/vm-disp5318-root
Jul 24 05:14:29 dom0 qubesd[3367]: INFO: vm.disp5318: Removing volume private: qubes_dom0/vm-disp5318-private
Jul 24 05:14:29 dom0 qubesd[3367]: INFO: vm.disp5318: Removing volume volatile: qubes_dom0/vm-disp5318-volatile
Jul 24 05:14:29 dom0 qubesd[3367]: INFO: vm.disp5318: Removing volume kernel: 6.18.35-1.fc41
This was wrong string that I typed… but doesn’t import much now…
I don’t see any error there, I think the message was just shared with the client. You’d possibly see it if using qvm-prefs QUBE template TEMPLATE, but no need to run it now, let it for next time.
odd that it was looking for a web cam. I don’t have one and never have. no interest. Kind of concerning is it possible there is a bit malware trying to access the webcam?
This is just a qui-devices integration, Nothing suspicious.