ISO qubes issues & strange sys-usb issues.(funny boot stuff as well...)

[apparatus]

@Zamm

So in relation, issues I have encounter with attaching usb devices…Previously on my laptop I would simply need to select the USB device and attach to the Qube no issue and the file manager would display it under devices to access the files, etc.
This is no longer the case…I would need to select the data block which would have multiple options from the same device and it very much would be a narrowing down game and if you attach the incorrect one all the others will no show again and you would need to unplug and repeat. I’ve tried this with multiple usbs, external hardrives and purchase a brand new usb stick which showed 3 possible options in the datablock and gave me these same issues.
My assumption is that this is due to a recent update during a time I wasn’t actively using Qubes and I could be greatly wrong however I believe this was either mentioned in this years summit or I believe I read it in one of the update docs but can’t recall and unfortunately
don’t have the availability to scour for it

Again any advisory regarding this would be great, I am quiet perplexed how that just attaching the usb device to the Qube doesn’t work (possibly just for me) like how it used to.

This seems to be a bug:

Device widget bug

Well, it happens with the block devices too. When I attach them as block devices: if I attach whole device, its partitions get lost. If I attach partition, whole device get lost and only that partition remains visible attached and after when detached. No one else experience this? I’m using sys-usb minimals based on fedora, regardless of its version.

@Zamm

Now one of the true wonders of my world all my network Qubes starting up on boot.
My main rule with Qubes is not to ever have anything run on boot, due to issue it caused on the laptop and more recent issues where such an evil setting has locked my out so many times with my tinkering
All of these qubes have the start on boot disabled but yet when I boot up and login they are all running(not good! EVER in my book. me don’t like.)
I had a similar issue like this on my laptop after a Qubes update where upon boot and login I would immediately have 12 - 20 tavs open in dom0 of the screen capture tool.

Like wise any advice as the Qubes starting up on boot is a big no for me.

Check the output of this command in dom0, it’ll show you the qubes with enabled autostart:

qvm-ls --fields NAME,autostart | grep True