Hello Qubes Community,
I have received multiple requests to accept an update of ‘dom0’ content lately.
The only info I’ve received after performing these updates has been:
Hello Mike,
Same behaviour happened again just now!
Is there any way to get more information (i.e. announcements, logs, notifications etc.)?
Viktor
What's the result of running `sudo qubes-dom0-update` in dom0 terminal?
Here’s the log:
[vr@dom0 ~]$ sudo qubes-dom0-update
Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time…
warning: Converting database from bdb to sqlite backend
Warning: Enforcing GPG signature check globally as per active RPM security policy (see ‘gpgcheck’ in dnf.conf(5) for how to squelch this message)
Fedora 25 - x86_64 7.7 MB/s | 50 MB 00:06
Fedora 25 - x86_64 - Updates 7.3 MB/s | 24 MB 00:03
Qubes Dom0 Repository (updates) 604 kB/s | 2.4 MB 00:04
determining the fastest mirror (14 hosts)… done.-- B/s | 0 B --:-- ETA
Qubes Templates repository 4.9 kB/s | 5.9 kB 00:01
Dependencies resolved.
Nothing to do.
Complete!
No packages downloaded
Qubes OS Repository for Dom0 24 MB/s | 29 kB 00:00
[vr@dom0 ~]$
Viktor
Looks good to me
Hello unman,
Hello unman,
> Looks good to me
>Can you please elaborate a bit more! - What were you looking for?
I was looking for a problem with the update process.
There has been a long thread in the forum about why you should use the
updated tool instead of updating locally. In brief, it's used to apply
other things (e.g. configuration changes) besides raw updates.
- Why is 'qubes updater' notified in the first place, if nothing needs
to be done? - OR -
- If something got done 'locally', why isn't at least a minimal
information about the performed activity returned?This inconsistency / uncertainty is confusing (at least to me ).
Because the updater does more than just update, it is possible that
there are things not applied.
What's the situation here? What Qubes version are you on? Do you mean
that dom0 is always marked a requiring updates in the updater tool?
Is it still showing that updates are required?
Can you please elaborate a bit more! - What were you looking for?
I was looking for a problem with the update process.
There has been a long thread in the forum about why you should use the
updated tool instead of updating locally. In brief, it’s used to apply
other things (e.g. configuration changes) besides raw updates.
Looks like I should subscribe to the new forum !
Why is ‘qubes updater’ notified in the first place, if nothing needs
to be done? - OR -If something got done ‘locally’, why isn’t at least a minimal
information about the performed activity returned?This inconsistency / uncertainty is confusing (at least to me ).
Because the updater does more than just update, it is possible that
there are things not applied.What’s the situation here? What Qubes version are you on?
Qubes version is 4.0 - for more info I’ve attached the info from
‘qubes manager’ below.
Do you mean
that dom0 is always marked a requiring updates in the updater tool?
No, not always. - But lately multiple updates have been requested for
dom-0, which I performed - but- the system did not provide any change
info …
Is it still showing that updates are required?
No, currently there is no notification active about a required update for
dom-0.
With kind regards,
Viktor
xen_version : 4.8.5-34.fc25
Linux 5.4.125-1.fc25.qubes.x86_64
Installed Packages:
kernel-qubes-vm.x86_64 1000:5.4.107-1.fc25.qubes
kernel-qubes-vm.x86_64 1000:5.4.120-1.fc25.qubes
kernel-qubes-vm.x86_64 1000:5.4.125-1.fc25.qubes
python2-qubesadmin.noarch 4.0.32-1.fc25
python2-qubesimgconverter.x86_64 4.0.31-1.fc25
python3-qubesadmin.noarch 4.0.32-1.fc25
python3-qubesdb.x86_64 4.0.16-1.fc25
python3-qubesimgconverter.x86_64 4.0.34-1.fc25
qubes-anaconda-addon.noarch 4.0.11-1.fc25
qubes-artwork.noarch 4.0.1-2.fc25
qubes-core-admin-addon-whonix.noarch 4.0.2-1.fc25
qubes-core-admin-client.noarch 4.0.32-1.fc25
qubes-core-dom0.x86_64 4.0.58-1.fc25
qubes-core-dom0-linux.x86_64 4.0.30-1.fc25
qubes-core-dom0-linux-kernel-install.x86_64
qubes-db.x86_64 4.0.16-1.fc25
qubes-db-dom0.x86_64 4.0.16-1.fc25
qubes-db-libs.x86_64 4.0.16-1.fc25
qubes-desktop-linux-common.noarch 4.0.22-1.fc25
qubes-desktop-linux-manager.noarch 4.0.25-1.fc25
qubes-gpg-split-dom0.x86_64 2.0.50-1.fc25
qubes-gui-dom0.x86_64 4.0.13-1.fc25
qubes-img-converter-dom0.x86_64 1.2.10-1.fc25
qubes-input-proxy.x86_64 1.0.23-1.fc25
qubes-input-proxy-receiver.x86_64 1.0.23-1.fc25
qubes-libvchan-xen.x86_64 4.0.9-1.fc25
qubes-manager.noarch 4.0.45-1.fc25
qubes-menus.noarch 4.0.22-1.fc25
qubes-mgmt-salt.noarch 4.0.26-1.fc25
qubes-mgmt-salt-admin-tools.noarch 4.0.26-1.fc25
qubes-mgmt-salt-base.noarch 4.0.4-1.fc25
qubes-mgmt-salt-base-config.noarch 4.0.2-1.fc25
qubes-mgmt-salt-base-overrides.noarch 4.0.2-1.fc25
qubes-mgmt-salt-base-overrides-libs.noarch
qubes-mgmt-salt-base-topd.noarch 4.0.2-1.fc25
qubes-mgmt-salt-config.noarch 4.0.26-1.fc25
qubes-mgmt-salt-dom0.noarch 4.0.26-1.fc25
qubes-mgmt-salt-dom0-qvm.noarch 4.0.10-1.fc25
qubes-mgmt-salt-dom0-update.noarch 4.0.10-1.fc25
qubes-mgmt-salt-dom0-virtual-machines.noarch
qubes-pdf-converter-dom0.x86_64 2.1.12-1.fc25
qubes-release.noarch 4.0-10
qubes-release-notes.noarch 4.0-10
qubes-rpm-oxide.x86_64 0.2.2-1.fc25
qubes-template-debian-10.noarch 4.0.1-201910230150
qubes-template-fedora-33.noarch 4.0.6-202012100255
qubes-template-whonix-gw-15.noarch 4.0.1-202003070901
qubes-template-whonix-ws-15.noarch 4.0.1-202003070901
qubes-usb-proxy-dom0.noarch 1.0.30-1.fc25
qubes-utils.x86_64 4.0.34-1.fc25
qubes-utils-libs.x86_64 4.0.34-1.fc25
qubes-windows-tools.noarch 4.0.1-3
xfce4-settings-qubes.x86_64 4.0.3-1.fc25