Zim

error during automatical store

Bug #1451179 reported by Jost-Juergen on 2015-05-03
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Zim
Undecided
Unassigned

Bug Description

using Zim 0.62
OS: Windows 8.1
during editing entries in Zim, zim will fail on saving the files.
this happens not every time, but often, much to often to can work fluent.

Jost-Juergen (jjeveit) wrote :
Jost-Juergen (jjeveit) wrote :

just i got an more specific erroer code from Zim, i think it is the same kontext:
This is zim 0.62
Platform: nt
Locale: de_DE cp1252
FS encoding: mbcs
Python: (2, 7, 8, 'final', 0)
Gtk: (2, 24, 10)
Pygtk: (2, 24, 0)
Zim revision is:
  branch: 062
  revision: 739 <email address hidden>
  date: 2014-10-10 21:28:06 +0200

======= Traceback =======
  File "zim\gui\pageview.pyo", line 5224, in do_link_clicked
  File "zim\gui\__init__.pyo", line 1242, in open_page
AssertionError: Could not close page

Bob (boababa) wrote :

Happens for me on Win 7, version 0.62, mobile install, english. Works just fine for a while after start-up, then, usually after backspacing a few times, decides to stop auto-saving and lose all changes made since last auto-save. If I continue typing without errors, next save works. If I backspace, there is a good chance it will fail to save again. This behavior seems to recover after system sleep or software restart.
In version 0.6, this did not happen...of course, the computer underwent many software changes at same time as update to version 0.62, so it could be external.

Jost-Juergen (jjeveit) wrote :

When I am using version 0.6 the error not appears.
Same situation as Bob told.

Jost-Juergen (jjeveit) wrote :

the situation is, using version 0.62 every 30 to 60 seconds the program stops.
the window with the error message appears, counting down some seconds, the you only can agree in loosing the last changes.
than, when trying to reconstruct the changes to the wiki, witch needs some time to, the nect error occurs.
so work is inpossible.

May be, it is a hint, using the version 0.60 the error does not occur.

Jost-Juergen

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments