GNOME Bugzilla – Bug 170444
Crash on clicking on node account
Last modified: 2018-06-29 20:50:54 UTC
From: Akhil Srinivasan <akhilss@gmail.com> To: submit@bugs.gnome.org X-Mailer: bug-buddy 2.8.0 Subject: GNUCash crashes on clicking on node account Distribution: Debian 3.1 Package: GnuCash Severity: normal Version: GNOME2.8.3 unspecified Gnome-Distributor: Debian Synopsis: GNUCash crashes on clicking on node account Bugzilla-Product: GnuCash Bugzilla-Component: User Interface General Bugzilla-Version: unspecified Description: Description of the crash: Application crashes when i try to view any account by double-clicking on it. Steps to reproduce the crash: 1. Start GNUCash 2. Expand account tree till node account like Cash In Wallet 3. Double click on Cash In Wallet Expected Results: Application crashes saying Segmentation Fault How often does this happen? Everytime Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/guile-1.6' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 1076279712 (LWP 2860)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0x400de4ee in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 56897
Thread 1 (Thread 1076279712 (LWP 2860))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-03-15 07:37 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "GnuCash". Setting to default milestone for this product, '---' Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Computer: IBM Thinkpad 600X CPU: 500 Mhz Mem: 192MB Linux Kernel: 2.6.8-2
Thanks for reporting this problem. We need just a little more information: What is your exact version number of gnucash? What language setting are you using (environment variable LANG)? Does the reported problem occur with every data file that you can open, or only with one specific data file? Or did you just started using gnucash, so that you always get the "account creation druid" in the beginning? If that is the case, can you first save the accounts to a file and then try whether this problem occurs? If it does, can you open the saved file when starting gnucash the next time and see whether it still crashes?
GNUCash version: 1.8.10 LANG=en_IN LANGUAGE=en_IN:en_US:en_GB:en The Druid did run at first. GNUCash staerted up ok, i could expand the account tree ok but when i tried to view the node account it crashed. I have tried to access the same created file after restarting GNUCash with the same result. I also deleted the file and created another with the druid again with the same result.
*** Bug 310524 has been marked as a duplicate of this bug. ***
I reported a bug which has been marked as a duplicate of this bug, and in the process of answering the questions asked here it seems I found a clue about the problem. GnuCash is v1.8.10 from Debian Sarge (1.8.10-12). My default LANG setting based on my location is en_PH. When LANG=en_PH, GnuCash crashes as soon as an account is opened (also when I try to access certain reports which show account details). This happens consistently whether I open an existing file or create a new one. However, I just discovered now that when LANG=C (or LANG=en_US), GnuCash works fine. This bug has also been reported on the Debian bug tracking system[1], and I have notified the package maintainer about my recent findings. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=312109 --> Jijo
*** Bug 311039 has been marked as a duplicate of this bug. ***
Thomas Bushnell here. I've confirmed that this happens, and the problem is that MAX_DATE_LENGTH in engine/date.h is only eleven bytes. That's fine if the date format is "%d/%m/%Y" but many locales have longer date formats.
I've got a fix for this in CVS, committed to 1.8 and g2.
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=170444. Please update any external references or bookmarks.