Did 11/02/26 dom0 updates break qvm-run?

General Discussion
1

I’m not sure if I’m just tired, or if the behavior of qvm-run is different now, since updating dom0 a couple of days ago.

Now when I run:

qvm-run -u root <vm_name> xterm

I get a terminal under the user account, not root. That’s different from how it was a few days ago. At least, I think it is? I only upgraded to 4.3 recently.

Also, should sysmaint apply to debian-13 templates, or just whonix? Because it’s not present on debian-13.

Also, several of my templates (ex: debian-13-xfce, fedora-42) are failing to update using the update manager. But they succeed when I do it manually.

Did this new dom0 upgrade change the updater code somewhere?

Am I right or am I just tired?

2

No, I get a root prompt (and was able to use sudo)

I updated dom0 and whonix just before I did this.

Just whonix. If you look at debian advanced settings, there is no option to boot in different modes. It’s a whonix “feature”, nothing to do with debian (except whonix is based off debian)

1 Like
3

Mea culpa. No further comments.

EDIT: PEBKAC :man_facepalming:

4

Maybe this is related?:

1 Like
5

Very disappointing:not an issue in 4.3. Does this affect all templates
in 4.2

I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.

6

@barto edited the post. This is the current content:

Mea culpa. No further comments.

EDIT: PEBKAC :man_facepalming:

7

Thanks. So is this an issue or no?

I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.

8

It is NOT an issue for me.

9

I guessed that from your edit.
Absent any other input it looks as if the answer to the original question
would be “No”, and OP will have to look elsewhere for cause of issue.

I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.

10

This is the same behavior as reported in

1 Like
11

Yes it is

I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.

12

I provided debugging steps on Github, please follow up there.

1 Like
13

link?

14

That isn’t clear yet. Waiting for more replies before passing judgement. There are two issues, both of which started after upgrading dom0. It might be similar to Root access fails on templates, causing qubes-dist-upgrade error - #2 by ephile. I will check when I have time. But the fact that the error is so similar makes me feel better that it’s not user error.(despite what @barto suggested above). (It would be hard for it to be user error. There’s not enough interaction for that to be true.)

And it’s still notable that it started immediately after a dom0 upgrade. Are there release notes for the most recent dom0 upgrade, which I could read?

Feel free to actually participate in the discussion by providing troubleshooting steps. Then I can provide that “oher input” .

15

Interesting. IT seems similar, yes. Except that I did not have the problem for two weeks after restoring the minimal templates on 4.3. It started afeter I upgraded tdom0- a few days ago. I’ll read that issue obviously. But there was at least a “trigger” from the recent dom0 changes.