A couple of days ago I checked my emails with Modest. After clicking on one of the freshly downloaded emails, Modest tried to open the Email. Somehow it got stuck during the opening process. Now even a couple of days later, it won't check Emails anymore automatically, and every time I open the application myself, at the bottom of the screen it is still displaying that it tries to open the Email. And it does not respond if I click on "cancel". It won't even stop if I switch the device off and on again. I tried to kill the application via the console, but I couldn't figure out which process it was.
Modest seems to be trapped in some king of "never ending loop" while trying to open my emails. This alone is a serious bug, but it became unacceptable because I couldn't restart the programm by restarting maemo. Modest works with suspend-to-ram when switching off the device and thereby preserves this loop.
I couldn't find the name of the related process, so I couldn't kill Modest manually. However I managed to produce a segementation fault by starting "modest.launch" in xterm. That killed Modest and I was able to make a clean restart of Modest.
However this tinkered solution makes me feel like I'm a bulgarian motor mechanic.
A couple of days ago I checked my emails with Modest. After clicking on one of the freshly downloaded emails, Modest tried to open the Email. Somehow it got stuck during the opening process. Now even a couple of days later, it won't check Emails anymore automatically, and every time I open the application myself, at the bottom of the screen it is still displaying that it tries to open the Email. And it does not respond if I click on "cancel". It won't even stop if I switch the device off and on again. I tried to kill the application via the console, but I couldn't figure out which process it was.
What do you suggest as a solution?
Do you know what Modest's process handle is?
Tim