Comment # 9 on bug 955233 from Wolfgang Bauer

(In reply to Wolfgang Bauer from comment #8)
> For the record, I cannot reproduce the problem here. Neither on 13.2 nor on
> Leap 42.1, neither with Wicked nor with NetworkManager.

Well, I actually was able to reproduce the problem now, by disabling automatic
connection in NetworkManager and connecting manually after login.

Of course in this case, the network is indeed "offline" when the update applet
is "started" (together with the desktop).
The applet takes this state from packagekitd.
When the network is activated, packagekitd is supposed to notice that and tell
the applet that the state has changed.

BUT: in openSUSE, packagekitd shuts itself down after 15 deconds of idleness,
to not block YaST/zypper forever.
As it is not running, it of course cannot notice the network becoming online,
and cannot notify the applet.

Running pkcon manually explicitly starts packagekitd, which then notifies the
applet that the system is online.

So all in all this is again related to Bug#899755...

Not sure what we can do to fix that though.
If the applet would poll packagekitd (i.e. restart it) regularly all the time,
people will complain as well I suppose, and it would somehow defeat the purpose
of packagekitd shutting itself down.

Maybe it would be enough if it would show the "Check for updates" button even
in case it is offline? Users would at least be able to "turn it on" again.
Or maybe we should just disable that check for being online/offline in the
applet.
Personally I'd go with the second approach I think (that's also Appers behavior
if I am not mistaken). Displaying "Network offline" by the updater isn't
probably very interesting for the user anyway. If there are no updates to be
installed, there are no updates to be installed, period.

Opinions are welcome of course.