Re: [Evolution] Accessing IMAP folder puts Evo into endless loop

Ok, here is what I get.  To reproduce for me is extremely easy and 100%
1.  Click on IMAP folder root
2.  Enter password
3.  Click on Inbox

Here's the last bit of output and a backtrace when I do this:

utf8_to_gtk: Body or subject contains => Body or subject contains
utf8_to_gtk: Body contains => Body contains
utf8_to_gtk: Subject contains => Subject contains
utf8_to_gtk: Body does not contain => Body does not contain
utf8_to_gtk: Subject does not contain => Subject does not contain
utf8_to_gtk: Sender contains => Sender contains
utf8_to_gtk: Advanced... => Advanced...
utf8_to_gtk: Show All => Show All
utf8_to_gtk: Save As... => Save As...
utf8_to_gtk: Store search as vFolder => Store search as vFolder
utf8_to_gtk: Edit... => Edit...
sending : A00006 SELECT "INBOX"

Bonobo-CRITICAL **: file bonobo-ui-component.c: line 829 (impl_xml_rm):
assertion `container != CORBA_OBJECT_NIL' failed.

Bonobo-CRITICAL **: file bonobo-ui-component.c: line 829 (impl_xml_rm):
assertion `container != CORBA_OBJECT_NIL' failed.
received: * NO Trying to get mailbox lock from process 13442
received: * 12 EXISTS
received: * NO Mailbox vulnerable - directory must have 1777 protection
received: * 0 RECENT
received: * OK [UIDVALIDITY 957803161] UID validity status
received: * OK [UIDNEXT 5171] Predicted next UID
received: * FLAGS (\Answered \Flagged \Deleted \Draft \Seen)
received: * OK [PERMANENTFLAGS (\* \Answered \Flagged \Deleted \Draft
\Seen)] Permanent flags
received: A00006 OK [READ-WRITE] SELECT completed
sending : A00007 UID FETCH 1:5162 (FLAGS)
received: * 1 FETCH (UID 2263 FLAGS (\Seen \Answered))
received: * 2 FETCH (UID 3542 FLAGS (\Seen))
received: * 3 FETCH (UID 3616 FLAGS (\Seen \Answered))
received: * 4 FETCH (UID 4295 FLAGS (\Seen \Answered))
received: * 5 FETCH (UID 4307 FLAGS (\Seen))
received: * 6 FETCH (UID 4842 FLAGS (\Seen))
received: * 7 FETCH (UID 4870 FLAGS (\Seen \Answered))
received: * 8 FETCH (UID 4871 FLAGS (\Seen \Answered))
received: * 9 FETCH (UID 4877 FLAGS (\Seen \Answered))
received: * 10 FETCH (UID 5119 FLAGS (\Seen))
received: * 11 FETCH (UID 5128 FLAGS (\Seen))
received: A00007 OK UID FETCH completed
got folder 'imap://dhensley mail xxxxxxxxxxxx com/INBOX' = 0x8215d18
Received Interrupt in LWP 6359 while waiting for SIGSTOP.
Received Interrupt in LWP 6312 while waiting for SIGSTOP.

Program received signal SIGINT, Interrupt.
[Switching to Thread 3076 (LWP 6361)]
0x40a53362 in sigsuspend () from /lib/
(gdb) bt
#0  0x40a53362 in sigsuspend () from /lib/
#1  0x406d7bc0 in __pthread_wait_for_restart_signal (self=0xbf3ffc00)
    at pthread.c:934
#2  0x406d3e8c in pthread_cond_wait (cond=0x811b588, mutex=0x811b568)
    at restart.h:34
#3  0x40069527 in e_msgport_wait (mp=0x811b540) at e-msgport.c:193
#4  0x40069c9f in thread_dispatch (din=0x811b4f0) at e-msgport.c:514
#5  0x406d4f54 in pthread_start_thread_event (arg=0xbf3ffc00) at

I don't know if this backtrace helps.  Do I need to get the other
threads as well?


On 27 Jun 2001 01:13:42 -0400, Peter Williams wrote:
Hi Dan,

On 26 Jun 2001 22:36:50 -0600, Dan Hensley wrote:
I sent this out several days ago but still haven't seen a response, and
the problem still exists.  When I click on the Inbox of my IMAP folder,
Evolution goes into an endless loop that uses 100% CPU and never comes
back.  Here's the last bit out output from evolution-mail, which
probably doesn't help much.  I doctored it up a bit to protect my

Can you please:

1) Open up 2 terminals
2) Run 'gdb evolution-mail' in one terminal and 'run' it
3) Wait five seconds
4) Run 'evolution' in the other terminal
5) Cause the infinite loop
6) Press ^C in the gdb
7) Get a backtrace with 'bt'

? That would be helpful.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]