This is an old revision of the document!
In case you don't get a metaserver list:
March, 2011.
Launching a trunk gtk-v2 client (1.60.0+) with an old user's .crossfire folder caused a fatal crash.
Renaming the .crossfire folder resolved the issue.
Full diagnosis of the root cause has not been done.
September, 2010.
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).
killall -HUP crossfire-client-gtk2
will kill it, but most window manager functions do not appear to be successfull at closing the hung client.
It appears that the client keeps trying to do socket operations to send the commands to the now disconnected server. GDB shows it stuck much if the time in _ _kernel_vsyscall, but sometimes you can catch in in libpthread.so.
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. This has probably been an issue for a very long time, but just has not been noticed or reported.
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.
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.
~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: GTK_MODULES=“”; crossfire-client-gtk2
.
In at least one instance of non-working themes, GTK_MODULES was set to canberra-gtk-module
, but the settings for all reports is unknown.
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.
~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 SVN is fixed. The fix is an update to {prefix}/share/crossfire-client/glade-gtk2/dialogs.glade , and does not require a re-compile.
Various reports of broken chat/say/tell/shout with trunk servers are reported:
~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 ~/.crossfire/gdefaults2 would allow the client to work.
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 -opengl -window_xml <any.glade>
, the client started properly.
If both opengl and an alternate .glade layout is specified in the configuration file, the problem recurred.
In below versions called “Double Text” and “Double up Keypress” Bugs were re-solved short time before the release of the version 1.12.0 of the client.
The problem did not occur, when “Popup Windows” had been chosen in the Menu > Client > Configure > General
and hit the button “Save” to save to the file gdefaults as popups set to 1
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 init_client_vars() in file common/init.c as variable want_config[CONFIG_POPUPS] = FALSE; .
The Popup Login-Window is nice to have, but the jumping small 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 : Keyboard input impossible or confusing
crossfire-client-gtk2 under Ubuntu Edgy (v1.9.1-1) and Feisty (v1.9.1-2) (untested on other versions or releases)