Bug#644930: bad LANG env crashes gnucash on File->New account

[lkml at think-future.com]

  Hi Micha,

  Thx for your msg and your work for Debian.

  As you suggested I built libgtk2.0-bin and tried again. No fix. Sorry.

  Besides, building libgtk was a PITA, all in caps. It was failing all over
  the build in docs, tutorials and finally doing the TEST stuff that made
  debuild stop (despite the "..] Error 2 [ignored]" msg). 
  Calling fakeroot manually and fixing up all docs/.. references in lots
  of install files and in rules (it _is_ tedious to exclude docs from being
  configured/built and packaged). 
  
  Finally there's the deb files. Well, just the patch didn't fix it. 

  Do you mean to also replace the -common stuff?

  Cheers

On Mon2011-10-10 at 10-18-06PM+0200, Micha Lenk wrote: 
# Date: Mon, 10 Oct 2011 22:18:06 +0200
# From: Micha Lenk <micha at debian.org>
# To: lkml at think-future.com
# CC: 644930 at bugs.debian.org, Debian GNOME Maintainers
#  <pkg-gnome-maintainers at lists.alioth.debian.org>, control at bugs.debian.org
# Subject: Re: Bug#644930: bad LANG env crashes gnucash on File->New account
# User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.20)
#  Gecko/20110822 Lightning/1.0b2 Icedove/3.1.12
# 
# tags 644930 + patch
# thanks
# 
# Hi,
# 
# Am 10.10.2011 21:54, schrieb lkml at think-future.com:
# > Problem description:
# >   Using "export LANG=de_DE; gnucash" to start gnucash. gnucash crashes upon
# >   Selecting "File -> New account".
# >   Same valid for de_DE at UTF-8 maybe others as well.
# >   export LANG=de_DE.UTF-8; gnucash however works as intended.
# > 
# > Further problem properties: 
# >   - exists iirc since 2008 or earlier
# >   - gnucash devs at #gnucash hint this might be related to libc or gtk.
# 
# This is very likely a duplicate of Debian bugs #616150 and #634091,
# which is IMHO a bug in the gtk+2.0 package.
# 
# If you want you can try my patch for gtk+2.0 that I've posted here:
# http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=57;filename=fix_null_pointer_segfault.patch;att=2;bug=616150
# 
# If you can confirm that this patch fixes your problem, I'll merge this
# bug with the other two bugs.
# 
# Regards,
# Micha