[qubes-users] Qubes updater icon never gets cleared

[vr2024]

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:

[mailinglist_bot]

It happened to me as well and is most probably an issue with the pulseaudio.

Does it happen with fedora-32 template only or is it the case for other templates too?

If only with fedora-32, try to directly open the fedora-32 template and execute:
$ sudo dnf update

If it says anything about pulseaudio, try to execute:

$ sudo dnf update --best --allowerasing

This should solve the issue.

Viktor Ransmayr:

[mailinglist_bot]

Dec 5, 2020, 11:16 by qubes-users@googlegroups.com:

It happened to me as well and is most probably an issue with the pulseaudio.

Does it happen with fedora-32 template only or is it the case for other templates too?

If only with fedora-32, try to directly open the fedora-32 template and execute:

$ sudo dnf update

If it says anything about pulseaudio, try to execute:

$ sudo dnf update --best --allowerasing

This should solve the issue.

I have the same persistent notification due to pulseaudio updates. Do you recall what packages it said it will remove when you run with --best --allowerasing.

I am told it will remove

Removing dependent packages:

• pulseaudio-qubes

• qubes-vm-recommended

Which at least the second one sounds important for qubes operation so feeling a bit cautious

[vr2024]

It happened to me as well and is most probably an issue with the
pulseaudio.

Thanks a lot for your quick feedback & suggestion!

Does it happen with fedora-32 template only or is it the case for other
templates too?

Only for fedora-32.

If only with fedora-32, try to directly open the fedora-32 template and
execute:
$ sudo dnf update

Here’s the output running that command:

[vr2024]

Thanks a lot for your answer & warning as well.

Let’s see, what the response to my other message will be …

With kind regards,

Viktor

[TheGardner1]

Worked for me! Update sign is gone at the taskbar.

Thanks a bunch Victor.

Here’s my output:

[user@fedora-32 ~]$ sudo dnf update --best --allowerasing
Last metadata expiration check: 0:11:37 ago on Sat Dec 5 20:32:06 2020.
Dependencies resolved.

[vr2024]

Worked for me! Update sign is gone at the taskbar.

Thanks a bunch Victor.

I did NOT yet perform the second part of the recommended procedure from ‘taran1s’ …

Here’s my output:

[user@fedora-32 ~]$ sudo dnf update --best --allowerasing
Last metadata expiration check: 0:11:37 ago on Sat Dec 5 20:32:06 2020.
Dependencies resolved.

Package Arch Version Repository Size

===============================================================================================================
Upgrading:

pulseaudio x86_64 14.0-1.fc32 updates 1.0 M

pulseaudio-libs x86_64 14.0-1.fc32 updates 690 k
pulseaudio-libs-glib2 x86_64 14.0-1.fc32 updates 18 k

pulseaudio-module-bluetooth x86_64 14.0-1.fc32 updates 78 k
pulseaudio-module-x11 x86_64 14.0-1.fc32 updates 31 k

pulseaudio-utils x86_64 14.0-1.fc32 updates 72 k
Removing dependent packages:
pulseaudio-qubes x86_64 4.0.31-1.fc32 @qubes-vm-r4.0-current 41 k
qubes-vm-recommended noarch 4.0.7-1.fc32 @qubes-builder-vm-r4.0-current-testing 0

Transaction Summary

Upgrade 6 Packages
Remove 2 Packages

Total download size: 1.9 M
Is this ok [y/N]: y
Downloading Packages:
(1/6): pulseaudio-libs-glib2-14.0-1.fc32.x86_64.rpm 15 kB/s | 18 kB 00:01
(2/6): pulseaudio-libs-14.0-1.fc32.x86_64.rpm 331 kB/s | 690 kB 00:02
(3/6): pulseaudio-14.0-1.fc32.x86_64.rpm 421 kB/s | 1.0 MB 00:02
(4/6): pulseaudio-module-bluetooth-14.0-1.fc32.x86_64.rpm 63 kB/s | 78 kB 00:01
(5/6): pulseaudio-module-x11-14.0-1.fc32.x86_64.rpm 76 kB/s | 31 kB 00:00
(6/6): pulseaudio-utils-14.0-1.fc32.x86_64.rpm 217 kB/s | 72 kB 00:00

