Comment # 14 on bug 1177395 from Chris Schaller

(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.