On a newly installed Qubes 4.1RC1, I get a notification at the top of the bar for the default Fedora-34 template.
When I run the update I get the following error message:
Error on updating fedora-34: Command '['sudo', 'qubesctl',
'--skip-dom0', '--targets=fedora-34, '--show-output', 'state.sls',
'update.qubes-vm']' returned non-zero exit status 1
Fedora-34: ERROR (exception Failed to copy Salt configuration to disp-mgmt-fedora-34)
I have solved the problem by a template reinstallation:
qvm-template --enablerepo qubes-templates-itl-testing reinstall fedora-34
Hello, I’m experiencing the same issue upgrading from Qubes 4.0 to 4.1 stable, but trying this method give me the following error:
Template 'fedora-34' is not managed by qvm-template.
Do you have any suggestion?
Thanks
Edit:
I solve my issue following this post. Sorry for re-open the thread!
Updating fedora-34
ID: dnf-and-rpm
Function: pkg.installed
Result: True
Comment: All specified packages are already installed and are at the desired version
Started: 16:02:12.924196
Duration: 4699.629 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: 16:02:17.645402
Duration: 1.454 ms
Changes:
ID: dnf-makecache
Function: cmd.script
Result: True
Comment: DNF cache successfully created
Started: 16:02:17.652371
Duration: 39796.009 ms
Changes:
ID: Disable deltarpm
Function: file.append
Name: /etc/dnf/dnf.conf
Result: True
Comment: File /etc/dnf/dnf.conf is in correct state
Started: 16:02:57.448676
Duration: 5.033 ms
Changes:
ID: update
Function: pkg.uptodate
Result: True
Comment: Upgrade ran successfully
Started: 16:02:57.455901
Duration: 55949.762 ms
Changes:
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: 16:03:53.405950
Duration: 25276.464 ms
Changes:
----------
pid:
1214
retcode:
0
stderr:
stdout:
Total states run: 6
Total run time: 125.728 s
Updating fedora-34-clone-1
ID: dnf-and-rpm
Function: pkg.installed
Result: True
Comment: All specified packages are already installed and are at the desired version
Started: 16:07:37.416980
Duration: 3271.924 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: 16:07:40.702275
Duration: 1.736 ms
Changes:
ID: dnf-makecache
Function: cmd.script
Result: True
Comment: DNF cache successfully created
Started: 16:07:40.708409
Duration: 13757.907 ms
Changes:
ID: Disable deltarpm
Function: file.append
Name: /etc/dnf/dnf.conf
Result: True
Comment: File /etc/dnf/dnf.conf is in correct state
Started: 16:07:54.466788
Duration: 12.115 ms
Changes:
ID: update
Function: pkg.uptodate
Result: True
Comment: Upgrade ran successfully
Started: 16:07:54.482599
Duration: 32479.258 ms
Changes:
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: 16:08:26.962217
Duration: 4164.814 ms
Changes:
----------
pid:
1211
retcode:
0
stderr:
stdout:
Total states run: 6
Total run time: 53.688 s
Is the star symbol a design error if fedora-34 keeps wanting to update? Should it not stay updated after updated and the logo changed? Why do the fedora-34 want to be updated every time over and over and how do i turn that off?
If i click update right after updating fedora, fedora is checked again straight away…
How do i remove that so the system looks updated even if it is?