[sylpheed:34961] Re: 3.2.0 beta 4: another command is already running
Hiroyuki Yamamoto
hiro-y at kcn.ne.jp
Mon Dec 19 10:43:29 JST 2011
Hello,
On Sat, 17 Dec 2011 19:24:36 +0400
Anton Shepelev <anton.txt at gmail.com> wrote:
> With my Gmail IMAP account, Sylpheed has been crash-
> ing periodically when I opened a message with a huge
> attachment. If I restart Sylpheed and try to open
> that message again, it silently refuses to load it
> showing a blank Message View (screenshot attached).
> This problem is not new in 3.2.0 beta 4.
It is because of a corrupted message cache. Please update caches by
'View - Update summary' to remove it.
> Here's the relevant fragment of the log file:
>
> [18:18:52] IMAP4< 1911 OK Success
> [18:20:02] IMAP4> 1912 NOOP
> [18:20:03] IMAP4< 1912 OK Success
> [18:20:03] IMAP4> 1913 UID FETCH 15424 BODY.PEEK[]
> [18:20:05] IMAP4< * 1761 FETCH (UID 15424 BODY[] {10429052}
> [18:21:50] ** LibSylph-WARNING: imap_cmd_gen_send: cannot send command because another command is already running.
> [18:21:50] ** LibSylph-WARNING: [18:21:50] IMAP4 connection to imap.gmail.com has been disconnected. Reconnecting...
>
> [18:21:50] ** warning: IMAP4 connection to imap.gmail.com has been disconnected. Reconnecting...
> [18:21:50] * message: creating IMAP4 connection to imap.gmail.com:993 ...
> [18:21:55] IMAP4< * OK Gimap ready for requests from 95.72.205.226 z13if9798135wei.76
> [18:21:55] ** LibSylph-WARNING: imap_cmd_gen_send: cannot send command because another command is already running.
>
> This error (cannot send command because another com-
> mand is already running) is said to have been fixed
> in beta 4, but it doesn't seem to be so...
I'll look into that again.
> Another way to cause the same error is to start
> opening a huge message over IMAP and then press the
> "Go Offline" icon.
--
Hiroyuki Yamamoto <hiro-y at kcn.ne.jp>
More information about the Sylpheed
mailing list