GNOME Bugzilla – Bug 597005
Column width of first column in Budget is very wide
Last modified: 2018-06-29 22:29:08 UTC
Column width of first column in Budget is very wide (width of many windows). There for is is hardly possible to fill in the values of a budget. It is not possible to display the name of the budget and the value of the budget together. In version 2.3.5 the width is correct with the same file.
Issue is still present in 2.3.9. I have attached a screen shot to confirm. Restart of GnuCash does not help either. The column width stays as wide as it was. I have tried to re-size the column, but that has been a losing battle. Double-clicking on the column spacer also fails to remedy the situation. Given I get some time I will muck around in the code and try to find a fix.
Created attachment 148986 [details] Screenshot of wide Accounts column in the Budget panel issue in GnuCash 2.3.9
Yes, I've seen it too.
I have been hitting this issue lately with Gnucash 2.2.9on Ubuntu 9.10 and I have found its reproducible using the following steps: 1) Create a new budget and set number of periods to 4. 2) Resize the account name bar so all four period date columns are visible, then open an account category by clicking on the arrow. This causes the account name bar to resize and push the period dates to the right, aligning with the edge. 3) Create another budget, set number of periods to 1. Account name bar will now grow, seemingly forever, until you close one of the two budgets. I think this is probably related to bug #347265, since when the second budget is created and auto-resizes, this causes the first budget also to resize, effectively creating a resizing loop between the two budgets, causing them to grow and grow.
*** Bug 577617 has been marked as a duplicate of this bug. ***
This is indeed a very nasty bug, because it effectively prevents a user to from using budgets. However, I found a way to revert its consequences, and I am now able to edit one budget at a time. In order to reset the column width, one has to start up gconf-editor, and set the /apps/gnucash/window/pages/budget/name_width to around 800. Attached are two screenshots that demonstrate the value of name_width increasing by ca. 11000 per second. Note: I have GnuCash 2.2.8 with Ubuntu 8.10, but according to bug 577617, this is the right place to submit this comment.
Created attachment 155021 [details] gconf-editor view of the increasing budget 'name_width' column at 11:40:20
Created attachment 155022 [details] gconf-editor view of the increasing budget 'name_width' column at 11:40:40
I have the same problem on Ver 2.3.14 Can someone tell me what the work around is? I see the bug was close, but dont see the resolution thanks
(In reply to comment #9) > I have the same problem on Ver 2.3.14 Can someone tell me what the work around > is? I see the bug was close, but dont see the resolution > > thanks In Windows 7 I changed the file %gconf.xml in the directory C:\Users\<username>\.gconf\apps\gnucash\window\pages\budget. The following line must be there. In my case the value was very big. After changing the vulue to 800 the value was changed in my case automatically to 1605 by the application. <entry name="name_width" mtime="1279540522" type="int" value="1605">
Thank you, Ton. I was able to modify the name-width value and it worked.
Hi; I filed a bug about this some time ago which was apparently closed. I recently upgraded to gnucash 2.2.9 in a Gentoo AMD64 system and saw the recurrence of this problem. Based on the direction provided by Ton van Oosterm, I first attempted to edit the file /home/*/gconf/apps/gnucash/windows/pages/budget/%gconf.xml as root in Kwrite, but the changes were not permanent. I then installed gconf-editor and edited the schema there. It seems to have had the desired effect, with "name_width" value being set by the system to 526
Hi all! Please, note that it is DANGEROUS to EDIT gconf configuration files BY HAND because they are read and cached by gconf daemon, and all applications access them via the gconf daemon. Therefore it is very important that you use gconf-editor (GUI) or gconftool-2 (CLI) to edit gconf. I don't know how it works under Windows, but don't use text editors for this purpose if you're running Linux. GNOME Desktop Admin Guide, for instance, insists that all users must be logged out before you change any default preference values. [1] That is probably because although you can shut down the gconf daemon, it would get started up automatically as soon as any application would attempt to access gconf, and it is naturally very difficult to make sure no such request is made between the moment of shutdown, and the moment of updating XML file. [1] http://library.gnome.org/admin/system-admin-guide/stable/gconf-7.html.en
And in any case this needs to be fixed inside gnucash so that the name_width column doesn't get larger than the screen width.
BTW I have no idea how to fix this. The size is never set explicitly in gnucash, or I could not find that. Instead, the view widget is a class derived from GtkTreeView implemented in src/gnome-utils/gnc-tree-view-account.c, but again it never sets the size itself. Hence, I think this error occurs only with particular versions of gtk. Which ones did you have?
I'm not completely sure which package you are asking about, but I am still using GNOME 2.24.1 with libgtk1.2.10 and libgtk2.14.4 on Ubuntu 8.10. However, since it happens in Ubuntu 9.10 (comment#4), this *might* be true for libgtk2.18.3 as well. So, can you reproduce the error on your machine?
*** Bug 619573 has been marked as a duplicate of this bug. ***
Apart from installing gconf editor, the gconf key can also be updated using gconftool. See https://lists.gnucash.org/pipermail/gnucash-devel/2009-December/027021.html for an example.
*** Bug 638370 has been marked as a duplicate of this bug. ***
I just encountered this bug, and discovered that it seems to be triggered by opening a second budget page while my first budget is still open. You can watch the bottom scroll bar go to infinity right before your eyes.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 347265 ***
So, is it confirmed now that what Espen Rønnevik described in comment#4 is the true reason of this bug? Does it also mean that you somehow managed to stop the automatic resizing (bug 347265) and get rid of this bug, which means we might be close to finally fixing it?
Indeed. I have some code ready to fix the unintended resizing interference between two budget reports with different column counts. It was ready just too late for the release of 2.4.3 which is now in progress, so it will appear in 2.4.4. I will commit it as soon as the 2.4.3 is released.
Thanks a lot, Geert, for fixing this long-standing 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=597005. Please update any external references or bookmarks.