Hi, is it just me or has anyone else had Fedora updates from the Qubes GUI 4 days in a row (30th Nov - 2nd Dec)? All updates seem to have completed btw.
Thanks
You are not alone 
What were the updates?
No idea what they were specifically, but I believe Op is referring to a number of template updates to fedora-36.
I found an update on that waiting for me 3 or 4 days in a row. I don’t recall a daily update for that number of days before.
1 Like
Not just you
Oh, sorry, I thought you revise your updates which could help in this “case”.
For example, I noticed qrexec (and a few other related packages from Qubes only) was updated twice in a given period. So, nothing unusual anyway, since Fedora is already known for frequent updates.,
Hello @enmus; they are GUI updates shown in the tray in the top right handside of Qubes and I have another one today!!?
Yep, me too.
Updating fedora-36-splitbrowser
fedora-36-splitbrowser:
----------
ID: dnf-and-rpm
Function: pkg.installed
Result: True
Comment: All specified packages are already installed and are at the desired version
Started: 12:55:03.605754
Duration: 1970.254 ms
Changes:
----------
ID: /usr/lib/rpm/macros.d/macros.qubes
Function: file.absent
Result: True
Comment: File /usr/lib/rpm/macros.d/macros.qubes is not present
Started: 12:55:05.585234
Duration: 2.96 ms
Changes:
----------
ID: dnf-makecache
Function: cmd.script
Result: True
Comment: DNF cache successfully created
Started: 12:55:05.591995
Duration: 30450.625 ms
Changes:
----------
ID: Disable deltarpm
Function: cmd.run
Name: echo deltarpm=False >> /etc/dnf/dnf.conf
Result: True
Comment: unless condition is true
Started: 12:55:36.043889
Duration: 2363.527 ms
Changes:
----------
ID: update
Function: pkg.uptodate
Result: True
Comment: Upgrade ran successfully
Started: 12:55:38.409885
Duration: 236465.733 ms
Changes:
----------
python3-dnf-plugins-qubes-hooks:
----------
new:
4.1.38-1.fc36
old:
4.1.37-1.fc36
python3-qubesadmin:
----------
new:
4.1.27-1.fc36
old:
4.1.26-1.fc36
qubes-core-admin-client:
----------
new:
4.1.27-1.fc36
old:
4.1.26-1.fc36
qubes-core-agent:
----------
new:
4.1.38-1.fc36
old:
4.1.37-1.fc36
qubes-core-agent-nautilus:
----------
new:
4.1.38-1.fc36
old:
4.1.37-1.fc36
qubes-core-agent-passwordless-root:
----------
new:
4.1.38-1.fc36
old:
4.1.37-1.fc36
qubes-core-agent-systemd:
----------
new:
4.1.38-1.fc36
old:
4.1.37-1.fc36
qubes-core-agent-thunar:
----------
new:
4.1.38-1.fc36
old:
4.1.37-1.fc36
qubes-core-qrexec:
----------
new:
4.1.20-1.fc36
old:
4.1.18-1.fc36
qubes-core-qrexec-libs:
----------
new:
4.1.20-1.fc36
old:
4.1.18-1.fc36
qubes-core-qrexec-vm:
----------
new:
4.1.20-1.fc36
old:
4.1.18-1.fc36
qubes-img-converter:
----------
new:
1.2.13-1.fc36
old:
1.2.12-1.fc36
qubes-pdf-converter:
----------
new:
2.1.14-1.fc36
old:
2.1.13-1.fc36
----------
ID: notify-updates
Function: cmd.run
Name: /usr/lib/qubes/upgrades-status-notify
Result: True
Comment: Command "/usr/lib/qubes/upgrades-status-notify" run
Started: 12:59:34.892616
Duration: 14350.851 ms
Changes:
----------
pid:
2601
retcode:
0
stderr:
stdout:
Summary for fedora-36-splitbrowser
------------
Succeeded: 6 (changed=2)
Failed: 0
------------
Total states run: 6
Total run time: 285.604 s
In a Fedora qube, as root or with sudo, you can use dnf history to get a numbered list of events, then dnf history info <number> to see details for each of them.
2 Likes
Hi, I’m looking at my history and would like some help with understanding the actions and altered columns, see attached.
Thanks
A quick google landed me on:
2 Likes