Ubuntu
snapd package

[snap] refresh message poses UI problem

Bug #1979140 reported by udippel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snapd (Ubuntu)
New
Undecided
Unassigned

Bug Description

Recently, like suggested in one of the bug report, Chromium pops up a notification that with a couple of (given) days, the current session must be closed, or could experience errors.
Now, this IS a bore, because my users all tell me about this, and they, just as myself, DID close and restart, and nothing changed; still the same. apt-get update && apt-get upgrade wouldn't help.
Now, for the sysadmin this is plain crxx; because the users are seriously worried.

The workaround is a snap refresh. Okay, simple. But cumbersome for the users and their admin. It just ought not happen, I think.

Adolfo Jayme Barrientos (fitojb)
affects: chromium-browser (Ubuntu) → snapd (Ubuntu)
Changed in snapd (Ubuntu):
status: New → Opinion
Revision history for this message
Adolfo Jayme Barrientos (fitojb) wrote :

See https://forum.snapcraft.io/t/wip-refresh-app-awareness/10736/26 for context.

You are notified to restart the application after it’s refreshed because, previously, the profile could get corrupted. The notification can be disabled, too.

Revision history for this message
udippel (udippel) wrote :

I'd call it a minor bug. If you have dozens of users, they'll be unhappy, and some file tickets.
What's worse: following the text, restart, won't help. Following the text and sudo update && sudo upgrade won't work either.
You can't expect your users to go to the dreaded command line and issue some 'gibberish' commands.

My 2 cents

Revision history for this message
Olivier Tilloy (osomon) wrote :

At this point there is wide consensus that this user experience isn't great, because the notification suggests that closing the application will automatically refresh it, but it doesn't.

The snapd team is fully aware of this shortcoming, in fact they reverted the feature a few weeks ago (https://github.com/snapcore/snapd/commit/5d02bb9c5ada7ce3e07d56ecb3d81aaf821df385), but backed off the revert again out of timing concerns (with the upcoming release of Ubuntu 22.04.1).

I don't know if they're already tracking the issue somewhere else. If not, this bug would be a good entry point.

Changed in snapd (Ubuntu):
status: Opinion → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.