Bug 2009063

Proposed as a Blocker for 35-final by Fedora user chrismurphy using the blocker tracking app because:

 Release-blocking desktops must notify the user of available updates, but must not do so when running as a live image. 
https://fedoraproject.org/wiki/Fedora_35_Final_Release_Criteria#Update_notification

Created attachment 1827494 [details]
journal log

I know you're coming here from https://pagure.io/fedora-workstation/issue/107#comment-753794, but for the purposes of keeping everything in this bug, let's confirm that it's been more than two weeks since your last update. E.g. yesterday I ran:

$ gsettings get org.gnome.software install-timesamp
1631660863

Then I fed that into DuckDuckGo to convert from Unix time to human-readable time: https://duckduckgo.com/?q=1631660863+unix+time&t=epiphany&ia=answer

And it tells me my last update was installed on "Tue Sep 14 18:07:43 2021 -0500." When was your last update?

$ gsettings get org.gnome.software install-timestamp
int64 1614618019

Translates to: GMT: Monday, March 1, 2021 5:00:19 PM
That would be about the time of the last gnome-software update (I normally do dnf updates).

One of these changes, followed by a reboot and login, results in the update notification appearing:
 gsettings set org.gnome.software check-timestamp "int64 1630458000"
 gsettings set org.gnome.software online-updates-timestamp "int64 1630458000"
 gsettings set org.gnome.software update-notification-timestamp "int64 1630458000"

1630458000 is Sep 1 2021

Last night I did a shutdown, and too quickly acknowledged the dialog which had the 'install pending updates' option checked. (Nitpick, I didn't get a shutdown but a restart instead, which I force powered off at GRUB. When asking for a shutdown, I shouldn't get restart just because there pending updates. Bug 2009353) This morning at cold boot time, the system successfully installed pending updates.

(In reply to Michael Catanzaro from comment #3)
> Then I fed that into DuckDuckGo to convert from Unix time to human-readable

If you do not want to use a website for it, then:

   $ date --date=`@1631660863`

does a similar job.

In any case, I found the flaw in the code and proposed a patch upstream [1]. Let's wait for the review of that change.

[1] https://gitlab.gnome.org/GNOME/gnome-software/-/merge_requests/1008

-4 blocker, +5 FE in https://pagure.io/fedora-qa/blocker-review/issue/485 - marking as such.

FEDORA-2021-ec19af5827 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-ec19af5827

FEDORA-2021-ec19af5827 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-ec19af5827`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-ec19af5827

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

(In reply to Fedora Update System from comment #10)
> FEDORA-2021-ec19af5827 has been submitted as an update to Fedora 35.
> https://bodhi.fedoraproject.org/updates/FEDORA-2021-ec19af5827

I can make the notifications appear with the above update when following https://fedoraproject.org/wiki/QA:Testcase_desktop_update_notification (I edited the wiki and advised to set all possibly relevant timestamp keys, which is probably overkill, but it works).

FEDORA-2021-ec19af5827 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.