known_client_issues
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| known_client_issues [2018/03/18 04:44] – [Impossible to create a character] Add internal link to section 1.50.0 of this page karl | known_client_issues [2024/05/20 17:52] (current) – Client issues are tracked at SourceForge, removing known_client_issues page leaf | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Known Client Issues ====== | ||
| - | ===== All Versions ===== | ||
| - | In case you don't get a metaserver list: | ||
| - | * If you're using ISDN or DSL verify that your MTU is 1492, not 1500. | ||
| - | * Do not use a nameserver of Deutsche Telekom or T-Online. | ||
| - | |||
| - | ===== Unspecified/ | ||
| - | ==== New Client with Old HOME folder ==== | ||
| - | //March, 2011.// | ||
| - | Launching a trunk gtk-v2 client **(1.60.0+)** with an old user's **.**[[: | ||
| - | Renaming the .crossfire folder resolved the issue. \\ | ||
| - | Full diagnosis of the root cause has not been done. | ||
| - | ==== Client freezes ==== | ||
| - | // | ||
| - | If you apply a bed of reality, hit q to quit, and something else, especially a keybind, in very quick succession, the client freezes up (at least on **Linux**). \\ | ||
| - | '' | ||
| - | It appears that the client keeps trying to do socket operations to send the commands to the now disconnected server. | ||
| - | In past experience, _ _kernel_vsyscall can hang for about 4 minutes on Linux before it returns, still, after many, many minutes, the client does not die. mwedel suggested a possible setting for the socket that might help. \\ | ||
| - | It looks like the client is very hard to kill if you do not have **xkill** or know how to go to a console to kill it, so this is a very unfriendly behavior. | ||
| - | |||
| - | EDIT March 2018 : | ||
| - | kill -SIGHUP or kill -1 is not the best way to kill something. \\ | ||
| - | kill -SIGKILL or kill -9 should kill any userspace program. | ||
| - | |||
| - | ==== Window frame X close button on Popups ==== | ||
| - | //August, 2010.// \\ | ||
| - | The GTK-V2 client design specifies that various dialogs (spell, skills, config, etc) should not be drawn with the X close icon on the window frame. \\ | ||
| - | This works for various window managers, but appears not to work under the default **LXDE** configuration on Mandriva 2010 Spring. \\ | ||
| - | Another report said that it did not work under **KDE 3.5.10** when kde-window-decorator was in use, though KDE is generally considered to not have this issue. \\ | ||
| - | In any event, if X close icons appear on client dialogs, **DO NOT dismiss them with the X icon** . \\ | ||
| - | This deletes the dialog and requires a client restart to show it again. \\ | ||
| - | Use the Close button, on the lower button bar, to dismiss all client dialogs. | ||
| - | * This is fixed in SVN as of 2010/08/19. | ||
| - | | ||
| - | ==== Themes do not work ==== | ||
| - | //~August, 2010 and earlier. // \\ | ||
| - | Various reports indicate that crossfire-client-gtk2 themes (colored text/spell window) no longer worked on some distributions when the client is launched from a user account. \\ | ||
| - | Workarounds were found. All of them essentially launch the client like this: '' | ||
| - | In at least one instance of non-working themes, GTK_MODULES was set to '' | ||
| - | It appears some theme engines are not compatible with crossfire-client-gtk2 theme code. \\ | ||
| - | It is not yet known whether there is a way to alter the client so that its themes work properly without regard to the system GTK theme engine setting. | ||
| - | |||
| - | ==== Impossible to create a character ==== | ||
| - | //~July, 2010.// \\ | ||
| - | The GTK-V2 client with account-based login support has a bug in a character create button that makes it impossible to set up a character. \\ | ||
| - | It is thought this bug is in **1.50** . Current [[: | ||
| - | |||
| - | See also further down [[# | ||
| - | |||
| - | ==== Player communication broken ==== | ||
| - | |||
| - | Various reports of broken chat/ | ||
| - | * Meflin reports 1.11 clients on trunk server: chat/say does not work. It is not known if this is widely experienced or not. Fedora is still on 1.11 (and is what was in use regarding this report). | ||
| - | * Invidious user report via Meflin is for Debian Stable 5.0.4 and current GTK V2 Unix Client 1.50.0.dev-r13535M (using gtk-v2.glade) chat. Say and shout do work. | ||
| - | * Kero has an issue of this nature, but details are not recorded. | ||
| - | * This may only be an issue when playing a trunk servers only? | ||
| - | |||
| - | ==== Client freezes using other than default .glade layout ==== | ||
| - | //~July, 2010.// \\ | ||
| - | Two users are known to have experienced a case where the gtk-v2 client (widely varying versions) locks up when a non-default .glade layout is selected (other than gtk-v2). \\ | ||
| - | When running under gdb, it appears the client is locked up in metaserver code. | ||
| - | |||
| - | The first observation by kbulgrien was on Mandriva 2007 (low memory, slow CPU), \\ | ||
| - | but various other Mandriva 2007 systems did not exhibit the problem. \\ | ||
| - | Deleting or renaming the ~/ | ||
| - | When the system was upgraded to Mandriva 2009.0, the problem disappeared. | ||
| - | | ||
| - | The second time the issue was noted by MasseR using Ubuntu 9.10. \\ | ||
| - | In this case, a workaround was discovered. If the client was launched specifying both '' | ||
| - | If both opengl and an alternate .glade layout is specified in the configuration file, the problem recurred. | ||
| - | |||
| - | ===== 1.50.0 ===== | ||
| - | * This client is affected by [[http:// | ||
| - | * Replace the broken dialogs.glade file with a recent version that is downloadable [[http:// | ||
| - | |||
| - | ===== Keyboard input impossible or confusing ===== | ||
| - | In below versions called " | ||
| - | The problem did not occur, when "Popup Windows" | ||
| - | and hit the button " | ||
| - | and re-start the client to re-read the gdefaults configuration file. \\ | ||
| - | The user could have altered that entry manually, too, but that file does not exist when the client gets installed newly \\ | ||
| - | and the default is set to **0** inside the source code \\ | ||
| - | in function // | ||
| - | Another possibility would have been the cmdline-parameter [[:/ | ||
| - | but the -help parameter claimed, that -popups would have been the default, and why using that option, when it would have been the default ? \\ | ||
| - | The Popup Login-Window is nice to have, but the tiny jumping window to press to play Again or Not after applying a save-bed is a reason to want to disable these popups. \\ | ||
| - | See also the Changelog : [[: | ||
| - | |||
| - | |||
| - | ===== 1.11.0 ===== | ||
| - | * Double text issues still a problem on recent Ubuntu (Gutsy, Hardy, Intrepid) based 64bit systems when using the GTK2 ([[trunk]] and [[branch]]) client. | ||
| - | * [[: | ||
| - | * The 1.50.0 client does not have this problem. | ||
| - | * See also [[http:// | ||
| - | |||
| - | ===== 1.10.0 ===== | ||
| - | * Dec-23-2007: | ||
| - | |||
| - | ===== 1.9.1 ===== | ||
| - | |||
| - | crossfire-client-gtk2 under Ubuntu Edgy (v1.9.1-1) and Feisty (v1.9.1-2) (untested on other versions or releases) | ||
| - | * We've heard there' | ||
| - | * Feb-22-2007: | ||
| - | * Sept-18-2007: | ||
known_client_issues.1521366270.txt.gz · Last modified: (external edit)