Closed tumbletree closed 1 year ago
Check if you haven't run out of disk space. For example check data% and meta% columns for pool00 in sudo lvs head
.
Sorry, just crashed again (two debian-standalone qubes, stall on second one. That's a recurring theme, stalling on a second update).
EDIT: Got it from sudo lvm -a
. However, I don't understand what I am looking at (tabulation, significance):
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
[lvol0_pmspare] qubes_dom0 ewi------- 372.00m
pool00 qubes_dom0 twi-aotz-- 363.42g 16.73 15.83
[pool00_tdata] qubes_dom0 Twi-ao---- 363.42g
[pool00_tmeta] qubes_dom0 ewi-ao---- 372.00m
root qubes_dom0 Vwi-aotz-- 363.42g pool00 3.20
swap qubes_dom0 -wi-ao---- 7.66g
Isn't there ample diskspace in there? Can volumes reallocate space as required?
(edited for my misunderstandings).
Also, I still have problems launching gnome-teminal #6156. I thought it had righted it self with an update, but no. Just discovered only some qubes can launch gnome-terminal, while others cannot.
For those that cannot, with journalctl -f
I get:
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**
I just don't know if these issues are related. System is quickly becoming unworkable.
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 launch on system startup of sys-usb
Brief summary Powering on delivers a system with no USB functionality; sys-usb is not started automatically.
USB icon in tray shows (internal) microphone only available for assignment.
Manual start of sys-usb qube works fine.
This only began since last update of fedora-32 last night.
Note the fedora update froze the system again, but worked on second attempt.
To Reproduce
Steps to reproduce the behavior:
Not sure exactly where to start.
Expected behavior Unremarkable automatic startup of sys-usb.
Actual behavior
Need to manually start sys-usb.
Screenshots
Additional context
I've already noted a problem with fedora-32 updates freezing the system.
I don't know if its relevant, but another start-up malfunction began recently: my laptop+monitor setup used to start up with 2 separate screens. Suddenly, it has begun starting in 'mirror' format. This began not long after -but not immediately after - I created a shortcut for an
xrandr
command to help return the laptop to the dock with the external monitor.Also have
dmesg
output - not sure where to put it, (large). On request I'll post.Solutions you've tried
I really don't know where to start.
Relevant documentation you've consulted
Related, non-duplicate issues
As mentioned above, #6156.