Bug 396484 - "machine geolite.mamind.com: host not found unknown" when I open nightly build installed via flatpak
Summary: "machine geolite.mamind.com: host not found unknown" when I open nightly buil...
Status: RESOLVED DUPLICATE of bug 403054
Alias: None
Product: ktorrent
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Joris Guisson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-13 17:32 UTC by Patrick Silva
Modified: 2019-05-27 05:27 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
screenshot taken on neon dev unstable. (67.15 KB, image/png)
2018-09-28 18:07 UTC, Patrick Silva
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Silva 2018-07-13 17:32:53 UTC
Every time I open ktorrent nightly installed via flatpak/kdeapps repo
I get the message "machine geolite.mamind.com: host not found unknown"
with "repeat" and "cancel" buttons.
It occurs on both neon dev unstable and Arch Linux.
Comment 1 Patrick Silva 2018-09-28 18:07:02 UTC
Created attachment 115300 [details]
screenshot taken on neon dev unstable.
Comment 2 Patrick Silva 2019-03-24 13:31:35 UTC
This bug persists on Arch linux.
Comment 3 Bart C 2019-05-24 17:58:24 UTC
Confirmed on Arch (fully up to date) with ktorrent 5.1.1 (KF 5.57.0).

ktorrent uses an obsoleted MaxMind GeoLite API and apparently the link does not work anymore.

GeoLite is discontinued: https://support.maxmind.com/geolite-legacy-discontinuation-notice/
GeoLite2 is to be used: https://dev.maxmind.com/geoip/geoip2/geolite2/

The APIs are not compatible with each other requiring changes to the way ktorrent uses the data and how it shows the flags. As the compressed GeoLite database file format also has changed (from .gz to .tar.gz), also the decompression routine needs an update (a quick look shows that KCompressionDevice does not handle these tarballs directly)
Comment 4 Wolfgang Bauer 2019-05-25 21:11:55 UTC
Isn't this basically the same as bug#403054?

This should fix it:
https://phabricator.kde.org/D21145
Comment 5 Bart C 2019-05-27 05:27:46 UTC
Yes it is

*** This bug has been marked as a duplicate of bug 403054 ***