Thanks very much for the complete report. It shows that you are running the right version of gpesummary and libeventdb2. And nothing unusual in options (I have set mine to match to see if I can reproduce the problem at all).

I really need to reproduce the problem. If you see it again please take note of anything you think might be relevant. And, if it does crash again, please take a copy of your calendar and todo databases (in /home/user/.gpe) before starting gpesummary again (if gpe-calendar or gpe-todo are running, do not close them before copying the database files). If you do see it again I can send you a special version of gpesummary which writes logs to a file in /tmp.

Thanks for taking the time to report the problem, Derek, and I am very sorry it is waking you up in the middle of the night! Just to be clear, was gpe-calendar running at the time of the problem or was it started automatically by gpesummary? If gpe-calendar was running, is it possible that the time they went off was (some exact multiple of) 24 hours after you last started gpe-calendar?

I will contact you off-line to ask you to send me your calendar database, if you are willing.

Graham