I installed yesterday Opensuse Leap 42.1 on a Intel i7 desktop computer. I have a Wireless USB dongle and I set it up for my Wifi connection. I am able to perform Online Update in Yast and I can browse the internet, but the Green Shield icon named “Software updates” reports network is offline. The computer has an internal ethernet card, which is not in use (at this location I don’t have a network cable to plug in).
The system is up-to-date, because I used Online Update.
You could try to configure the wireless connection as “system connection”. It will then be connected during boot already, long before you login and the updater is started.
To do so, tick the “Allow all users to connect” option in the connection editor.
If I understood right, I have to go to Start -> Configure Desktop -> Network ->Settings. In there, my setting was “No Proxy”. I changed it to “Detect Proxy Configuration Automatically”, saved, rebooted and didn’t work. I restored it back to no proxy, still no luck.
I don’t know where to change the wireless connection to a system connection. In Yast, I went to Network Settings and I edited my Wifi Device. I selected to activate the device at boot time. Restarted the computer, the Software Updates application still believes the computer has no network. It would be nice if this application would have some identifier, such a version number, so we could downgrade it. If the other applications that use the network are happy with the settings, it has to be the Software Updates that has a bug.
I also tried changing between Wicked Service to Network Manager and it still didn’t work.
To do so, tick the “Allow all users to connect” option in the connection editor.
And I meant NetworkManager’s connection editor with that, i.e. click on the network symbol in your panel/system tray and then on the “Edit Connections” icon in the top-right corner (that’s supposing that you use Plasma5).
It would be nice if this application would have some identifier, such a version number, so we could downgrade it.
The updater applet (plasma5-pk-updates) is version 0.2, there is no downgrade.
But it actually just gets the network state from PackageKit.
If the other applications that use the network are happy with the settings, it has to be the Software Updates that has a bug.
Thanks. I changed back to Network Manager and Configure Network Connections, selected my WiFi connection, Connection Editor -> General configuration. Here I added the second tick (All users may connect to this network). The checkbox for “Automatically connect to this network when available” was already ticked. I restarted the computer, Software Updates says “Your system is offline”. I am using the same computer to post this message.
I will return to Wicked Service, which seems to work a bit better (at least yast does not complain) and I will look into PackageKit issue.
With KInfoCenter, I found out I am using Plasma v5.4.3 - which is strange, since you mentioned v5.5.4 - yesterday I run the Online update and it’s done a lot of installing and I thought the system is up do date. I will have to run again Online Update, although I have a terrible internet connection today.
It seems the latest version of Plasma, 5.5.4 has not yet been made available for update. My system reports it is up to date (and I have Plasma 5.4.3). Does anybody know how can I instruct my computer to update to Plasma 5.5.4?
No, not as official update for Leap 42.1 at least, and probably never will be.
OpenSUSE normally only provides security- and bug fixes as official updates, 5.5 is a major new (feature) release.
Does anybody know how can I instruct my computer to update to Plasma 5.5.4?
It is available in an additional repo (for Leap 42.1 too), KDE:Frameworks5. You could add that and do a full switch to it to always have the latest version.
But it would probably be better to first test whether this really is the problem here. If it is, it would be good if we could release an official update with the fix.
I’ll create a package for Leap 42.1 with this fix backported.
As you are affected by this problem, it would be nice if you could test it.
I don’t understand why Yast would not be able to connect now though. You did use NetworkManager before without problem (except for the updater saying offline), no?
And just for understanding: you do have the same problem (updater saying “offline”) with Wicked, right?
I’ve noticed this issue on my Leap 42.1 Laptop when the WLAN (Network Manager) has troubles connecting (takes time to connect).
Logging out and then (immediately) logging back in normally resolves the issue (this sequence hasn’t yet not resolved the issue).Possibly a time-out issue between the Network Manager and the Plasma5 Updater?
CLI “zypper refresh/list-patches/list-updates/patch/update” function correctly even if the Plasma5 Updater is indicating “offline”.
Not a timeout. But the updater applet is started at login (together with Plasma5). If there’s no Internet connection at that time, it of course will (correctly) be in status “offline”.
So, apparently the status is not correctly updated later, which might be a bug in the applet or PackageKit (actually the applet is just a small frontend and displays what it gets from PackageKit). Or it might be the problem with plasma-nm5 not correctly updating the network status, which should be fixed in my test package.
CLI “zypper refresh/list-patches/list-updates/patch/update” function correctly even if the Plasma5 Updater is indicating “offline”.
Yes. zypper doesn’t ask for the network status, it just tries to use the network when you run it. Like YaST2 or your Web Browser.
Also it is not running in the background, it gets started when you run it.
I beginning to wonder if simply deselecting the Updater applet in the System section of the Task Bar (need to unlock the Widgets/Mini-Programs) and then after the setting has taken effect, re-selecting the Updater applet could alleviate the short-term effects of this issue.
I’ll take a look next week.
I’d think so, yes. And maybe wait ~15 seconds for PackageKit to shut down if running before enabling it again.
Although that depends on how PackageKit exactly determines the network state or where the problem lies exactly.
Or maybe try to quit plasmashell and start it again, this would also restart plasma-nm.
Something like:
Ok, I was able to reproduce the problem now by disabling automatic connection and only connect manually later after login.
The updater applet really doesn’t notice that the network is online now.
Removing and readding it to the system tray doesn’t help.
But running “pkcon get-updates” in a Konsole “fixes” it.
My suspicion: the applet is only a frontend to PackageKit as mentioned, and it just displays packagekitd’s view of the network status.
The problem: on openSUSE, packagekitd shuts itself down after being idle for 15 seconds, to not block YaST/zypper all the time.
When packagekitd is not running, it obviously cannot detect the change of the network connection and notify the update applet. And the applet will not start packagekitd either, because it thinks there’s no internet connection.
“pkcon” does explicitly start packagekitd, which sees the “online” network and tells the applet.
Disabling the ShutdownTimeout in /etc/PackageKit/PackageKit.conf should fix the problem too I think (if not there’s another one), but then you have to kill it manually to be able to use YaST or zypper.
Yesterday I tried both the wicked service and NetworkManager and Software Updates reported the system is offline in both cases. However, at some stage something crashed (can’t remember what, maybe plasma) and after that I was able to check the Software Updates many times during the day and it confirmed that the system is up-to-date (as I updated it via Yast - Online Update). Today, after restarting the computer, Software updates reports again the system is offline. I am however, able to use Yast - Online Updates and I am updating the system as we speak.
I was able to use the internet with both Wicked Service and Network Manager, but after failing to use Software Updates with Network Manager, I switched back to Wicked Service. For no particular reason, that is my preference. I initially configured the network using Wicked Service and this was the first time I came across the message “Yous system is offline”.
I will restart the computer, as the latest updates require me to do it. Next, I’ll switch back to Network Manager and confirm that Software Updates still reports the system is offline. Then, I’ll try to install the repo for Plasma 5.5.4 and I’ll check if it works (both with Wicked Service and Network Manager) and report back.
I tried what you said and after logging back in, Software Updates reported my system is Up to date. However, when I want to check for updates, I get errors saying “Update Error - Problem connecting to a software origin. There was a (possibly temporary) problem connecting to a software origins. Please check the detailed error for further details”. At the moment, I am using NetworkManager Service and “All users may connect to this network” is ticked.
I found out that because previously I logged out and logged back in, Yast and the Terminal were not aware the network is in fact active. So, while I could use the browser to go on the net, I was unable to either run the command above and also to add a new repository or check for updates. I restarted the computer and now it works - but these are pretty serious flaws.
Now, it also happens that the Software Updates is functional (using NetworkManager). But the terminal still fails to execute the sudo command above, with the message Network is unreachable. I will try the Wicked Service, the NetworkManager does not seem to like me…