Have to restart pc to connect to a different wifi network!

[sfsdsdfdsfdsfs]

I hadn't seen the date stamps initially, I just blindly copied This is from today.

[tbg]

Does this look like it might apply to you:

[Stable Update] 2018-08-31 - Kernels, Mesa, Qemu, Nvidia, Firefox, Python, Haskell

Until now I had downgraded systemd to v239.0-2 to have Internet at home. I finally could upgrade systemd and solved the "wifi connected no Internet" issue at home. Just the upgrade was not enough. I had to configure NetworkManager to use systemd-resolved and disable DNSSEC in the latter. This issue doesn't appear in a wired connection and it started with the systemd v239.0-1 upgrade. If someone has a similar issue, I could share the configuration. The symptom of the issue: You can ping to …

When looking at your logs I was kind of scratching my head because there didn't appear to be the connection failures you'd expect.

[Stable Update] 2018-08-25 - Kernels, KDE Apps & Framework, Flatpak 1.0, Nvidia, Cleanup

@mbb: I don't if you found a solution for "wifi connected but no internet" issue. In my case, I found out was related to the DNS resolution; ping www.google.com doesn't works, but ping 8.8.8.8 does work. What it worked for me was to change NetworkManager to use systemd-resolved and disable DNSSEC in the latter. I could share the configuration, if this is the case for you.

Perhaps @jetm could describe his symptoms to see if your issues are related. The timing definitely coincides.

Systemd-resolved info on the Arch Wiki:

https://wiki.archlinux.org/index.php?title=Systemd-resolved&redirect=no

https://wiki.archlinux.org/index.php/Domain_name_resolution

Perhaps run this command to look for related errors:

journalctl -b -1 | grep  systemd-resolved