Closed tumbletree closed 1 year ago
update
gnome-terminal
, as previous template. Works on debian-10 template and all fedora-based app-vms.apt
: it reported 3 qubes packages upgradable but wouldn't upgrade them. (I'm sorry, I thought we could update a template that way?). Upgraded fine through Updater.update2 (I'm just doing this as I go, in case I lose access to the machine).
gnome-terminal
update3
nautilus
results in mouse clicks (right and left) being non-responsive for ~20-40s.gnome-terminal
works now.
Are there any disk/filesystem-related errors in the dom0 journal?
Anything out of the ordinary if you:
journalctl -f
in one terminalThen see logs within the VM:
sudo virsh console VM-NAME-HERE
)journalctl -f
Hi, and thanks.
Update: it now seems like I have a couple of qubes launching gnome-terminal, and a bunch that don't, all from the same template.
For 1-3, journalctl -f
in xterm
, I see an error message. I can't cut-and-paste from that app, so I'll try accurate hand retyping.
This is from "email" app-vm.
Oct 31 #time email qubes.StartApp+org.gnome.Terminal-dom)1027: ** * Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached**
There's a message before it successfully starting tracker-store.service
, and after it successfully starting Mark
then grub-boot-success
then Finished Mark boot as successful
.
I got sudo: virsh: command not found
in app-vms, but launched it in dom0. There is no opportunity to launch journalctl -f
, but there's about 50 lines of journaling of some kind. However, there's absolutely no reaction when I try and fail to launch gnome-terminal
in "email" -vm.
In contrast, I did the same for a vm where gnome-terminal is working, and I watched register a couple of lines. I am guessing you aren't too surprised at this, however. Sorry, this is all new territory to me and I am out of my depth.
Is it appropriate to merge with #6168 ? Its all happening at once.
Is it appropriate to merge with #6168 ? Its all happening at once.
Only if they're actually the same bug (which may not be known until diagnosed). For details, please see here.
i also have corebooted (Heads) x230 and once every couple weeks running the Qubes Updater GUI will hard freeze the machine. never happens when updating via command line. next time i will share logs - if folks have a particular command i should use let me know.
Is there actually reason to believe that this is Fedora-specific, much less specific to Fedora 32?
hi folks, this happened again. was updating multiple templates, it got halfway through and had just started updating the next template when the system hard froze. please tell me what commands i should run to share more useful info.
This issue is being closed because:
If anyone believes that this issue should be reopened and reassigned to an active milestone, please leave a brief comment. (For example, if a bug still affects Qubes OS 4.1, then the comment "Affects 4.1" will suffice.)
Qubes OS version 4.0.3
Affected component(s) or functionality Updater, fedora-32 template, system.
Brief summary Updater starts normal, black notification box (I think its the one that announces mngmt disp start up), then the whole system freezes. Hard restart required.
Repeated twice.
Additionally, template will not launch
gnome-terminal
by any method.Debian-10 template (also in first notification) updated fine.
To Reproduce
Steps to reproduce the behavior:
Expected behavior The usual update procedure.
Actual behavior System freeze within seconds. Hard restart required. (Replicable.)
Tried to update template by
dnf
in terminal, butgnome-terminal
is not launched by any menu option (although template starts up) or dom0qvm-run...
.Additional context
Unaware of any changes by me to the template or Qubes settings.
I've seen this before, but maybe not this stubborn. I think it was fixed by waiting a few days, which suggests you need notification and fixing your side (?).
This is a corebooted x230, plenty of RAM.
Also, though probably unrelated, system is NOT recognising dual screen set-up (in dock) on start-up all of a sudden now.
xrandr
command rectifies.Solutions you've tried
tried via gnome terminal (fail; see above).
Currently attempting to fall back to backup template, but writing this up first.
Relevant documentation you've consulted
Related, non-duplicate issues