After selecting a results entry in the config/search dialog, the plugin tries to determine timezone and height using the geonames API. For gentoo, a username has been given at compile time, but this user has not been registered: <geonames><status message="user account not enabled to use the free webservice. Please enable it on your account page: http://www.geonames.org/manageaccount " value="10"/></geonames> Please register the user. Reproducible: Always
*Bump* This issue is still present in the latest version. The user account provided in the ebuild is still not registered, thus the plugin cannot use the geonames service. Cannot gentoo just leave it unset so that it uses the default user name, if the gentoo devs decide not to register their own? This shouldn't cause any issues as not many people will configure their plugin at the same time... From the README: INFORMATION FOR PACKAGE MAINTAINERS AND DISTRIBUTORS ========================================================================== If you're going to distribute this package, and legal concerns and principles allow you to do it, please be so kind and set the GEONAMES_USERNAME configure option for the GeoNames web service which is used for altitude and timezone detection. GeoNames requires one to register an account and limits requests on a per-hour and per-day basis to prevent misuse of their service. There are no other restrictions and registration is free, uncomplicated and takes less than a minute (https://www.geonames.org/export/web-services.html). Performing these steps will ensure automatic altitude and timezone detection are kept operational for all users of the plugin. Currently, it is no big deal and only a precaution, as there are likely not that many users setting up the plugin within the same hour and exhausting the credits. Still, if it is ok with you to register a username yourself for the users of your package, then it would certainly help should that unlikely case become true. While the user can also set this via a hidden option, the developer/maintainer of the plugin thinks the user should not be bothered with it, as every user would need to do it by default, and that would hurt user experience.
