Source: gnome-software Followup-For: Bug #909804 Hi,
I am seeing what looks like this behaviour on a X230 with 4G RAM, most often on resuming from suspend (I presume because the update job gets delayed while the system is suspended and gets kicked of by systemd at resume). Said machine is currently sitting next to me on the desk, completely unresponsive (imobile mouse, apparently unable to negotiate WPA) and I'm leaving it to see if it manages to got over the problem or just needs a power-cycle. The disk activity LED is on solid. It was responding to pings over WiFi for a while, but no longer. My suspicion is that this occurs if one has a reasonable amount of swap already in use when suspending. IIRC both Firefox and DrRacket were running on this machine when it was suspended, which between them eat all the RAM. If you can tell me how to provoke gnome-software into attempting an update in 10 minutes time, say, such that it will try it on resume if I wait till after that time, then I'll be able to do that, suspend the machine, and perhaps be able to provide you with a recipe for reporoducing the issue. BTW I suspected it was gnome-software (or something in it's circle) that was causing this when I noticed it about a year ago, so deinstalled that and IIRC packagekit, and the problem went away -- it seems that I installed/upgraded something recently that pulled them back in, and the problem is back. When the machine is behaing itself I can probably give you versions and dates (they ought to be recorded in etckeeper) Cheers, Phil.
