Any ideas how to fix unresponsive client?

SilverNexus · Post by **SilverNexus** » Thu Oct 17, 2013 9:19 pm

My Crossfire Client decided to inexplicably stop working today. It loads the windows for the server selection and the client, but fails to populate either window with anything; they remain grey boxes.
I played it fine yesterday, and hadn't updated it since then, so I was wondering if this was on my end.
I attempted to revert to an older revision, but that also did not fix the problem. Every time I run svn up, it tells me I have conflicts in aclocal.m4 and common/def-keys.h. When I look at the repo on SourceForge, neither of the two files exist.
Are these two files the source of my problems, or is something else missing?

EDIT: I get this output in the terminal when I run the program:

Code: Select all

WARNING: gnome-keyring:: couldn't connect to: /run/user/dan/keyring-yBLKec/pkcs11: No such file or directory
[  INFO  ] (Client Version) GTK V2 Unix Client 1.70.0.dev-r19083M (using gtk-v1.glade)
[  INFO  ] (common::raiseChild) Raising /usr/local/bin/cfsndserv with flags 7

(crossfire-client-gtk2:13925): Gtk-WARNING **: gtk_scrolled_window_add(): cannot add non scrollable widget use gtk_scrolled_window_add_with_viewport() instead
[  INFO  ] (gtk-v2::init_image_cache_data) Init Image Cache

Also, the only way to exit the program is to use

Code: Select all

sudo killall -9 crossfire-client-gtk2

Even Ctrl-C in a terminal window running it does not terminate the process.

UPDATE: It's not the repo version. I downloaded v1.70.0 and tried to use that and encountered the same problem. Something is wrong on my end. What, I'm not sure, but it is clearly something.

SilverNexus · Post by **SilverNexus** » Fri Oct 18, 2013 11:15 am

Well, I can only conclude it was a bad update.

My Linux won't even boot anymore

.

At least I have a recovery disk.

Website · Post by **Leaf** » Fri Oct 18, 2013 7:10 pm

Oh my, sorry to hear that!

For the original question, I was going to suggest a complete recompile of the client.

Inside the client directory, run the following:

sudo make clean;sh autogen.sh && make && sudo make install

Hope all goes well with the system recovery.

SilverNexus · Post by **SilverNexus** » Sat Oct 19, 2013 11:57 pm

I think I figured out the problem; for whatever reason, the client does not seem to load correctly when the saved window position is fullscreen on 1920x1080 resolution. Manually dragging the window size to the same position of fullscreen (but not actually using the maximize button) does not break the client. It seems to be happening with svn repository, manual download and binary download versions of the client, and has occurred on both my 64-bit Linux Mint 15 install and a 32-bit live DVD of the same OS.

To solve this (once I fix my Mint install), I should be able to delete ~/.crossfire/gtk-v1.pos and have a running client once more.

EDIT: I should note that the end process dialog that shows up because the client is unresponsive actually closes the client on the live DVD.

mwedel · Post by **mwedel** » Mon Oct 21, 2013 7:31 am

Rather than kill -9, a kill -SEGV might work, and then result in the client dumping a core file.

With a core file, gdb can then be used to see where the client is stuck.

Actually better is you can attach gdb to a running process with gdb crossfire-client-gtk <pid>, and then hopefully break and and do a 'where'.

From the description, it sorts of sounds like it is getting stuck figuring where the windows may end up - I could certainly believe there are bugs in the client if the saved window positions are somehow 'wrong' with respect to actual size.