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 351351 - Opening non-existing file gives weird error message
Opening non-existing file gives weird error message
Status: VERIFIED FIXED
Product: GnuCash
Classification: Other
Component: Backend - XML
git-master
Other Linux
: Normal normal
: ---
Assigned To: Chris Lyttle
Chris Lyttle
: 330932 (view as bug list)
Depends on:
Blocks: 347575
 
 
Reported: 2006-08-14 19:37 UTC by Christian Stimming
Modified: 2018-06-29 21:11 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Screenshot of error message (7.69 KB, image/png)
2006-08-14 19:38 UTC, Christian Stimming
Details

Description Christian Stimming 2006-08-14 19:37:13 UTC
If you open a non-existing file in gnucash, the error message is wildly misleading:

  The file type of file /bla/bla is unknown.

Steps to reproduce:

  gnucash /bla/bla

What is expected instead: Gnucash should say "File /bla/bla does not exist.".

This should be fixed in branch-2.0 as well.
Comment 1 Christian Stimming 2006-08-14 19:38:22 UTC
Created attachment 70885 [details]
Screenshot of error message

The weird error message that is shown if the file in question does not exist (or has been removed since last startup).
Comment 2 Christian Stimming 2006-08-18 20:27:06 UTC
Actually this very same weird error message is shown if you open a file that you don't have read permissions for.

Steps to reproduce (if you own the file):

  touch ~/foo
  chmod 000 ~/foo
  gnucash ~/foo

The game gets an interesting twist if you also don't have write permission to the directory. Try this:

  gnucash /etc/shadow

Heh.
Comment 3 Christian Stimming 2006-09-03 11:07:52 UTC
Fixed in r14789. Awaiting audit and back-port.
Comment 4 Christian Stimming 2006-09-12 14:05:01 UTC
*** Bug 330932 has been marked as a duplicate of this bug. ***
Comment 5 Andreas Köhler 2006-09-20 21:30:49 UTC
I guess we have to append [r14791, r14865] to [r14789].
Comment 6 Christian Stimming 2006-09-22 09:53:00 UTC
Re comment#5: You mean, these three changesets should be back-ported together? This bug here first only asks for r14789 - I'm still waiting for someone who accepts the audit for this one...
Comment 7 Christian Stimming 2006-09-22 12:12:12 UTC
Oh, and in case anyone wonders about the string addition in r14791: Per the policy described on http://wiki.gnucash.org/wiki/String_Freeze , I'd totally accept the new string introduced by r14791 because it fixes "an existing string which is just plain wrong and/or is completely misleading". So the new string of r14791 shouldn't stop us from back-porting r14791 as well.
Comment 8 Derek Atkins 2006-09-23 12:16:06 UTC
Merged into 2.0 in r14883, along with the two subsequent further fixes.
Comment 9 John Ralls 2018-06-29 21:11:19 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=351351. Please update any external references or bookmarks.