Crash, attempted to move page to a section.

[capsicum]

I had a number of pages, with links but no section hierarchy. My first attempt to move a page into a section worked, my second attempt where I moved a different page into the same section as before resulted in an instant crash. I right clicked the page in the left side bar, selected move page, entered the section,(here it gave two seemingly identical suggested sections, the field is too narrow to see the right ends of the section titles so they might be different.) and upon hitting enter, ZIM crashed, the window closed and a bug tracker popped up. Unfortunately it is the wrong bug tracker(centos7) and so I copied the data into text files attached below.
On reloading Zim, the original page move was successful in spite of the original crash.

I was able to repeat the crash, again on the second page move in a row, this time with a different target section and pages.

Zim.noarch 0.65-1.el7 @epel (repo)
CentOS-7 kernel 3.10.0-327.10.1.el7.x86_64 SMP
GNOME 3.14.2
gtk-vnc2.x86_64 0.5.2-7.el7
gtk2.x86_64 2.24.28-8.el7
gtk2-immodule-xim.x86_64 2.24.28-8.el7
gtk3.x86_64 3.14.13-16.el7
gtk3-immodule-xim.x86_64 3.14.13-16.el7
gtkmm24.x86_64 2.24.2-8.el7
gtkmm30.x86_64 3.8.1-3.el7
gtksourceview3.x86_64 3.14.3-1.el7

pygtk2.x86_64 2.24.0-9.el7
pygtk2-libglade.x86_64 2.24.0-9.el7

"python2.7 killed by SIGSEGV"

$INFO: Index update done
DEBUG: Action: close (delete-event)
DEBUG: Wrote <UnixFile: /root/.cache/zim/notebook-root_Notebooks_Notes/state.conf>
DEBUG: Remote call from 7673: <RemoteMethodCall: 7673: zim.ipc.Server(None).on_object_quit((<RemoteObject: zim.gui.GtkInterface(file:///root/Notebooks/Notes)>,), {})>
INFO: Last child quit, stopping server
DEBUG: Server stopped listening
INFO: Remove file: /tmp/zim-root/zim-server-authkey
DEBUG: Remote call returned to 7673: True
DEBUG: Server process 7671 quit
DEBUG: Child process 7673 quit
DEBUG: Server thread for process 7673 quit

[capsicum (capsicumw)]

This move page induced crash happens fairly frequent, but not consistently.

[Jaap Karssenberg (jaap.karssenberg)]

Afraid this logging doesn't help me to trace the error.

You can run zim with "zim --standalone -D" and it will print debug log to the terminal. That will help to get the actual error on the python interpreter level.

REgards,

Jaap

[Launchpad Janitor (janitor)]

[Expired for Zim because there has been no activity for 60 days.]