deeplow

> > But I have a feeling those who come to the website may mostly want to answer the question **why use qubes?** > > Perhaps this should be directly...

Happened again this morning. journalctl ``` Sep 10 06:46:00 dom0 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-16890-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Sep 10 06:46:00 dom0 kernel: audit: type=1130...

I've run into the same issue. > Anyway, maybe it should simply call python3 /run/qubes-update/agent/entrypoint.py, instead of just /run/qubes-update/agent/entrypoint.py, what do you think @piotrbartman ? This indeed fixes it.

@UndeadDevel This is an intended regression, I think. Block devices are confusing for novice users and advanced users can use `qvm-block`. This was talked about in the Qubes summit.

@dmoerner said: > This is an obvious regression. Qubes own labels are not sufficient to disambiguate the block device which exposes the whole partition table from a specific partition. And...

Then I guess what's needed it: - a) a better heuristic for the device name - b) (or) some sort of :information_source: button which shows the labels of all the...

I don't think it is because here the problem is when calling it from the terminal and not necessarily just a problem with the UI itself.

Not really. My point here is that the "restart" option doesn't get selected at all. So the app qubes don't even shut down by default much less restart. So it's...

It may well be the same, but at least the symptoms are slightly different and so I'd argue it merits to different reports until that is cleared up. I should...

I have noticed that on my original screenshot the qubes were not selected, but on a new install they are. I believe that the system which I used to report...