http://bugzilla.opensuse.org/show_bug.cgi?id=1177395 Yifan Jiang <yfjiang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yfjiang@suse.com Assignee|gnome-bugs@suse.de |songchuan.kang@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1177395 http://bugzilla.opensuse.org/show_bug.cgi?id=1177395#c3 --- Comment #3 from Chris Schaller <kwizzz@googlemail.com> --- Used pkmon to check for packagekit activities in the background: After resume, got 2 successful download (repository sync) messages, but gnome-software stayed quiet. Opened gnome-software; it showed that software is up to date (last checked date 2 days ago!?) Clicking on refresh ended up in endless loop. pkmon did not show anything (last entry: "daemon connected=0") -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1177395 http://bugzilla.opensuse.org/show_bug.cgi?id=1177395#c4 --- Comment #4 from Jonathan Kang <songchuan.kang@suse.com> --- (In reply to Chris Schaller from comment #2)

Did some more online investigation and found similar issues in other bug trackers: https://bugzilla.redhat.com/show_bug.cgi?id=1651817 https://gitlab.gnome.org/GNOME/gnome-software/-/issues/508 https://bugzilla.redhat.com/show_bug.cgi?id=1767453

Maybe this helps.

Please let me know if you need more information/logs from my end.

Still happens regularly on my laptop. But only in combination with suspend/resume after a couple of days (2-3 days).

What I noticed was that packagekit throws DNS related errors in its log. Looks like packagekit tries name lookup of repos online before network is back.

