VM

assertion failed in vm-imap-end-session

Bug #544873 reported by Uday Reddy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
VM
Invalid
Low
Uday Reddy

Bug Description

The backtrace below shows an assertion failed error in vm-imap-end-session. Checking the values of variables shows that vm-imap-session-done is t, but vm-imap-session-type is 'active.

Debugger entered--Lisp error: (error "assertion failed: (eq vm-imap-session-type type)")
  signal(error ("assertion failed: (eq vm-imap-session-type type)"))
  error("assertion failed: %S" (eq vm-imap-session-type type))
  vm-imap-end-session(#<process IMAP>)
  vm-establish-new-folder-imap-session(t)
  vm-imap-synchronize-folder(t nil t t t t)
  vm-get-spooled-mail(t)
 ------
IMAP session log:

starting IMAP session Tue Mar 23 00:04:32 2010
connecting to localhost:143
connected
* OK IMAP4 Ready imap 0001cdf3

VM CAPABILITY

* CAPABILITY IMAP4 IMAP4REV1

VM OK CAPABILITY

VM LOGIN <parameters omitted>

VM OK Logged in.

VM SELECT "INBOX"

* FLAGS (\Answered \Flagged \Deleted \Seen \Draft forwarded filed redistributed ! $Forwarded 7350 7354 7391 signed * accept action plagiarism Junk NonJunk !@)

* OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft forwarded filed redistributed ! $Forwarded 7350 7354 7391 signed * accept action plagiarism Junk NonJunk !@ \*)] Flags permitted.

* 3379 EXISTS

* 0 RECENT

* OK [UIDVALIDITY 1217243146] UIDs valid

* OK [UIDNEXT 24074] Predicted next UID

VM OK [READ-WRITE] Select completed.

VM LOGOUT

Tags: imap
Uday Reddy (reddyuday)
Changed in vm:
status: New → Confirmed
importance: Undecided → Low
assignee: nobody → Uday Reddy (reddyuday)
milestone: none → 8.2.0-devo
tags: added: imap
Uday Reddy (reddyuday)
Changed in vm:
milestone: 8.2.0-devo → 8.1.91a
Uday Reddy (reddyuday)
Changed in vm:
status: Confirmed → Triaged
Revision history for this message
Uday Reddy (reddyuday) wrote :

This not reproducible any more.

Changed in vm:
status: Triaged → Incomplete
Uday Reddy (reddyuday)
Changed in vm:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.