Follow-up Comment #3, bug #17608 (project freeciv):

Also seen by alocritani (duplicate bug #17724).

Not sure how to debug this -- is there a way of forcing GTK to segfault or
otherwise get a backtrace when it hits a "Gtk-CRITICAL"?

Otherwise, perhaps running the client as something like "freeciv-gtk2 -d 4
>logfile 2>&1" and attaching "logfile" will give us a clue whenabouts this is

Otherwise, perhaps it's some setting difference? Can someone who sees this
attach their ~/.freeciv-client-rc-2.3?


Reply to this item at:


  Message sent via/by Gna!

Freeciv-dev mailing list

Reply via email to