Would you please attach these logs here? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1177395 http://bugzilla.opensuse.org/show_bug.cgi?id=1177395#c6 --- Comment #6 from Chris Schaller <kwizzz@googlemail.com> --- Opened laptop lid this afternoon (2020-10-23) Confirmed that there are updates available via `zypper lu`. But in Gnome, no message was displayed that new software is available. .................. chris@linux:~> dconf dump /org/gnome/software/ | awk '$2 ~ /[0-9]/ {print $1, strftime("%c", $2);next} {print $0}' [/] check-timestamp=int64 Thu 22 Oct 2020 09:57:16 AM CEST first-run=false online-updates-timestamp=int64 Tue 20 Oct 2020 09:55:29 AM CEST .................. pkmon log attached. journalctl output attached. Then I started gnome-software: * clicking on list of repositories => empty popup window, no repository displayed * clicking on Updates => "Software is up to date. Last checked Yesterday 9:57"; clicking on Refresh => rotating circle is shown, but no change; gave up after 15 minutes no changes During that: there were no more updates from pkmon, nothing in journal. Performed a reboot, then started gnome-software. gnome-software showed 2 updates available under Updates tab. Strangely enough, gnome-software did not start Package Updater, but instead fell back to "normal" behavior: first the Download button, then Restart and Install button is shown. Restart and Install did not work. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1177395 http://bugzilla.opensuse.org/show_bug.cgi?id=1177395#c8 --- Comment #8 from Chris Schaller <kwizzz@googlemail.com> --- Created attachment 842972 --> http://bugzilla.opensuse.org/attachment.cgi?id=842972&action=edit output of journalctl -S 2020-10-23 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1177395 http://bugzilla.opensuse.org/show_bug.cgi?id=1177395#c10 --- Comment #10 from Chris Schaller <kwizzz@googlemail.com> --- Regarding the lookup errors: sorry, got confused by my other system running Fedora 32. It has also gnome-software update issues, but different in nature. For sake of completeness: On F32, after resuming, transaction `refresh-cache` fails due to name resolving issues (probably related to network coming back too slowly), thus fooling gnome-software to think that there are no updates available. Logs look like this: ..................................... Oct 25 12:24:49 linux.fritz.box PackageKit[1838]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0) Oct 25 12:24:49 linux.fritz.box PackageKit[1838]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh Oct 25 12:24:50 localhost.localdomain packagekitd[1838]: LRO_METALINKURL processing failed: Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-cisco-openh264-32&arch=x86_64 [Could not re> Oct 25 12:24:51 localhost.localdomain packagekitd[1838]: LRO_METALINKURL processing failed: Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-32&arch=x86_64 [Could not resolve h> Oct 25 12:24:51 localhost.localdomain packagekitd[1838]: LRO_METALINKURL processing failed: Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=updates-released-modular-f32&arch=x86_64 [Could no> Oct 25 12:24:51 localhost.localdomain packagekitd[1838]: LRO_METALINKURL processing failed: Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=updates-released-f32&arch=x86_64 [Could not resolv> Oct 25 12:24:51 localhost.localdomain packagekitd[1838]: LRO_METALINKURL processing failed: Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-32&arch=x86_64 [Could not resolve host: mir> Oct 25 12:24:52 localhost.localdomain packagekitd[1838]: LRO_METALINKURL processing failed: Curl error (6): Couldn't resolve host name for https://mirrors.rpmfusion.org/metalink?repo=free-fedora-updates-released-32&arch=x86_64 [Could not> Oct 25 12:24:52 localhost.localdomain packagekitd[1838]: LRO_METALINKURL processing failed: Curl error (6): Couldn't resolve host name for https://mirrors.rpmfusion.org/metalink?repo=free-fedora-32&arch=x86_64 [Could not resolve host: mi> Oct 25 12:24:52 localhost.localdomain packagekitd[1838]: LRO_METALINKURL processing failed: Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-cisco-openh264-32&arch=x86_64 [Could not re> Oct 25 12:24:52 localhost.localdomain packagekitd[1838]: Skipping refresh of fedora-cisco-openh264: cannot update repo 'fedora-cisco-openh264': Cannot prepare internal mirrorlist: Curl error (6): Couldn't resolve host name for https://mi> Oct 25 12:24:52 localhost.localdomain packagekitd[1838]: LRO_METALINKURL processing failed: Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-32&arch=x86_64 [Could not resolve h> Oct 25 12:24:52 localhost.localdomain PackageKit[1838]: refresh-cache transaction /595_ccceecce from uid 1000 finished with failed after 2530ms Oct 25 12:24:55 localhost.localdomain PackageKit[1838]: get-updates transaction /596_acbdbdad from uid 1000 finished with success after 3058ms Oct 25 12:25:07 linux.fritz.box PackageKit[1838]: resolve transaction /597_deacbbce from uid 1000 finished with success after 2201ms ..................................... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1177395 http://bugzilla.opensuse.org/show_bug.cgi?id=1177395#c12 --- Comment #12 from Chris Schaller <kwizzz@googlemail.com> --- During the last days I noticed that this behaviour also happens after a reboot. So not directly related to suspend/hibernate. However, I noticed that gnome-software always goes defunct whenever new patches are available. Like it's choking on new data to process. Starting Package Updater manually always works. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1177395 http://bugzilla.opensuse.org/show_bug.cgi?id=1177395#c14 --- Comment #14 from Chris Schaller <kwizzz@googlemail.com> --- (In reply to Jonathan Kang from comment #13)

I don't find anything particularly wrong in the logs. PackageKit did finish a few transactions(refresh-cache, get-updates) when GNOME Software is starting up in the background.

Somehow PackageKit quits after idling for 300-ish seconds. I remember that should be 15. Can you show the content of your /etc/PackageKit/PackageKit.conf?

