GNOME Bugzilla – Bug 545722
Can't change date in dialog boxes
Last modified: 2018-06-29 22:08:09 UTC
Please describe the problem: When I run the investment portfolio I can only display prices from 7/01/2008 regardless of what date is selected in the options. Steps to reproduce: 1. Run update financial quotes 2. make sure there are several dates in the price editor 3. select any date option Actual results: When clicking on the price, the price that is displayed says 7/01/2008 Expected results: I want it to pull the price for the date specified in the option menu Does this happen every time? Yes Other information:
I can reproduce this in 2.2.6. This doesn't have anything to do with Finance::Quote, and it affects other reports too (Balance Sheet, for example). For now, a workaround is to select the date from the calendar. Instead of typing in a date, click the button on the right edge of the text box to pop up the calendar. Click on a date, close the calendar, then click OK.
Interesting... I am running on Windows XP and the dialogs work perfectly when I start GnuCash from an MSYS shell. If I start GnuCash from a DOS-style command line then the bug shows itself. So I am guessing this bug must be Microsoft related. I'll keep investigating.
Fix committed as r17459. Requesting backport for 2.2.
*** Bug 546160 has been marked as a duplicate of this bug. ***
*** Bug 546501 has been marked as a duplicate of this bug. ***
*** Bug 545748 has been marked as a duplicate of this bug. ***
*** Bug 545927 has been marked as a duplicate of this bug. ***
These duplicates have some differing descriptions but are all the same underlying problem. So far this seems to affect Windows users only.
*** Bug 547120 has been marked as a duplicate of this bug. ***
There is also a data loss issue when editing a scheduled transaction, as all the dates on all the pages are reset when you edit. This affects the repeat until date as well as the start date.
Sounds like those who use scheduled transactions on Windows might be better off skipping 2.2.6 and waiting for 2.2.7.
I am seeing the same trouble under Mac OS X 10.5.4, so the trouble is NOT limited to Windows users. Using 2.2.6, I see this same trouble when trying to use the reconcile account dialog.
Re comment 12: What you see is slightly different from Windows users. They always see the 1st of the month, whereas you said (on the mailing list) you always see the current date. So I don't know if this is the same bug or not. Perhaps it is the same but just expresses itself differently on Mac.
Yes, my experience is that it sets to the current date (as opposed to the first); I overlooked that piece. Everything else, though, stacks up. Moreover, bugs 546160 and 546501, marked as duplicates of this one, indicate the same behavior that I observed (i.e., date setting to current date, not the first). I will try to see whether I see the same behavior in some of the other areas mentioned by the others. That may clarify things.
I'm curious why Dave Reiser can't reproduce this on his Mac. Perhaps some library updates would be a workaround. However, I would also be very interested to know whether the patch that fixes the bug on Windows works for your Mac.
Changing the title and component as it is also possible for Mac users to be affected.
Can confirm bug 547120 on WinXP, now a dupe of this It gets worse though. I cannot even select the dates from the calendar widget either, so I'm stuck on Posting Invoices to 01/08/2008 with a due date of 01/08/2008 (dd/mm/yyyy) Would like to request the severity of this bug to be upgraded MAJOR as data could not be input correctly via alternative means and reverting back to 2.2.5 would reintroduce old bugs.
Can confirm bug 547120 on WinXP, now a dupe of this It gets worse though. The calendar drop-down widget does not allow me to select any dates with keyboard/mouse navigation either, so I'm stuck on Posting Invoices to 01/08/2008 with a due date of 01/08/2008 (dd/mm/yyyy) Would like to request the severity of this bug to be upgraded MAJOR as data could not be input correctly via alternative means and reverting back to 2.2.5 would reintroduce old bugs.
@Brian: coolguy4 on #gnucash suggests that you use Billing Terms to force a better due date as a temporary work-around.
(In reply to comment #19) > @Brian: coolguy4 on #gnucash suggests that you use Billing Terms to force a > better due date as a temporary work-around. As I noted on bug 547120, billing terms weren't being recognized. I had a 15-day term on but the due date was stuck at the same (bad) Post Date.
In New Invoice, typing in a date will change it back to 01/08/2008 constantly but it can can get around it by dropping down the calendar to select a date. However, you can't use the same work around when posting invoices. Dates in the drop down calendar just refuse to be selected.
Problems described by Brian is exactly the problem I see in Windows. All my records in setting share price window shows 08/01/2008. I think I will revert back to 2.2.5 awaiting for a new version.
*** Bug 548008 has been marked as a duplicate of this bug. ***
*** Bug 548327 has been marked as a duplicate of this bug. ***
*** Bug 548257 has been marked as a duplicate of this bug. ***
I believe that 2.2.7 will be released in about two weeks.
Thank you for working on a fix for 2.2.7, but here is one solution that worked for me: It's so stupid I am amazed that it actually worked! When posting an invoice, just before you bring up the dialog box, change your computer's (system) date to the date you want to post the invoice, bring up the dialog box and voila! it should be filled up with the correct date. Don't forget to reset your system date to the correct date asap, like before the auto-save kicks in.
*** Bug 550003 has been marked as a duplicate of this bug. ***
*** Bug 550121 has been marked as a duplicate of this bug. ***
*** Bug 551014 has been marked as a duplicate of this bug. ***
(In reply to comment #3) > Fix committed as r17459. Requesting backport for 2.2. Applied to branches/2.2 as r17522 for inclusion in GnuCash 2.2.7. Thanks a lot! (In reply to comment #26) > I believe that 2.2.7 will be released in about two weeks. Dumdidum... :-)
*** Bug 552927 has been marked as a duplicate of this bug. ***
*** Bug 553951 has been marked as a duplicate of this bug. ***
*** Bug 575721 has been marked as a duplicate of this bug. ***
*** Bug 586663 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=545722. Please update any external references or bookmarks.