GNOME Bugzilla – Bug 502649
Register transactions may not display
Last modified: 2018-06-29 21:56:03 UTC
Please describe the problem:
When opening an account register in a new tab, the account's transactions may not display.
Steps to reproduce:
1. Open an account register in a new tab. NOTE: The account must contain enough transactions such that scrolling would be necessary to see the oldest one.
Only the column headings (at the top) and the current date (at the bottom, to begin entering a new transaction) are displayed. The rest of the register is blank (see attached screen capture).
Transactions are displayed normally.
Does this happen every time?
Once opened, clicking anywhere inside the register or pressing the up arrow key will cause the transactions to magically appear.
Created attachment 100635 [details]
Screen capture of blank register
This is still a problem in 2.2.2 if GnuCash is installed via a .exe setup file.
However, this problem goes away if I compile GnuCash in my own Windows build environment, then run it from an MSYS shell. Perhaps this difference has something to do with the difference in visual styles? (If you install GnuCash via the .exe file then dialog box buttons such as "Close" and "Cancel" don't have graphics on them. Run your own build from an MSYS shell and they will.)
I have experienced this bug as well. It still happens in 2.2.3. It does not happen on every machine on which I run the program. I use a copy installed on a USB flash drive and the same installation works fine on two of the three computers I use regularly, and on the third I experience this problem. All three machines are Windows XP SP2, fully updated. I also confirmed a regular install to C:\Program Files on that machine behaves the same way.
I also reported this in bug # 511343
This problem happened to me when I "upgraded" to 2.2.3 from 2.2.1
Then I tried 2.2.2 and it also happened. All of these were on the same PC/laptop.
So I am using 2.2.1 without the problem. Still want to upgrade when this is fixed! :)
XP Home Edition Version 2002 SP2
1.6 GHz Pentium M
Intel Extreme Graphics 2 for Mobile (Intel 82852/82855 GM/GME Graphics Controller)
1280x768 Highest 32bit
Shawn, your experience would seem to suggest that different PCs get different results with the same version of GnuCash. Do you know of anything different about that third machine (the one that experiences the bug)? Is the GnuCash data file on the USB drive, or does each machine have its own? Have any of the machines ever had any version of GnuCash installed directly onto the hard drive?
Diane, your experience would seem to suggest that the same PC gets different results with different versions of GnuCash. The bug is not seen in 2.2.1 but is seen thereafter.
Please check whether this is related to http://wiki.gnucash.org/wiki/Windows#Font_problems .
/me is looking at this now.
Confirmed with the default Windows XP style (first thing for me is to switch back to Classic ;-)).
Created attachment 104760 [details]
Close-up of cut off button image
Andreas, I followed the instructions in the wiki that you pointed out, and found that the problem disappeared if I switched my Message Box font from Tahoma 8 to Tahoma 10. So that can be used as a workaround. Cool.
Any idea where the bug originates? The register actually displays OK in Tahoma 8, provided you are willing to click on it first to make the transactions appear. It seems to me that if the font size is really the problem then clicking on the register should not fix it. So something else is going on.
By the way, GnuCash doesn't look quite right in Tahoma 10 either... For instance, the close button on each tab seems to be cut off, so that you only see about 75% of the 'X' button image (see attachment).
Hm, I wanted to link you to bug 432021, but now I see that Zach commented again on it, making this bug look like a complete duplicate of it.
Andreas, I read bug 432021. I never would have guessed that it was the same bug by the title, description, or attachments, but what I'm experiencing certainly sounds like what Zach describes in the most recent comment (#13). I've never seen any of the other rendering problems discussed before that, but maybe that's just the evolution of the same bug.
(In reply to comment #5)
> Shawn, your experience would seem to suggest that different PCs get different
> results with the same version of GnuCash. Do you know of anything different
> about that third machine (the one that experiences the bug)? Is the GnuCash
> data file on the USB drive, or does each machine have its own? Have any of the
> machines ever had any version of GnuCash installed directly onto the hard
Charles, this is with the same data file on the USB. Two of the machines have had GnuCash installed to the hard drive and then removed (one of the working machines and the one with the bug). I am using my GnuCash Portable launcher (http://portableapps.com/node/10633) to launch on all machines, which takes care of existing hard drive install registry entries if they exist. Just in case it was something odd with my launcher I checked with a hard drive install, as I mentioned, and got the same behavior.
*** Bug 511343 has been marked as a duplicate of this bug. ***
*** Bug 517565 has been marked as a duplicate of this bug. ***
*** Bug 507178 has been marked as a duplicate of this bug. ***
Does this problem still occur in 2.2.9 (just released)? It includes a newer version of the Gtk+ library.
*** Bug 570825 has been marked as a duplicate of this bug. ***
This problem continues to be experienced in 2.2.9 (see bug 570825), so the upgrade to Gtk+ 2.14.7 didn't fix it.
For anyone willing/able to compile trunk, does r18023 fix the problem for you?
Actually, please test with at least r18024 or you may find that the scroll position is off when the register is first opened.
Can anyone confirm that this is fixed in 2.3.0?
(In reply to comment #20)
> Can anyone confirm that this is fixed in 2.3.0?
If there were a Windows build I'd be happy to test it.
There are now nightly bleeding-edge builds for Windows that can be tested. The resulting installer .exe can be found at:
Just remember that these are not considered safe-to-use with precious data, so make a backup first. Please test with r18101 or better and let me know how it goes.
I've never seen the effect described in this bug, where no transactions are showing, but I often (but not usually reproducibly) get the effect in bugs 517565 and 507178 where there's a large grey area and some transactions showing at the bottom. Those are marked as duplicates of this.
I have my file in a state where, after opening with 2.2.9 and opening a particular account, it consistently displays like 517565 and 507178.
Switching to r18101 does not display the problem, so it looks good to me.
(Though, as I said, I've never seen the exact effect as initially described in this bug.)
(Windows XP, SP3, classic theme, GnuCash r18101 from the link in #22)
OK, I strongly suspect that bug 432021 was the same underlying problem anyway, with a variation in font size. I'm going to close this out as FIXED, and we can reopen if anyone can reproduce the problem with r18101 or higher. Thanks for your help.
*** Bug 549888 has been marked as a duplicate of this bug. ***
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=502649. Please update any external references or bookmarks.