Viktor Ransmayr schrieb am Sonntag, 6. Dezember 2020 um 12:18:17 UTC+1: > > Viktor Ransmayr schrieb am Samstag, 5. Dezember 2020 um 22:59:57 UTC+1: > >> >> a...@qubes-os.org schrieb am Samstag, 5. Dezember 2020 um 22:29:45 UTC+1: >> >>> On 12/5/20 1:36 AM, Viktor Ransmayr wrote: >>> > Hello Qubes community, >>> > >>> > I noticed since yesterday, that the icon, which indicates that updates >>> are >>> > available, never gets cleared on my system, although I obviously try >>> to >>> > launch the updater in a timely fashion - and - the operation succeeds >>> ... >>> > >>> > Here's the log from the latest attempt: >>> > >>> > ### >>> > >>> > Updating fedora-32 >>> > >>> > fedora-32: >>> > ---------- >>> > ID: dnf list updates --refresh >/dev/null >>> > Function: cmd.run >>> > Result: True >>> > Comment: Command "dnf list updates --refresh >/dev/null" run >>> > Started: 09:00:59.753451 >>> > Duration: 8745.114 ms >>> > Changes: >>> > ---------- >>> > pid: >>> > 1077 >>> > retcode: >>> > 0 >>> > stderr: >>> > stdout: >>> > ---------- >>> > ID: update >>> > Function: pkg.uptodate >>> > Result: True >>> > Comment: Upgrade ran successfully >>> > Started: 09:01:10.612928 >>> > Duration: 24382.315 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: 09:01:34.995429 >>> > Duration: 3878.256 ms >>> > Changes: >>> > ---------- >>> > pid: >>> > 1148 >>> > retcode: >>> > 0 >>> > stderr: >>> > stdout: >>> > >>> > Summary for fedora-32 >>> > ------------ >>> > Succeeded: 3 (changed=2) >>> > Failed: 0 >>> > ------------ >>> > Total states run: 3 >>> > Total run time: 37.006 s >>> > >>> > ### >>> > >>> > Does anyone have an explanation - or - a suggestion what else to try? >>> - TIA! >>> > >>> > Viktor >>> > >>> >>> This is probably: >>> >>> https://github.com/QubesOS/qubes-issues/issues/6234 >>> >>> In which case, it's a known bug, and the fix is in current-testing. >>> >> >> Thanks for the link to this issue. - I'll spend some time tomorrow >> reading it in detail & will report back here ... >> > > Yes, it looks like that this is / was most likely the reason for the > 'hickup' on my system as well. > > In the meantime the situation has changed however on my system again! > > As I did report already initially I update my system in a timely fashion - > and - continued to do so, even while waiting for an anwer / response > related to "sudo dnf update --best --allowerasing" ... > > Today two more updates related to 'fedora-32' and 'whonix-gw-15' were > performed ... > > Result: Update of template 'whonix-gw-15' succeeded immediately - and - > the partial update of 'fedora-32' succeeded after multiple 'hickups'. - > However the Qubes Updater icon is still active - but - when I perform 'sudo > dnf update' in Dom0 the system now only reports: >
> [vr@dom0 ~]$ sudo dnf update ### <- Layer-8 error ;-) - Should have > checked against [user@fedora-32] !!! > > Qubes OS Repository for Dom0 80 MB/s | 82 kB > 00:00 > Dependencies resolved. > Nothing to do. > Complete! > [vr@dom0 ~]$ > > while running the update of the 'fedora-32' template using the updater > still reports: > > Updating fedora-32 > > fedora-32: > ---------- > ID: dnf list updates --refresh >/dev/null > Function: cmd.run > Result: True > Comment: Command "dnf list updates --refresh >/dev/null" run > Started: 10:17:20.752975 > Duration: 8103.878 ms > Changes: > ---------- > pid: > 1076 > > retcode: > 0 > stderr: > stdout: > ---------- > ID: update > Function: pkg.uptodate > Result: True > Comment: Upgrade ran successfully > Started: 10:17:30.963450 > Duration: 26434.827 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: 10:17:57.398477 > Duration: 3940.383 ms > > Changes: > ---------- > pid: > 1148 > retcode: > 0 > stderr: > stdout: > > Summary for fedora-32 > ------------ > Succeeded: 3 (changed=2) > Failed: 0 > ------------ > Total states run: 3 > Total run time: 38.479 s > > FYI: If it is important & interesting, I've logged the details of each > operation & can report them here or in the issue ... > I wanted to inform you, that I was finally able to clear / deactivate the icon successfully. I did execute the command recommended by user 'tlaurion' in * https://github.com/QubesOS/qubes-issues/issues/6234#issuecomment-739998536 With kind regards, Viktor -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/91a02510-15c7-4881-835b-89ae35e008afn%40googlegroups.com.
