http://bugzilla.opensuse.org/show_bug.cgi?id=1128358 http://bugzilla.opensuse.org/show_bug.cgi?id=1128358#c5 Dennis Irrgang changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED CC| |me@dennis-irrgang.com --- Comment #5 from Dennis Irrgang --- I can confirm this bug after a rather lengthy wild goose chase. I upgraded TW from 2019-07-18 to 2019-07-30, which happened to coincide with me finally adding flatpak.Slack and flatpak.Telegram to autostart. Next day I boot up my system and - none of my flatpak apps are able to reach the internet anymore. Coincidentally (?) Discover displayed the same problems, which lead me to believe it is something both flatpak and discover use to verify connectivity. However on dbus NM is correctly returning NM_CONNECTIVITY_FULL, putting me back to square one. Eventually I found this bug report and lo and behold - @dario.tislar@gmail.com 's workaround does indeed work! Now that I started to understand the timeline I wondered what part Slack plays in all this. Rolling back via snapper to the previous state (flatpak apps once more not having connectivity) I removed flatpak.slack and flatpak.telegram (thus all flatpak apps) from the autostart - and now it works as well! It seems like something breaks horribly when Slack (or any other flatpak app?) tries to access the internet prior to NM having established a connection. Part of the problem may be that after login I need to enter my wallet password, which results in the connection to the wifi to be delayed. I assume this may have something to do with this. -- You are receiving this mail because: You are on the CC list for the bug.