https://bugs.gpodder.org/show_bug.cgi?id=1730
Thomas Perl <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #20 from Thomas Perl <[email protected]> --- This should fix the bug: http://gpodder.org/commit/72c028dc * Only use "ifconfig" if it's available * Only use "ip" if it's available * If neither "ifconfig" nor "ip" are available, assume we are online (because we can't prove that we're offline) * If an error happens while trying to check for the connection, assume we are online (again, because proving that we're offline failed) In edge cases where "ifconfig" shows that we're offline, but "ip" shows that we're online, the function still returns that we're online (only one command needs to return success). In general, this should make sure that all users bitten by this bug would have not had the problem with their initial setup, while still giving useful feedback to users who DO have "ifconfig" and/or "ip" installed, and who just accidentally try to update the feeds while there's no connection. -- You are receiving this mail because: You are watching all bug changes.
_______________________________________________ gPodder-Bugs mailing list [email protected] https://lists.berlios.de/mailman/listinfo/gpodder-bugs
