GNOME Bugzilla – Bug 394420
Schedule Transaction Editor logs GLib-Critical messages
Last modified: 2018-06-29 21:21:57 UTC
When starting the Scheduled Transaction Editor the following messages are logged to the terminal window. This is a development version. It may or may not work. Report bugs and other problems to gnucash-devel@gnucash.org. You can also lookup and file bug reports at http://bugzilla.gnome.org The last stable version was GnuCash 2.0.4 The next stable version will be GnuCash 2.2 gnucash: [M] "Found Finance::Quote version ""1.12" (gnucash:8622): GLib-CRITICAL **: g_date_set_month: assertion `g_date_valid_month (m)' failed (gnucash:8622): GLib-CRITICAL **: g_date_strftime: assertion `g_date_valid (d)' failed (gnucash:8622): GLib-CRITICAL **: g_date_strftime: assertion `g_date_valid (d)' failed (gnucash:8622): GLib-CRITICAL **: g_date_strftime: assertion `g_date_valid (d)' failed (gnucash:8622): GLib-CRITICAL **: g_date_strftime: assertion `g_date_valid (d)' failed (gnucash:8622): GLib-CRITICAL **: g_date_strftime: assertion `g_date_valid (d)' failed (gnucash:8622): GLib-CRITICAL **: g_date_strftime: assertion `g_date_valid (d)' failed (gnucash:8622): GLib-CRITICAL **: g_date_strftime: assertion `g_date_valid (d)' failed (gnucash:8622): GLib-CRITICAL **: g_date_strftime: assertion `g_date_valid (d)' failed (gnucash:8622): GLib-CRITICAL **: g_date_strftime: assertion `g_date_valid (d)' failed (gnucash:8622): GLib-CRITICAL **: g_date_strftime: assertion `g_date_valid (d)' failed (gnucash:8622): GLib-CRITICAL **: g_date_strftime: assertion `g_date_valid (d)' failed (gnucash:8622): GLib-CRITICAL **: g_date_strftime: assertion `g_date_valid (d)' failed (gnucash:8622): GLib-CRITICAL **: g_date_set_month: assertion `g_date_valid_month (m)' failed (gnucash:8622): GLib-CRITICAL **: g_date_strftime: assertion `g_date_valid (d)' failed (gnucash:8622): GLib-CRITICAL **: g_date_strftime: assertion `g_date_valid (d)' failed (gnucash:8622): GLib-CRITICAL **: g_date_strftime: assertion `g_date_valid (d)' failed (gnucash:8622): GLib-CRITICAL **: g_date_strftime: assertion `g_date_valid (d)' failed (gnucash:8622): GLib-CRITICAL **: g_date_strftime: assertion `g_date_valid (d)' failed (gnucash:8622): GLib-CRITICAL **: g_date_strftime: assertion `g_date_valid (d)' failed (gnucash:8622): GLib-CRITICAL **: g_date_strftime: assertion `g_date_valid (d)' failed (gnucash:8622): GLib-CRITICAL **: g_date_strftime: assertion `g_date_valid (d)' failed (gnucash:8622): GLib-CRITICAL **: g_date_strftime: assertion `g_date_valid (d)' failed (gnucash:8622): GLib-CRITICAL **: g_date_strftime: assertion `g_date_valid (d)' failed (gnucash:8622): GLib-CRITICAL **: g_date_strftime: assertion `g_date_valid (d)' failed (gnucash:8622): GLib-CRITICAL **: g_date_strftime: assertion `g_date_valid (d)' failed Attached is a test file.
Created attachment 79791 [details] Sample/Test GnuCash data file
(Just out of curiosity:) Did you change your locale recently so that the date format changed? I.e. did you start gnucash in french language, then added a scheduled transaction, and now start gnucash in english language again?
(In reply to comment #2) > (Just out of curiosity:) Did you change your locale recently so that the date > format changed? I.e. did you start gnucash in french language, then added a > scheduled transaction, and now start gnucash in english language again? > No - Only think I have done with currencies was to enable in security editor. Don't think I'm tracking any though. Error occurs on two systems 1)"production" while I do run both std release and svn trunk - nothing but "real" transactions are entered, 2) test system - all kinds of expermentation (verifing documentation). Same message both systems.
I don't see this with 2.0.1 or on branches/sx-cleanup/. Dave, is this repeatable for you? If so, would you mind trying to dig in and seeing where those messages are coming from? $ /usr/bin/gnucash-env gdb /usr/bin/gnucash-bin (gdb) run --g-fatal-warnings [gnucash starts; open sx editor, "--g-fatal-warnings" will make gnucash bomb out when you get the first warning] (gdb) backtrace
Oh, I do see these with trunk. With your datafile and one of my own. Just to be clear, is the version string for the bug (2.0.4) correct? Or do you only see this on trunk?
I'll answwer in reverse order It appears that the messages do not appear in 2.0.2, but 2.0.3, 2.0.4 and svn-trunk do give the message. yes - it appears reproducable. Both x86_64 and i386 system give messages (x86_64 2.0.4 not available in repositories). I'm post the output from gdb below (2.0.4) ============================================================================ (gdb) run --g-fatal-warnings Starting program: /usr/bin/gnucash-bin --g-fatal-warnings (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [snip] [Thread debugging using libthread_db enabled] [New Thread -1208809776 (LWP 16953)] (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) ---Type <return> to continue, or q <return> to quit--- (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) gnucash: [M] "Found Finance::Quote version ""1.12" GLib-CRITICAL **: g_date_set_month: assertion `g_date_valid_month (m)' failed aborting... Program received signal SIGABRT, Aborted. [Switching to Thread -1208809776 (LWP 16953)] 0x003fb402 in __kernel_vsyscall () (gdb)
(In reply to comment #6) > It appears that the messages do not appear in 2.0.2, but 2.0.3, 2.0.4 and > svn-trunk do give the message. > I'm post the output from gdb below (2.0.4) [...] > GLib-CRITICAL **: g_date_set_month: assertion `g_date_valid_month (m)' failed > aborting... > > Program received signal SIGABRT, Aborted. > [Switching to Thread -1208809776 (LWP 16953)] > 0x003fb402 in __kernel_vsyscall () > (gdb) And what's the output of the gdb command 'backtrace' at this point?
(confirming)
Sorry didn't read all the instructions .... (gdb) backtrace
+ Trace 102467
trunk@15408. Tagged for backport to branches/2.0; if we do a 2.0.5, it should be in there. Otherwise, 2.2.
Backported to 2.0 as r15439. Should be in 2.0.5
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=394420. Please update any external references or bookmarks.