That files is untouched: ................................ chris@linux:~> more /etc/PackageKit/PackageKit.conf # Only the system administrator should modify this file, ordinary users # should not have to change anything. [Daemon] # Default backends, as chosen in the configure script. This will be used # where no --backend="foo" option is given to the daemon. # # The order they are specified is the order they are tried, so for the # value "foo,bar" first "foo" will be attempted and then "bar" if the # libpk_backend_foo.so module load failed. #DefaultBackend=auto # Unlock the backend after this many seconds idle. #BackendShutdownTimeout=5 # Shut down the daemon after this many seconds idle. 0 means don't shutdown. #ShutdownTimeout=300 # # for openSUSE, we want this shorter so it does not interfere with zypp/yast all the time # until boo#899755 is fixed (in fact it's a libzypp issue, NOT a PK issue) ShutdownTimeout=15 # Keep the packages after they have been downloaded #KeepCache=false ................................ Had my laptop running for 2 days (no suspend/resume) and no issues with gnome-software. On both days I received an update notification. Looks like a race condition / lockup when suspending/resuming or freshly booting. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1177395 http://bugzilla.opensuse.org/show_bug.cgi?id=1177395#c16 --- Comment #16 from Chris Schaller <kwizzz@googlemail.com> --- How to reproduce: * start gnome-software (gs) * click on repo list * close gs * close laptop lid * wait for the next day and repeat * after repeating for some days, gs and packagekit loosing connection with each other: - repo list window stays empty with twisting circle - same goes for update checks What I tried so far: * used LAN instead of WLAN => no difference * removed repos for fwupd and gnome extensions (exclusively used in gs) => no change * instead of waiting for the next day (assuming that this is related to gs looking for updates), I set the last-checked timestamp in dconf to 0 => could not force a lock up; maybe because packagekit is refusing to check again? I figured out to enable verbose loging for packagekit. Attached is the log of journalctl, pkmon, and gs, all merged together and annotated by what I was doing or was happening (starting with ###). * 2020-11-12 showed good behaviour * 2020-11-13 the issue came back (some weird entries in the log file: cancelling running background transaction, Cancel not supported by backend, plugin .* did not return error with cancellable set) * 2020-11-14 once messed up, only way to go back to normal operation is to kill and restart gnome-software -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1177395 http://bugzilla.opensuse.org/show_bug.cgi?id=1177395#c20 --- Comment #20 from Chris Schaller <kwizzz@googlemail.com> --- Created attachment 844614 --> http://bugzilla.opensuse.org/attachment.cgi?id=844614&action=edit Log Collection Script Updated script to ensure that packagekit is still running with --verbose. Added dbus-monitor output to log file. Ensuring to kill all started background processing when script ends. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1177395 http://bugzilla.opensuse.org/show_bug.cgi?id=1177395#c22 --- Comment #22 from Jonathan Kang <songchuan.kang@suse.com> --- I reported this upstream as it's also happening in the latest GNOME Software. @Chris Could you try this[0] out and see if it makes any difference? I'm using this for two days and so far so good. But sometimes it might take a bit longer to reproduce this. *[0] https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1118#note_998952 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1177395 http://bugzilla.opensuse.org/show_bug.cgi?id=1177395#c24 --- Comment #24 from Chris Schaller <kwizzz@googlemail.com> --- Wait a moment. Shouldn't GNOME_SOFTWARE_PLUGINS_BLOCKLIST=fwupd disable fwupd? gnome-software still lists the plugin as enabled: chris@linux:~/gs-issues> pkill gnome-software; GNOME_SOFTWARE_PLUGINS_BLOCKLIST=fwupd gnome-software 17:00:26:0724 Gs enabled plugins: desktop-categories, fwupd, os-release, packagekit, packagekit-local, packagekit-offline, packagekit-proxy, packagekit-refine-repos, packagekit-refresh, packagekit-upgrade, packagekit-url-to-app, shell-extensions, appstream, desktop-menu-path, flatpak, hardcoded-blacklist, hardcoded-featured, hardcoded-popular, modalias, packagekit-refine, rewrite-resource, odrs, packagekit-history, provenance, systemd-updates, generic-updates, provenance-license, icons, key-colors, key-colors-metadata 17:00:26:0724 Gs disabled plugins: dpkg, dummy, fedora-pkgdb-collections, fedora_langpacks, repos, epiphany fwupd also shows up in my logs. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1177395 http://bugzilla.opensuse.org/show_bug.cgi?id=1177395#c26 --- Comment #26 from Chris Schaller <kwizzz@googlemail.com> --- (In reply to Jonathan Kang from comment #25)

