Binary package hint: gnucash
This bug appeared since I upgraded to natty, it was working fine in maverick. The version I use is: 1:2.4.2-1ubuntu1
Since this looks like a display issue, I tried both Unity and the Classic mode with the same result.
With large accounts, the last rows are not rendered. If I scroll to the beginning of the account the rendering is normal but after a point the list rendering is not updated anymore and I get whatever was on the screen before.
The point seems to be related to the size of the table. It is 05/12/2009 in simple line and 10/14/2010 in double line.
The trace in /tmp/gnucash.trace also suggests this:
~
* 16:46:59 WARN <gnc.backend.dbi> [gnc_module_init_backend_dbi()] No DBD drivers found
* 16:47:11 CRIT <qof> qof_query_guid_predicate: assertion `options == QOF_GUID_MATCH_NULL' failed
* 16:47:13 WARN <Gdk> Native Windows wider or taller than 65535 pixels are not supported
* 16:47:13 WARN <Gdk> Native children wider or taller than 65535 pixels are not supported
* 16:47:13 WARN <Gdk> Native children wider or taller than 65535 pixels are not supported
* 16:47:13 WARN <Gdk> Native children wider or taller than 65535 pixels are not supported
* 16:47:44 WARN <Gdk> Native children wider or taller than 65535 pixels are not supported
* 16:47:44 WARN <Gdk> Native children wider or taller than 65535 pixels are not supported
* 16:47:57 WARN <Gdk> Native children wider or taller than 65535 pixels are not supported
* 16:47:57 WARN <Gdk> Native children wider or taller than 65535 pixels are not supported
* 16:50:16 CRIT <gnc.import.aqbanking> gnc_plugin_ab_account_selected: assertion `GNC_IS_PLUGIN_PAGE(plugin_page)' failed
~
==================================================
Finally, this looks similar to this debian bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561791
I tried to play with GDK_NATIVE_WINDOWS but with no results, and it is not set by default on my machine.
It's possible to work around the bug by only displaying a few hundred transactions in the preferences.
I can confirm that the work around mentioned by Olosta (many thanks for that, by the way) does allow you to view the most recent N transactions, and add new ones. Of course, the transactions that are not displayed cannot be viewed or edited. I have set the register display (N) to 500.