Not sure if this might be of help to anyone who updates to KDE 4.14.0
On updating and reboot I lost my internet (wireless) connection.
I noticed network manager looked different and my wireless connection was showing as connected but I was unable to view any content in browser, thunderbird, skype etc.
What I did was delete my wireless connection and established a new connection to the same router and I was up and running again.
Not sure what has caused it - only speculating that it was the network manager update.
Probably. You can of course also just revert back to the old networkmanagement applet, by installing “plasmoid-networkmanagement” again (and uninstall “plasma-nm”).
And there should not be a problem with “system-connections” as they are stored by NetworkManager itself, so the frontend does not matter.
That said, an update should not switch to the “new” (well, it’s not really that new any more, an older version is even included in standard 13.1 already) plasma-nm automatically.
How did you update to 4.14?
Probably you manually selected to install “plasma-nm”?
I upgraded to the 4.14 in [noparse]KDE:Distro:Factory[/noparse] 3 weeks ago (with “zypper dup” even), and back to KDE:Current now, and I did not get plasma-nm (and of course also had no problem with my wireless connection… ).
So I don’t see any change there regarding the 4.14 update.
Maybe one of your versions isn’t configured to store network connections (and passwords) in a db (which is default)?
If NM is configured to read data directly from wpa_supplicant.conf, I can see that file possibly being replaced during a package upgrade.
Or, if something happened to the db… (look at the file creation data)
I’ve been using plasma-nm for as long as I can remember - this was merely just a version upgrade from that included with KDE 4.13 to 4.14 of which there appears to be some differences (at least visually).
Maybe one of your versions isn’t configured to store network connections (and passwords) in a db (which is default)?
If NM is configured to read data directly from wpa_supplicant.conf, I can see that file possibly being replaced during a package upgrade.
No change from default here so should be saving passwords etc to the default db.
Today I’m not entirely sure that my issues was related to the network manager update.
My isp has been in the news this morning as having had some connectivity issues over the past 24 hours.
After the update I could browse my local network no problem but anything outside of my local network was unavailable. The reason I thought the update was the cause was that I could still browse the internet using the same network from my phone and conectivity on the openSUSE machine returned after establishing a new connection - but it seems that may have just been conicidence as I have had some sporadic outages since then.
I think I’ll just keep an eye on things for the next day or two.
I’ve been using the KDE Current repo since it has existed (I forget - between four to eight moths ago I guess)
KDE 2.14 has been available in that repo since Sept 03 and I just did an “update all if newer version available” in yast
I’ve been using the KDE Current repo since it has existed (I forget - between four to eight moths ago I guess)
KDE 2.14 has been available in that repo since Sept 03 and I just did an “update all if newer version available” in yast (on that specific repo and KDE Extra)
Well, I mainly asked because I thought a switch to plasma-nm caused your problems now.
The way you updated cannot cause a switch to plasma-nm though, as already mentioned.
But since you used plasma-nm before already, this is all moot now anyway.
Ok, there might have been changes in plasma-nm’s Interface. It is still in active development.
But I don’t think it can have caused your problems.
In the end it’s NetworkManager that makes the connection (and some lower-level stuff is involved as well of course).
But none of that is in KDE:Current, and none of that could therefore have been changed by the KDE Update to 4.14.
And if there would have been a problem with the password, the connection should not have been shown as “connected”.
In particular this statement of yours:
mostly rules out any problem on your system anyway IMHO (be it with NetworkManager, plasma-nm, the password, or whatever).
So I think the most probable reason would really be problems with your ISP or router.
yep - switched to use google’s DNS this morning and things have been very stable since.
I’ve been using the KDE Current repo since it has existed (I forget - between four to eight moths ago I guess) KDE 2.14 has been available in that repo since Sept 03 and I just did an “update all if newer version available” in yast (on that specific repo and KDE Extra)
).