---- Reported by jim@yorba.org 2013-03-28 11:57:00 -0700 ----

Original Redmine bug id: 6698
Original URL: http://redmine.yorba.org/issues/6698
Searchable id: yorba-bug-6698
Original author: Jim Nelson
Original description:

Adam first reported this to me, and now this morning I've seen it as well. I
received an email and the notification bubble popped up. I went to Geary but
the message was not displayed. Even after waiting, the message never arrived.
Finally, I switched to another Inbox and then back and the message appeared in
the list.

In the console I saw no warning messages at all, everything seemed to be
working fine. I could see when the notification was made and even the
prefetcher pulling in the entire message. It looks like there's some code path
where either (a) a new message is not added in the ConversationMonitor or (b)
a new conversation is not added to the code list.

The relevant portion of the log:

    
    
     [deb] 11:37:24 imap-engine-generic-folder.vala:444: Opening remote Gmail account jimbonator@gmail.com:[Gmail]/All Mail
     [deb] 11:37:26 imap-engine-generic-folder.vala:106: normalize_folders Gmail account jimbonator@gmail.com:[Gmail]/All Mail
     [deb] 11:37:30 imap-client-session.vala:1355: [ClientSession:0013/74.125.25.108:993/GEARY_IMAP_CLIENT_CONNECTION_STATE_IDLING] SOLICITED EXISTS 77554
     [deb] 11:37:30 imap-client-session.vala:1355: [ClientSession:000D/74.125.129.109:993/GEARY_IMAP_CLIENT_CONNECTION_STATE_IDLE] UNSOLICITED EXISTS 71
     [deb] 11:37:30 imap-engine-generic-folder.vala:606: on_remote_messages_appended: total=71
     [deb] 11:37:30 imap-engine-generic-folder.vala:618: do_replay_appended_messages Gmail account jim@yorba.org:INBOX: remote_count=70 new_remote_count=71
     [deb] 11:37:31 imap-engine-generic-folder.vala:642: do_replay_appended_messages: 1 new messages from 71 in Gmail account jim@yorba.org:INBOX
     [deb] 11:37:31 geary-conversation-monitor.vala:723: 1 message(s) appended to Gmail account jim@yorba.org:INBOX, fetching to add to conversations...
     [deb] 11:37:31 imap-engine-generic-folder.vala:687: do_replay_appended_messages: completed for Gmail account jim@yorba.org:INBOX
     [deb] 11:37:31 unity-launcher.vala:44: set unity launcher entry count to 1
     [deb] 11:37:31 new-messages-monitor.vala:149: do_process_new_email: 1 messages listed, 1 unread in folder Gmail account jim@yorba.org:INBOX
     [deb] 11:37:32 imap-engine-email-prefetcher.vala:193: do_prefetch_batch Gmail account jim@yorba.org:INBOX 1
     [deb] 11:37:32 imap-engine-email-prefetcher.vala:236: finished do_prefetch_batch Gmail account jim@yorba.org:INBOX total=1 skipped=0
     [deb] 11:38:25 geary-controller.vala:371: Folder Gmail account jimbonator@gmail.com:INBOX selected
     [deb] 11:38:25 geary-controller.vala:429: switching to Gmail account jimbonator@gmail.com:INBOX
    

At the top, note that the account synchronizer was fetching from my other
account's All Mail. It appears while that was happening a message came in on
All Mail (from the number in the first EXISTS message) followed by the new
mail in my work Inbox. The last two lines are from waiting and then switching
to the other account's Inbox.

Related issues:
related to geary - 7392: [norepro] Geary fails to download message in my
Inbox (Invalid)



---- Additional Comments From geary-maint@gnome.bugs 2013-10-03 17:52:00 -0700 ----

### History

####

#1

Updated by Adam Dingle 8 months ago

I've seen this bug many times, at least 5 times in the past week or two. Glad
you now know I wasn't making that up. :)

####

#2

Updated by Jim Nelson 8 months ago

  * **Assignee** set to _Eric Gregory_

####

#3

Updated by Eric Gregory 8 months ago

I've created a branch at bug/6698-email-not-listed that has some extra debug
printfs. My thinking right now is the ConversationListStore has a number of
places where we back out of inserting a message if various conditions aren't
met; this branch logs those situations.

If one of you guys experiencing this issue could test with this branch, we
should be able to at least narrow down the problem.

####

#4

Updated by Eric Gregory 8 months ago

Okay, disregard the above; the extra debug logging is now in master.

####

#5

Updated by Eric Gregory 8 months ago

  * **Status** changed from _Open_ to _Need Information_

####

#6

Updated by Adam Dingle 8 months ago

I still see this very often, numerous times every day. I'll start running
Geary from the console always so that I can look at the debug output if/when
this happens again. Is that good enough? Or do I need to run Geary with an
option to enable extra logging in some way?

