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

[no-reply_wiki at metalforge.org]

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

Date        : 2010/07/31 11:45
User        : kbulgrien
Edit Summary: Improve "facts" about chat/say/tell/shout issues.

@@ -7,9 +7,13 @@
  
  ===== Unspecified/Multiple/SVN =====
  
    * 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 dialogs.glade, and does not require re-compile.
-   * Various reports of broken chat/say with trunk servers is reported.  One report by Invidious user is for Debian Stable 5.0.4 and current GTK V2 Unix Client 1.50.0.dev-r13535M (using gtk-v2.glade) chat/tell.  This report says say/shout 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?
+   * Various reports of broken chat/say/tell/shout with trunk servers are reported:
+     * 1.11 clients on trunk servers: chat/say does not work.
+     * Report by Invidious user is for Debian Stable 5.0.4 and current GTK V2 Unix Client 1.50.0.dev-r13535M (using gtk-v2.glade) chat.  This report says 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?
    * 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.
  


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

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