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 691587 - Crash while loading corrupted .gnucash/stylesheet-2.0
Crash while loading corrupted .gnucash/stylesheet-2.0
Status: RESOLVED FIXED
Product: GnuCash
Classification: Other
Component: User Interface General
2.4.x
Other All
: Low critical
: ---
Assigned To: Christian Stimming
Geert Janssens
Depends on:
Blocks:
 
 
Reported: 2013-01-12 03:06 UTC by Subbarayan
Modified: 2018-06-29 23:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Trace file for gnucash (901 bytes, text/plain)
2013-01-13 14:15 UTC, Subbarayan
Details
Metadata files, which made my gnucash to crash (15.35 KB, application/x-zip-compressed)
2013-01-19 09:02 UTC, Subbarayan
Details
Console error when crashing (captured on linux) (5.51 KB, text/plain)
2013-01-19 09:34 UTC, Geert Janssens
Details

Description Subbarayan 2013-01-12 03:06:15 UTC
Hey,
I am a beginner with some 2 months of data with GNUcash package.  The tool worked like a gem till last evening; when my Windows blue-screened.  post reboot, gnucash does not start; no error messages as well.

when i click gnucash, for sometime i get hourglass; and post that no action.  i get splash screen, and the last loading thing i see in the splash screen is "loading system".  if i watch task manager, i see 1 gnucash.exe process and 2*gconfd-2.exe processes running.  when the splash screen vanishes, gnucash.exe is terminated, and subsequently after sometime, the other two processes as well is getting terminated.

i tried reinstalling the same package, and no difference.  please help me.

Subbarayan N.
Comment 1 Mike Evans 2013-01-13 09:49:44 UTC
Thank you for reporting this.  We will however, need a lttle more information to enable us to diagnose this behaviour.

Please read http://wiki.gnucash.org/wiki/Tracefile#Trace_file_on_Windows and post the file contents here.

Note: Blocker: Blocks development and/or testing work.  Changing severity to critical.
Comment 2 Subbarayan 2013-01-13 14:15:46 UTC
Created attachment 233383 [details]
Trace file for gnucash
Comment 3 Subbarayan 2013-01-19 07:43:15 UTC
Team,
can some one help me open gnucash?  It is not opening, I am not sure whether i still have my old data or not? whether to continue with this application or not? etc...  Once, I am able to open the existing database, and continue using this aplication, then we can go slow on this bug fixing :)

Subbarayan N
Comment 4 Geert Janssens 2013-01-19 08:38:37 UTC
The trace file doesn't show anything unusual, so that won't help us much further.

You mention that your system blue-screened. My experience with computer crashes is that if they happen at an unfortunate time, you may have some file corruption on disk. Let's start from that assumption and try to isolate the corrupted item.

The first potential file corruption would be the program itself. If some of the program files are damaged, the code will crash. As you say you already reinstalled the program, this should be fixed.

Next would be the metadata GnuCash uses. Check your user's home directory (typically c:\Documents and Settings\<username> or c:\users\<username>) for the following files and directories:
.banking
.gnucash
.gconf
.gconfd
.gnome2
.gnome2_private
.gtkrc-2.0
.gconf.path
And move them to some place else. They may not all be there, just move the ones you have. This will make GnuCash forget all preferences (including which file it last opened).
Then start GnuCash again.

If GnuCash starts fine like that, you can try the next step. Within GnuCash, use File->Open to open your data file and see if that works.
Comment 5 Subbarayan 2013-01-19 09:02:43 UTC
Created attachment 233849 [details]
Metadata files, which made my gnucash to crash
Comment 6 Geert Janssens 2013-01-19 09:31:40 UTC
From your attachment's comment I presume you can successfully start GnuCash again.

There were at least two corrupted files:
.gnucash\accelerator-map
.gnucash\stylesheets-2.0

You have two choices now. Either you simply continue to work as is and reconfigure GnuCash. This is probably the safest approach as most directories get recreated automatically.
Or you can try to restore some other settings by moving directories back. You can safely skip the .gnucash directory though. Other than the two corrupted files, there's not much in there that needs restoring.

Finally, I'll keep this bug report open because IMO GnuCash shouldn't crash when encountering corrupted (meta)data. Since it happened in a rarely occurring situation, I will mark it low priority though.
Comment 7 Geert Janssens 2013-01-19 09:34:13 UTC
Created attachment 233851 [details]
Console error when crashing (captured on linux)

For the record I have attached the console output that is generated on linux during the crash.

The crash itself is easily reproduced by extracting the corrupt stylesheets-2.0 file from the metadata zip file in attachment 233849 [details] and putting this corrupted file in your .gnucash directory before running gnucash.
Comment 8 Christian Stimming 2013-06-19 15:50:59 UTC
trunk r23059. Before, a ~/.gnucash/stylesheets-2.0 that contains nothing but a bunch of zero-bytes will crash gnucash during startup. With r23059, it will not crash but display a warning in the trace during startup and continue as normal. 

Can someone confirm, please?
Comment 9 Geert Janssens 2013-06-20 15:51:48 UTC
Confirmed. Thank you for fixing this.
Comment 10 John Ralls 2017-09-24 22:45:29 UTC
Reassign version to 2.4.x so that individual 2.4 versions can be retired.
Comment 11 John Ralls 2018-06-29 23:12:54 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=691587. Please update any external references or bookmarks.