[4.0.1.48] Notification for available system update to Koli can't be removed

Bug Reports
#1

REPRODUCIBILITY (% or how often): persistent
BUILD ID = OS VERSION (Settings > About product): 4.0.1.48
HARDWARE (XA2, Xperia 10…): XA2 Ultra
UI LANGUAGE: German
REGRESSION: (compared to previous public release: Yes, No, ?): 3.4.0.24

DESCRIPTION:

The notification for the available system update to Koli is shown permanently in the events view. It has no delete UI element and is not impacted by delete all.

PRECONDITIONS:

STEPS TO REPRODUCE:

  1. go to events view
  2. see system updata available
  3. does not vanish when using delete all

EXPECTED RESULT:

notification vanishes

ACTUAL RESULT:

notification persists

ADDITIONAL INFORMATION:

(Please ALWAYS attach relevant data such as logs, screenshots, etc…)

#2

Did you trigger the OS update to 4.0.1.48 from the UI or from the CLI?

#3

from the User Interface

#4

Wait a day.
Press the notification.
Select check for update in the pulldown menu.
It disappears.

#5

@davidrasch:

Sailfish Events view shows a notification on available Sailfish OS updates. This notification should vanish on a successful installation of the OS update. If it persists in the Events view, the following procedure should remove it:

  • Enable the Developer mode (if not done previously). See this help article .
  • Open Terminal app
  • Give the command

rm /home/defaultuser/.cache/sailfish-osupdateservice/os-info

or

rm /home/nemo/.cache/sailfish-osupdateservice/os-info

depending on the admin username of your phone.

  • Finally, go to “Settings > System > Sailfish OS updates” and pull down “Check for updates”

This should do the trick.

1 Like
#6

@svalmont 's method worked on my Jolla C.

1 Like
#7

Would it not be nice to have an env var set for this? So one could also look for this to know which version was flashed and so which is the admin name (nemo on devices with flashed image <3.3, defaultuser for >=3.3).

#8

I didn’t have to wait for a day, worked right away for me.

1 Like
#9

Thanks to all of you, the approach suggested by @svalmont did the trick for me.

1 Like
#10

Same here, this trick worked for me too (Xperia X)

1 Like