Comment 1 Dirk-Jan C. Binnema 2008-02-22 08:29:07 UTC

ok... can you give some information about the accounts you've been using?

also, starting from the commandline ('modest showui') might give some valuable
output.

ah, yes. Two IMAP accounts with SSL, both seem to work fine. Nothing seems out
of the ordinary, except that one account keeps saying "Last updated: Never",
when in fact it gets updated just like the other account.

"modest showui" printed nothing... except that during this testing I managed to
segfault it for the first time: no idea if it is connected to this bug report
here. I had been using the UI for several minutes when it happened. I believe I
was just changing folders with arrow keys. Nothing in xterm, except
"segmentation fault"

I didn't notice this at first, but it seems that every time there is a
"Internal Error" dialog, there's also a "Connection to one or more accounts
lost" notification.

I'm having similar behaviour. I've got a gmail account (imap) and an ssl imap
account. I cant see that it correlates with having a connection or not, but I
haven't been paying that much attention. Ill try to make a note of it in the
future.

Receiving error "Application Email has closed" Seems to happen when modest is
automatically polling for new messages. IMAP accounts with SSL

This is getting pretty annoying: unless there are new debug requests, I'll try
to get rid of the problem by re-install/purging Modest... Let me know ASAP if
there are.

Same here, different release

After the last Modest upgrade (1.0-2008.12-1) I've been getting "Internal
error: application E-mail closed" popups. This has happened again after
rebooting. Often several popups come up one after the other. So far popups have
always appeared when device was idle, with Modest not running.

This has happened when Modest had not been started at all after a reboot. I
have never started the official email app.

I cannot really reproduce this, but it's happened several times over several
reboots, so I'm filing it too.

Using one IMAP account with SSL.

Comment 8 Dirk-Jan C. Binnema 2008-03-26 08:36:30 UTC

we're working on this...

(In reply to comment #6)
> This is getting pretty annoying: unless there are new debug requests, I'll try
> to get rid of the problem by re-install/purging Modest...

Apparently threats worked... I haven't seen any Internal error dialogs in about
two weeks. so WORKSFORME here, leaving open in case others are still seeing it.

Comment 10 Alan Bruce 2008-04-17 20:50:42 UTC

I am still getting this error in W15, although not as frequently as I did in
previous releases.

Comment 11 Eric Warnke 2008-05-02 17:58:42 UTC

Just the other day 17-2 started throwing these messages again.  I have no
changed anything knowingly on this system that might have caused this issue.

I'm also have been experiencing this error with 1.0-2008.19-1.

I haven't seen an "Internal error: application E-mail closed" popup from I am
using Diablo (and the diablo modest version) (about ~ 10 days).

software version 2.2007.51-3.

Running a private opensource imap server (hmailserver) and getting "Internal
error: application E-mail closed" since first tested modest version (V10).
Problem is persisten till the current one version (V22).

Latly I realized, that if i delete the local cache
(/home/user/.modest/cache/mail/imap/imap__account) modest will start normally
again. It will re-read the imap folders and the messages with the correct
status flags (read).
When modest is closed and a new message waits on the server, modest will crash
when it queries for new mails with the message described above.
If I delete the cache again, and startup modest, the new message is received
without a problem. 
Every is working fine until the next message arrives.

Comment 15 Neil MacLeod 2008-07-01 23:11:54 UTC

I'm getting this on Diablo 4.2008.23-14 on N810, Modest configured with a
single POP server using non-authenticated incoming, authenticated (Normal TLS)
outgoing. I usually pick up the device in the morning (it has a stable WiFi 11g
connection, Linksys WRT54GS) to find Modest has crashed with the "internal
error" dialog.

(In reply to comment #15)
> I'm getting this on Diablo 4.2008.23-14 on N810, Modest configured with a
> single POP server using non-authenticated incoming, authenticated (Normal TLS)
> outgoing. I usually pick up the device in the morning (it has a stable WiFi 11g
> connection, Linksys WRT54GS) to find Modest has crashed with the "internal
> error" dialog.
> 

I too find the device in the morning with Modest crashed with the internal
error dialog.
This is happening every morning.
I usually had only Gmail over IMAP, now I have also my own university mail
server (IMAP/SSL) configured.

Looks like it happens only when the GUI is off.

Comment 17 Andre Klapper 2008-08-04 16:45:25 UTC

OK, let's try to track this down, though I can imagine several different issue
behind this.

Can you please run Modest in a terminal window (Applications Menu -> Utilities
X Terminal, then enter the command "maemo-summoner /usr/bin/modest.launch
showui
 > log 2>&1" and hit the Enter key) and attach the resulting log file here
after it has crashed?

Having a core dump could be even more useful. It requires installing the
"sp-rich-core" package from the tools repository[1] and creating a "core-dumps"
directory to the memory card with at least few megabytes of free space.

[1] http://maemo.org/development/tools/


I also wonder whether somebody of you also ran into bug 3357 (Modest lingers in
memory using 100% CPU)?

Created an attachment (id=856) [details]
log file

Attaching modest log. Log copied after acknowledging three "internal error"
dialogs.

command line:
maemo-summoner /usr/bin/modest.launch > /media/mmc2/modest-log 2>&1

Created an attachment (id=857) [details]
core dump

re comment 18: actually, there probably were only two dialogs since I see two
core dumps. Only attaching the first one (let me know if you need more, I'm
sure I've got nice collection soon...).

This problem was been fixed a couple of weeks ago. The fix would be available
in the next Modest release. The problem was inside tinymail. The g_atexit
handler was calling PR_Cleanup. This Mozilla function is so highly unreliable,
that nor even the firefox guys use it now. When we removed that from tinymail
code, the crashes caused by the auto-update feature disappeared completely. So
be patient for the next Modest release :)

Comment 21 Andre Klapper 2008-08-07 15:32:15 UTC

Sergio, thanks for the explanation!

Closing as per last comment. Anybody of the reporters/voters please reopen this
bug if you can still reproduce this issue after installing the next (upcoming)
version of modest.

Thanks!

Comment 22 Andre Klapper 2008-08-14 16:20:08 UTC

Setting Target Milestone correctly to 4.1.1 (corresponding to 4.2008.30-2).