After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 337185 - Save confirmation displayed when no data has been changed
Save confirmation displayed when no data has been changed
Status: VERIFIED FIXED
Product: GnuCash
Classification: Other
Component: User Interface General
1.9.x
Other All
: Normal blocker
: ---
Assigned To: David Hampton
Chris Shoemaker
Depends on: 337780
Blocks:
 
 
Reported: 2006-04-04 13:25 UTC by Adam Buchbinder
Modified: 2018-06-29 21:01 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Adam Buchbinder 2006-04-04 13:25:48 UTC 
Please describe the problem:
The "Save changes to the file?" dialog displays even when no file is open, if
the new-file druid has been cancelled.

Steps to reproduce:
1. Open GnuCash with --nofile.
2. File--New--New File.
3. Cancel the druid.
4. File--New--New File.


Actual results:
The "Save changes to the file?" dialog appears.

Expected results:
The dialog should not appear.

Does this happen every time?
Yes, this is repeatable.

Other information:
Comment 1 Christian Stimming 2006-04-05 09:21:21 UTC 
Pretty much caused by the same issue as bug#327780 . Might be closed as duplicate.
Comment 2 Adam Buchbinder 2006-04-05 20:56:17 UTC 
Yeah, I see it mentioned as comment 5 over on that bug. Closing as duplicate.
Comment 3 Adam Buchbinder 2006-04-05 20:56:57 UTC 
Yeah, I see it mentioned as comment 5 over on that bug. Closing as duplicate.

*** This bug has been marked as a duplicate of 327780 ***

*** This bug has been marked as a duplicate of 327780 ***
Comment 4 Derek Atkins 2006-04-25 15:38:00 UTC 
I've reopened this bug because bug #327780 wont fix this one (see #327780#c12)
Comment 5 Derek Atkins 2006-04-25 15:39:42 UTC 
This problem still exists in 1.9.5, so I've upped the version while also increasing the severity to "blocker" because it really is a usability issue.
Comment 6 David Hampton 2006-04-26 04:14:23 UTC 
Fixed in r13859.
Comment 7 Derek Atkins 2006-04-26 16:47:55 UTC 
Unfortunately this is not fixed.  I just tested r13861.

To reproduce this bug:

  1) start gnucash
  2) open a register
  3) [optionally] close the register
  4) exit gnucash

When you exit gnucash, it believes data has changed, even when the user has done nothing to the data but open a register.
Comment 8 David Hampton 2006-04-26 17:29:44 UTC 
Ah, but you've now changed the conditions of the bug report.  What you're seeing with your new testing methodology is very likely a result of 337780 or related to 337780.  Gnucash is now complaining about a dirty split, which is probably the blank split created when the register is opened.
Comment 9 Derek Atkins 2006-04-27 14:41:48 UTC 
Maybe, but if you look in comment 12 over there you will see that he doesn't care about this particular problem, about dirtying the book with the blank split.  So, I don't particularly care which bug number it is -- the two probably ARE related -- but just considering them separately is probably doing users a disservice.
Comment 10 David Hampton 2006-04-27 18:04:45 UTC 
Bug #339943 has been opened to address the issues in comment 7.
Comment 11 John Ralls 2018-06-29 21:01:04 UTC 
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=337185. Please update any external references or bookmarks.