[Bug 1005495] New: Repetitive Update notification after an offline update was done
http://bugzilla.opensuse.org/show_bug.cgi?id=1005495 Bug ID: 1005495 Summary: Repetitive Update notification after an offline update was done Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome@forge.provo.novell.com Reporter: dimstar@opensuse.org QA Contact: qa-bugs@suse.de CC: dimstar@opensuse.org, fezhang@suse.com, mgorse@suse.com, sckang@suse.com, sreeves@suse.com, yfjiang@suse.com, zaitor@opensuse.org Depends on: 1004343 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1004343 +++ After a successful system update using the offline update mechanism (gnome-software or packagekit directly triggered) the system pops up a notification about the successful state of this update. Nothing clears out the file responsible to trigger this and on next boot, the notification happens again, even without any further updates happening. This all happens due to us backporting logic for the online update mechanism in gnome-settings-daemon, but we lack to backport the feature that cleans up the stale info file after a notification was done. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1005495
http://bugzilla.opensuse.org/show_bug.cgi?id=1005495#c2
--- Comment #2 from Dominique Leuenberger
what offline updates? that feature should be disabled.
I disagree - the feature is nested deep into systemd/packagekit/gnome-software and should remain. What we did is implement for the DEFAULT gnome update notification to NOT be the offline update method; but breaking the feature completely is definitively not what we should aim for. This bug is only about the fact that if somebody triggered it manually (and this explicitly), the notification log is not being cleaned after the user was notified - resulting in a notification at every boot (this does not happen if the user only follows the notifications given by the system to perform the regular online update) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1005495
Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=1005495
http://bugzilla.opensuse.org/show_bug.cgi?id=1005495#c3
--- Comment #3 from Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=1005495
http://bugzilla.opensuse.org/show_bug.cgi?id=1005495#c5
--- Comment #5 from Dominique Leuenberger
Fix is generated as SR to GNOME:STABLE:3.20. Here is the link:
The fact that PK would install files into /usr/lib/gnome-settings-daemon-3.0 makes this a very strange patch on top of PK -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1005495
http://bugzilla.opensuse.org/show_bug.cgi?id=1005495#c6
--- Comment #6 from Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=1005495
http://bugzilla.opensuse.org/show_bug.cgi?id=1005495#c9
--- Comment #9 from Dominique Leuenberger
Is it *really* too difficult to integrate this into g-s-d to make the patch there self-contained without going across multiple packages?
I created https://build.opensuse.org/request/show/439062 as a base for discussion. The entire logic is now contained into that one patch in g-s-d and we do not risk losing parts of it... It installs pk-clear-offline-update to /usr/lib/gnome-settings-daemon-3.0/ as all other binaries in libexecdir for g-s-d -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com