[Crossfire-wiki] [Crossfire DokuWiki] page changed: known_client_issues

Sat Mar 12 21:23:11 CST 2011

A page in your DokuWiki was added or changed. Here are the details:

Date        : 2011/03/12 21:23
User        : 
Edit Summary: Fatal crash trying to start gtk-v2 when old .crossfire exists.

@@ -5,8 +5,9 @@
    * 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/Multiple/SVN =====
+   * 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.
    * 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.
    * ~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.


IP-Address  : 75.23.46.105
Old Revision: http://wiki.metalforge.net/doku.php/known_client_issues?rev=1283581483
New Revision: http://wiki.metalforge.net/doku.php/known_client_issues

-- 
This mail was generated by DokuWiki at
http://wiki.metalforge.net/

