This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
client:bugs [2018/03/17 06:58] karl [GTK-v1] add entry for version 1.9.1 |
client:bugs [2018/03/18 04:54] (current) karl [GTK-v2] Add content about no internet connection |
||
---|---|---|---|
Line 14: | Line 14: | ||
See also : [[:known_client_issues#Client freezes]] | See also : [[:known_client_issues#Client freezes]] | ||
====== GTK-v2 ====== | ====== GTK-v2 ====== | ||
+ | ===== Server listing does not show ===== | ||
+ | |||
+ | ==== Reason : No internet connection. ==== | ||
+ | |||
+ | Affected versions : 1.11.0 and 1.12.0 | ||
+ | |||
+ | Explanation : \\ | ||
+ | When the client starts, it tries to look up for the [[:servers:metaservers]] , that | ||
+ | are hardcoded inside, usually at http://crossfire.real-time.com/metaserver2 . \\ | ||
+ | But this look-up fails, because the connection to the world-wide-web is not possible. | ||
+ | |||
+ | Version 1.11 of the client loops forever printing //Choosing server 0// | ||
+ | when launched inside a terminal. The '0' reads in human minds as '1' . | ||
+ | From the list of metaservers a random metaserver gets chosen. | ||
+ | But because at that time there was just one metaserver-address | ||
+ | written in the code, it will be always number '1' ( as '0' would be the first of the list ). | ||
+ | |||
+ | Version 1.12 of the client does not loop forever, but still | ||
+ | tries the metaserver list, without stopping it at a point and presenting the | ||
+ | list from the **.**[[crossfire]] / servers.cache file instead. | ||
+ | |||
+ | Version 1.50 of the client works again. But this version is affected by the | ||
+ | [[:known_client_issues#1.50.0|create character bug]] , when playing on a server of versions 1.50 and later. | ||
+ | |||
+ | ==== Reason : No internet connection and no servers.cache file ==== | ||
+ | |||
+ | Affected versions : Likely all versions of the client. | ||
+ | |||
+ | Explanation : \\ | ||
+ | When the client starts, it should present a list of servers consisting of entries | ||
+ | received by the metaserver lookup and by entries from the servers.cache file. | ||
+ | But the metaservers can not send a list, because they did not receive a request | ||
+ | and an empty or non-existent servers.cache file has no entries. | ||
+ | |||
+ | ===== Client freezes when connecting to a server ===== | ||
+ | |||
+ | Reason : No internet connection. \\ | ||
+ | |||
+ | Affected versions : 1.60.0 and 1.70.0; probably later versions. \\ | ||
+ | 1.50.0 works fine, but has the [[:known_client_issues#Impossible to create a character|create character]] bug. | ||
+ | |||
+ | Explanation : \\ | ||
+ | When the client starts, it presents a list to select a server to play on. | ||
+ | This list is a mix of servers a gamer once connected to from | ||
+ | the file **.**[[crossfire]] / servers.cache and from the list, | ||
+ | the metaserver lookup received. While the terminal gets printed an error | ||
+ | message, the failed lookup message does not reach the average user | ||
+ | being printed somewhere visible to him. \\ | ||
+ | But the user can still select from the cached entries an on-line server. \\ | ||
+ | When the client tries to connect to the chosen on-line server, | ||
+ | the client freezes forever, on Linux | ||
+ | eating up one cpu-core 100% in //- system: processes executing in kernel mode// | ||
+ | state; whatever "kernel mode" means - | ||
+ | //linux/Documentation/filesystems/proc.txt// does not tell much about it. | ||
+ | |||
+ | Termination of the client on Linux is only possible by the KILL signal, | ||
+ | all other signals fail to close the client and freeing the CPU : \\ | ||
+ | ''killall -9 crossfire-client-gtk2'' . | ||
+ | |||
===== Quit the server connection ===== | ===== Quit the server connection ===== |