(In reply to Chris Schaller from comment #24)

...

Wait a moment. Shouldn't GNOME_SOFTWARE_PLUGINS_BLOCKLIST=fwupd disable fwupd?

gnome-software still lists the plugin as enabled:

chris@linux:~/gs-issues> pkill gnome-software; GNOME_SOFTWARE_PLUGINS_BLOCKLIST=fwupd gnome-software 17:00:26:0724 Gs enabled plugins: desktop-categories, fwupd, os-release, packagekit, packagekit-local, packagekit-offline, packagekit-proxy, packagekit-refine-repos, packagekit-refresh, packagekit-upgrade, packagekit-url-to-app, shell-extensions, appstream, desktop-menu-path, flatpak, hardcoded-blacklist, hardcoded-featured, hardcoded-popular, modalias, packagekit-refine, rewrite-resource, odrs, packagekit-history, provenance, systemd-updates, generic-updates, provenance-license, icons, key-colors, key-colors-metadata 17:00:26:0724 Gs disabled plugins: dpkg, dummy, fedora-pkgdb-collections, fedora_langpacks, repos, epiphany

fwupd also shows up in my logs.

That's weird. I added `GNOME_SOFTWARE_PLUGINS_BLOCKLIST=fwupd` to collect.sh, and it shows fwupd as disabled plugin.

Did you try this on Leap 15.2? I confirmed with two Leap 15.2 installations that the GNOME_SOFTWARE_PLUGINS_BLOCKLIST is getting ignored on both. Whereas on my Tumbleweed system it got respected. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1177395 http://bugzilla.opensuse.org/show_bug.cgi?id=1177395#c28 --- Comment #28 from Chris Schaller <kwizzz@googlemail.com> --- Created attachment 845330 --> http://bugzilla.opensuse.org/attachment.cgi?id=845330&action=edit Log File with fwupd Disabled in gnome-software Successfully disabled fwupd in gnome-software (using GNOME_SOFTWARE_PLUGINS_BLACKLIST on Leap 15.2), but still the issue is coming up. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1177395 http://bugzilla.opensuse.org/show_bug.cgi?id=1177395#c30 --- Comment #30 from Chris Schaller <kwizzz@googlemail.com> --- (In reply to Jonathan Kang from comment #29)

(In reply to Chris Schaller from comment #28)

...

Created attachment 845330 [details] Log File with fwupd Disabled in gnome-software

Successfully disabled fwupd in gnome-software (using GNOME_SOFTWARE_PLUGINS_BLACKLIST on Leap 15.2), but still the issue is coming up.

Did you manage to reproduce this in Tumbleweed with GNOME_SOFTWARE_PLUGINS_BLOCKLIST=fwupd added?

Tried in Tumbleweed: chris@linux-ls9h:~> GNOME_SOFTWARE_PLUGINS_BLOCKLIST=fwupd gnome-software 16:49:37:0002 Gs plugin appstream took 1.3 seconds to do setup 16:49:37:0027 Gs enabled plugins: desktop-categories, os-release, packagekit, packagekit-local, packagekit-offline, packagekit-proxy, packagekit-refine-repos, packagekit-refresh, packagekit-upgrade, packagekit-url-to-app, appstream, desktop-menu-path, flatpak, hardcoded-blocklist, hardcoded-popular, modalias, packagekit-refine, rewrite-resource, malcontent, odrs, packagekit-history, provenance, systemd-updates, generic-updates, provenance-license, icons, key-colors, key-colors-metadata 16:49:37:0027 Gs disabled plugins: dpkg, dummy, fedora-langpacks, fedora-pkgdb-collections, fwupd, repos Again, gs got stuck. Let me know if you need the logs from this one, too. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1177395 http://bugzilla.opensuse.org/show_bug.cgi?id=1177395#c32 --- Comment #32 from Jonathan Kang <songchuan.kang@suse.com> --- a potential is available in latest tumbleweed now. Please test if this can still be reproduced. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1177395 http://bugzilla.opensuse.org/show_bug.cgi?id=1177395#c34 --- Comment #34 from Chris Schaller <kwizzz@googlemail.com> --- Looks like I found the reason for this issue. It is related to IPv6. After disabling IPv6, gnome-software does its job. Added comment on gnome's gitlab. -- You are receiving this mail because: You are on the CC list for the bug.