reordering entries triggers random problems

Bug #1927117 reported by Michael Waldor
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Lifeograph
Triaged
Undecided
Unassigned

Bug Description

I have discovered just yesterday your nice tool to maintain my hiking tours. Sadly I encounter random problems when I try to reorder entries.

I have created a set of entries, organized in a small hierarchy. By accident I've created a new entry, and during deletion of this unwanted entry lifeograph crashed. After restart many entries were in a random sequence, additionally some of them have changed their type from "free floating" into hierarchically numbered. By dragging these numbered entries around suddenly they became free floating again. Happily I moved them again, and then a spurious enty named 1023.1023.some other numbers appeared. Trying to delete that triggered a crash.

Additionally I have a question: howto drag "safely" a child entry to move up to its parent level? Sometimes it works, sometimes that entry appears as a child of some other entry.

Revision history for this message
Michael Waldor (olwaldi) wrote :
Revision history for this message
Ahmet Öztürk (dmxe) wrote :

Hello Michael,

I did some experiments with the diary file you shared but couldn't crash Lifeograph by deleting an entry.

Could you please specify, the version of Lifeograph you are using as well as the operating system your operating system.

It will also help if you could specify the steps you are taking in the example diary until it crashes.

As to drag and drop, you need to look carefully at where the insertion line appears. To move an entry up to its parent's level you can drag it onto its parent and find the sweet spot where a single line appears under the parent and drop there. Be careful that the line is below the parent and not above the first child, or the entry will just be shifted to the first position under its parent.

Revision history for this message
Michael Waldor (olwaldi) wrote :

Thanks for looking into my finding...

I'm running the latest release 2.01 within the most recent linux (tumbleweed). I've compiled it on my own following your README.

The main problem was the "magical" ubwanted change from free entries into numbered ones. Or is the topmost entry semi-automatically a numbered one?

Maybe my crash has to do with my try to remove an unwanted entry. I could reproduce it by the following actions (as far as I remember). Create a new entry, modify it, so that it appears within the table. Mark the entry with the waste bin, use the drop down menue to finally remove it. It's still within the table, and lifeograph crashes when I click onto the deleted entry within table.

Revision history for this message
Ahmet Öztürk (dmxe) wrote :

OK, on entry deletion, the table was not updating. I have fixed that now in master. You can clone the git repo, build again, and test it right away.

On the other hand, it is still not clear to me how the types of entries are changing. If you can describe the steps to reproduce it, I will look into it, too.

Changed in lifeograph:
status: New → Triaged
Revision history for this message
Michael Waldor (olwaldi) wrote :

As of now lifeograph works for me fine. I have entered all my hiking tours from the last 3 years without crash.

Currently I do not try to reorganize the entries due to my bad experience. Maybe the complete corruption of all entries was triggered by some misuse from my side due to my lack of experience with your tool. As I wrote above I did create some entries, marked them with the waste bin, played around with table. And suddenly many entries have changed their order and their type from temporal into numbered. I could recover by dragging those entries back and forth.

Maybe it was a cut&paste error? I use the entry wanderungen as a kind of template. I copy it into new, empty entries. Maybe the focus was not as expected, and the paste did cause my trouble.

I'll come back to this bug if I'll might encounter it again. Maybe as a suggestion howto ease error debugging in the future: you might enhance lifeotab by logging all user interactions of one session within a logfile for later inspection. But that logfile might become quite huge over time.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.