Comment 1 for bug 792118

Thanks for reporting this bug.

I could reproduce the issue on my computer. It seems that a file in the diodon history is not available anymore and then causes diodon to start.

Such entries should actually be ignored during start up.