Fork of GTK3 Dino with experimental features. https://gitea.privatedns.org/xavi/dino/atom?h=send-button 2022-02-01T22:37:54+00:00 2022-02-01T22:37:54+00:00 fiaxh git@lightrise.org 2022-02-01T16:38:15+00:00 urn:sha1:b7ca33a37de5dd2ecffa7575681c6009996b7ba2 related #1155 2020-11-20T14:21:34+00:00 fiaxh git@lightrise.org 2020-11-20T14:21:34+00:00 urn:sha1:11d9855a3994bc24ff67f5c2c4933c1d9559f6c5 fixes #707 2018-01-09T19:39:45+00:00 Mathieu Bridon bochecha@daitauha.fr 2018-01-09T19:39:45+00:00 urn:sha1:5557c03be87a622fa830b26e27ca6b158093937c * Move to GNetworkMonitor Dino currently talks to NetworkManager over DBus to know the state of the network. That doesn't work in a Flatpak sandbox by default though, because Flatpak filters DBus communications and only allows a very small set of things to pass (which are known to be safe). Gio provides an API to know the state of the network (and be notified of changes via a signal): GNetworkMonitor. And GNetworkMonitor works both inside a Flatpak sandbox, and in traditional builds. (in Flatpak it uses what we call a "portal", which are the clean, safe way to let apps exit their sandbox) Fixes #235 * Don't check for network connectivity for now The connectivity check really is the correct thing to do: * network_available means that the computer has network routes to "somewhere". That is, it is connected to a router. * connectivity.FULL means that the computer can access "the Internet". That is, if it is behind a router, that router is connected. As a result, only checking for network_available is not correct. Unfortunately, NetworkManager tends to wait a long time before checking for connectivity. As a result, it is possible that a transient network error leaves NetworkManager thinking that network_available is true but connectivity!=FULL, and it will wait several minutes before realizing that the Internet connexion did come back. During that time, apps checking for connectivity (e.g the whole GNOME desktop) will think they don't have access to the Internet, while apps that don't (e.g Firefox) will access the Internet just fine. Users are understandably confused when that happens. Removing the check for connectivity is an acceptable trade-off in the short-term, until this situation is improved on the NetworkManager side. https://bugzilla.gnome.org/show_bug.cgi?id=792240 2017-08-25T20:30:03+00:00 fiaxh git@mx.ax.lt 2017-08-24T21:24:04+00:00 urn:sha1:f9436b63f1f7de08f8c2c97878c183495bb3c6f6 2017-08-22T14:22:56+00:00 fiaxh git@mx.ax.lt 2017-08-21T15:16:25+00:00 urn:sha1:4a4b5956c9b12bbfb583da1794ef0184e760ac33 2017-03-10T18:50:34+00:00 Marvin W git@larma.de 2017-03-10T18:34:56+00:00 urn:sha1:29ca70a6d534e1cd79963718c793ae740318cff1