####

#7

Updated by Charles Lindsay 7 months ago

  * **Target version** changed from _0.3.1_ to _0.4.0_

####

#8

Updated by Jim Nelson 7 months ago

Adam, I must have missed your questions. As long as you run Geary with the
--debug option and save the log output when you see the problem, that will
help us.

####

#9

Updated by Adam Dingle 7 months ago

I still see this bug very often, maybe 5-10 times every day. I had forgotten
that you guys were waiting for logging information from me. I'll start running
Geary with --debug all the time and hope to get you some log information in
the next few days.

####

#10

Updated by Adam Dingle 7 months ago

  * **File** geary.log added

OK, so this bug just occurred while I was running

$ geary --debug | tee geary.log

I immediately exited Geary. Here's the log file - does this help in any way?

####

#11

Updated by Jim Nelson 7 months ago

  * **Status** changed from _Need Information_ to _Open_

It does, Adam. From the log I can see that the ConversationMonitor is
reporting to the client that messages have been appended to an existing
conversation. The client does have that conversation in its store, so it drops
the notification on the floor.

Although I'm not sure yet what exactly the bug is, this pinpoints the problem.
Hopefully we can have this fixed soon.

####

#12

Updated by Jim Nelson 7 months ago

  * **Assignee** changed from _Eric Gregory_ to _Jim Nelson_

I have some ideas about this one, so assigning to myself.

####

#13

Updated by Jim Nelson 7 months ago

  * **Status** changed from _Open_ to _Fixed_

Applied in changeset 557ae84dccb4ffd5980d093f59929ebd03906e52.

####

#14

Updated by Jim Nelson 7 months ago

Adam, please let me know if you still see this. Once I understood the issue I
was able to reproduce it. If you see it again, a log would still be helpful.

####

#15

Updated by Adam Dingle 6 months ago

This bug is not fixed, alas: I still see this all the time. Please reopen.
I'll start running with --debug again and will send another log the next time
this occurs.

####

#16

Updated by Adam Dingle 6 months ago

  * **File** geary.log added

OK, this just happened again - that didn't take long. :) Here's the log file.
As always, this happened when a new message arrived in a conversation I had
already archived in the current Geary session.

####

#17

Updated by Charles Lindsay 6 months ago

  * **Status** changed from _Fixed_ to _Open_

####

#18

Updated by Adam Dingle 6 months ago

Still seeing this often.

####

#19

Updated by Jim Nelson 6 months ago

The prior patch dealt with archives messages keeping the Conversation
lingering in the ConversationMonitor even though it's reported as removed.
This new patch deals with a related problem: references to messages the user
did not receive causing the Conversation object to linger in the
ConversationMonitor.

Adam, I will be closing this. If you continue to see this problem (I hope you
don't!) please re-open and let us know.

####

#20

Updated by Jim Nelson 6 months ago

  * **Status** changed from _Open_ to _Fixed_

Applied in changeset 3e8618dcdac4e670dfb4cf29e4228f341eeef749.

####

#21

Updated by Adam Dingle 4 months ago

  * **Status** changed from _Fixed_ to _Open_

This bugbear is back: I've seen this happen a couple of times today. I'll
start running with --debug once again to try to catch this in the act.

####

#22

Updated by Adam Dingle 4 months ago

I just saw this again, but unfortunately wasn't storing debug output to a
file. Here's what happened:

1. A new message arrived. I saw a popup notification, but there was no sign of
the message in my Inbox. The message definitely did not belong to any
conversation I had read or archived today.

2. A second new message arrived. I saw a notification, and this message showed
up in my Inbox normally. The first message was still absent from the Inbox.

3. I restarted Geary. As expected, both messages were visible in my Inbox.

I really will start logging now. :)

####

#23

Updated by Jim Nelson 4 months ago

Thanks, that really will help us with this.

####

#24

Updated by Charles Lindsay 4 months ago

  * **Status** changed from _Open_ to _Need Information_

Adam, my fix to #7096 might affect this as well. Please let us know if you can
make this happen again with the latest in master.

####

#25

Updated by Jim Nelson 3 months ago

  * **Status** changed from _Need Information_ to _Open_

####

#26

Updated by Jim Nelson 2 months ago

Adam, have you seen this recently?

####

#27

Updated by Charles Lindsay about 1 month ago

  * **Target version** changed from _0.4.0_ to _0.5.0_



--- Bug imported by chaz@yorba.org 2013-11-21 23:11 UTC  ---

This bug was previously known as _bug_ 6698 at http://redmine.yorba.org/show_bug.cgi?id=6698
Imported an attachment (id=261142)
Imported an attachment (id=261143)

Unknown milestone "unknown in product geary. 
   Setting to default milestone for this product, "---".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Resolution set on an open status.
   Dropping resolution