Re: nnimap against Cyrus imapd just stopped working

[Steinar Bang <sb@dod.no>]

>>>>> Steinar Bang <sb@dod.no>:

>>>>> Steinar Bang <sb@dod.no>:
>>>>> Steinar Bang <sb@dod.no>:
>>>>> Steinar Bang <sb@dod.no>:
>>>>> Steinar Bang <sb@dod.no>:
>>>> [snip!]
>>>>> Sigh!  Unless someone knows something clever, I guess this means I
>>>>> have a *seriously* trashed .newsrc.eld file, and the only way out of
>>>>> this is to create a new one from scratch?

>>>> Hm... the problem may not be in the ~/.newsrc.eld at all.  I moved
>>>> away the existing ~/.newsrc.eld, and the problem still persists.

>>>> Below are the contents of the *Messages* buffer after a startup that
>>>> ends with emacs displaying the *Group* buffer after the beep.

>>> I set (setq debug-on-error t) and started Gnus in a fresh emacs.  This
>>> is the backtrace I got:

>>> Signaling: (wrong-type-argument stringp nil)
>>> intern(nil [0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0])
>>> imap-mailbox-put(permanentflags nil)
>>> imap-parse-resp-text-code()
>>> imap-parse-resp-text()
>>> imap-parse-response()
>>> imap-arrival-filter(#<process imap<1>> "* FLAGS (\\Answered \\Flagged \\Draft \\Deleted \\Seen)\r\n* OK [PERMANENTFLAGS ()]  \r\n* 0 EXISTS\r\n* 0 RECENT\r\n* OK [UIDVALIDITY 1025304220]  \r\n* OK [UIDNEXT 2]  \r\n6 OK [READ-ONLY] Completed\r\n* FLAGS (\\Answered \\Flagged \\Draft \\Deleted \\Seen)\r\n* OK [PERMANENTFLAGS ()]  \r\n* 16071 EXISTS\r\n* 16071 RECENT\r\n* OK [UNSEEN 1]  \r\n* OK [UIDVALIDITY 1]  \r\n* OK [UIDNEXT 16082]  \r\n7 OK [READ-ONLY] Completed\r\n8 NO Mailbox does not exist\r\n* FLAGS (\\Answered \\Flagged \\Draft \\Deleted \\Seen)\r\n* OK [PERMANENTFLAGS ()]  \r\n* 0 EXISTS\r\n* 0 RECENT\r\n* OK [UIDVALIDITY 1026364784]  \r\n* OK [UIDNEXT 1]  \r\n9 OK [READ-ONLY] Completed\r\n* FLAGS (\\Answered \\Flagged \\Draft \\Deleted \\Seen)\r\n* OK [PERMANENTFLAGS ()]  \r\n* 0 EXISTS\r\n* 0 RECENT\r\n* OK [UIDVALIDITY 1026198897]  \r\n* OK [UIDNEXT 1]  \r\n10 OK [READ-ONLY] Completed\r\n11 NO Mailbox does not exist\r\n* FLAGS (\\Answered \\Flagged \\Draft \\Deleted \\Seen)\r\n* OK [PERMANENTFLAGS ()]  \r\n* 385 EXISTS\r\n* 385 RECENT\r\n* OK [UNSEEN 1]  \r\n* OK [UIDVALIDITY 856603065]  \r\n* OK [UIDNEXT 11839]  \r\n12 OK [READ-ONLY] C")

>>> Is the second argument to imap-mailbox-put the cause behind the 
>>> error in process filter: Wrong type argument: stringp, nil [2 times]
>>> message?

>>> What is the second argument to imap-mailbox-put?  C-h f imap-mailbox-put RET
>>> gives the following message:
>>> imap-mailbox-put is a compiled Lisp function in `imap'.
>>> (imap-mailbox-put PROPNAME VALUE &optional MAILBOX BUFFER)
>>> not documented

>>> Not very useful on what VALUE is.

>> I tried edebug-defun on imap-mailbox-put, but I got the beep and the
>> error message without the debugger being entered.

> I have now tried edebug-defun on all functions on the stack about.  I
> tried each of them in a fresh emacs.  None of them caused emacs to
> enter the debugger.

Now I have removed ~/News/overview/ but the problem still persists.

Help! :-/ 

Are the running gnus-slave processes causing problems?  I don't want
to stop this emacs process, because then I can't post to this group.
I don't want to stop the remote login process, because nnimap mail
still works in this process.

This latest thing is the biggest weirdness, because it seems to rule
out problems in the IMAP daemon, and problems in the Gnus
installation, or the Gnus config.  Nothing has changed in the Gnus
config lately.

Since the error message occurs just after the loading of gnus-topic,
can the problem have something to do with topics?  Do topics have some
persistence stored in files other than  ~/.newsrc.eld?