Total 431 kB/s | 1.9 MB 00:04
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Upgrading : pulseaudio-libs-14.0-1.fc32.x86_64 1/14
Running scriptlet: pulseaudio-libs-14.0-1.fc32.x86_64 1/14
Running scriptlet: pulseaudio-14.0-1.fc32.x86_64 2/14
Upgrading : pulseaudio-14.0-1.fc32.x86_64 2/14
Running scriptlet: pulseaudio-14.0-1.fc32.x86_64 2/14
Upgrading : pulseaudio-utils-14.0-1.fc32.x86_64 3/14
Upgrading : pulseaudio-module-x11-14.0-1.fc32.x86_64 4/14
Upgrading : pulseaudio-module-bluetooth-14.0-1.fc32.x86_64 5/14
Upgrading : pulseaudio-libs-glib2-14.0-1.fc32.x86_64 6/14
Cleanup : pulseaudio-module-x11-13.99.1-4.fc32.x86_64 7/14
Cleanup : pulseaudio-module-bluetooth-13.99.1-4.fc32.x86_64 8/14
Cleanup : pulseaudio-utils-13.99.1-4.fc32.x86_64 9/14
Cleanup : pulseaudio-libs-glib2-13.99.1-4.fc32.x86_64 10/14
Erasing : qubes-vm-recommended-4.0.7-1.fc32.noarch 11/14
Erasing : pulseaudio-qubes-4.0.31-1.fc32.x86_64 12/14
Running scriptlet: pulseaudio-13.99.1-4.fc32.x86_64 13/14
Cleanup : pulseaudio-13.99.1-4.fc32.x86_64 13/14
Cleanup : pulseaudio-libs-13.99.1-4.fc32.x86_64 14/14
Running scriptlet: pulseaudio-14.0-1.fc32.x86_64 14/14
Running scriptlet: pulseaudio-libs-13.99.1-4.fc32.x86_64 14/14
Verifying : pulseaudio-14.0-1.fc32.x86_64 1/14
Verifying : pulseaudio-13.99.1-4.fc32.x86_64 2/14
Verifying : pulseaudio-libs-14.0-1.fc32.x86_64 3/14
Verifying : pulseaudio-libs-13.99.1-4.fc32.x86_64 4/14
Verifying : pulseaudio-libs-glib2-14.0-1.fc32.x86_64 5/14
Verifying : pulseaudio-libs-glib2-13.99.1-4.fc32.x86_64 6/14
Verifying : pulseaudio-module-bluetooth-14.0-1.fc32.x86_64 7/14
Verifying : pulseaudio-module-bluetooth-13.99.1-4.fc32.x86_64 8/14
Verifying : pulseaudio-module-x11-14.0-1.fc32.x86_64 9/14
Verifying : pulseaudio-module-x11-13.99.1-4.fc32.x86_64 10/14
Verifying : pulseaudio-utils-14.0-1.fc32.x86_64 11/14
Verifying : pulseaudio-utils-13.99.1-4.fc32.x86_64 12/14
Verifying : pulseaudio-qubes-4.0.31-1.fc32.x86_64 13/14
Verifying : qubes-vm-recommended-4.0.7-1.fc32.noarch 14/14
Last metadata expiration check: 0:11:54 ago on Sat Dec 5 20:32:06 2020.
Notifying dom0 about installed applications

Upgraded:
pulseaudio-14.0-1.fc32.x86_64 pulseaudio-libs-14.0-1.fc32.x86_64
pulseaudio-libs-glib2-14.0-1.fc32.x86_64 pulseaudio-module-bluetooth-14.0-1.fc32.x86_64
pulseaudio-module-x11-14.0-1.fc32.x86_64 pulseaudio-utils-14.0-1.fc32.x86_64

Removed:

?

pulseaudio-qubes-4.0.31-1.fc32.x86_64 qubes-vm-recommended-4.0.7-1.fc32.noarch

?

Complete!

I’d still like to get a confirmation from someone closer to the source, that this is all expected / OK - and - there’s nothing to worry about. - TIA again …

With kind regards,

Viktor

[adw]

This is probably:

qubes-vm-pulseaudio dependency failed with new pulseaudio-14.0-1

In which case, it's a known bug, and the fix is in current-testing.

[vr2024]

Hello Andrew

[vr2024]

Hello Andrew, hello Community

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
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:

[vr2024]

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