GNOME Bugzilla – Bug 714833
Conversation not shown ("Message nnnn only fulfills 21Fh fields (required: 37Fh)")
Last modified: 2018-01-09 23:25:29 UTC
---- Reported by jim@yorba.org 2013-03-18 10:52:00 -0700 ---- Original Redmine bug id: 6604 Original URL: http://redmine.yorba.org/issues/6604 Searchable id: yorba-bug-6604 Original author: Jim Nelson Original description: I have a conversation in my Inbox that Geary won't display when I select it. When I do select it, this appears in the console: [deb] 10:49:16 db-connection.vala:351: Connection.exec_transaction: transaction threw error: Message 30558 only fulfills 21Fh fields (required: 37Fh) [deb] 10:49:16 db-transaction-async-job.vala:42: AsyncJob: transaction completed with error: Message 30558 only fulfills 21Fh fields (required: 37Fh) [deb] 10:49:16 geary-controller.vala:636: Unable to show message: Message 30558 only fulfills 21Fh fields (required: 37Fh) Note that this conversation may include archived messages. Related issues: related to geary - 7274: no conversations accessible after search matches no messages (Fixed) related to geary - 6754: can't read certain conversations: message area empty (Open) ---- Additional Comments From geary-maint@gnome.bugs 2013-09-23 14:42:00 -0700 ---- ### History #### #1 Updated by Jim Nelson 8 months ago * **Target version** changed from _0.3.0_ to _0.4.0_ #### #2 Updated by Charles Lindsay 7 months ago This was just reported at https://bugs.launchpad.net/geary/+bug/1168515, so it appears not to be fixed. #### #3 Updated by Charles Lindsay 7 months ago I got this a couple times this morning, after having switched folders a number of times when I first created my account last night. Blowing away my database fixed it. This would seem to suggest that it's caused by the database getting into an inconsistent state due to some user action. Maybe a particular write outside of a transaction is being interrupted when you switch folders? #### #4 Updated by Eric Gregory 7 months ago I just saw this one too. I deleted my DB and tried to see if I could reproduce the problem. Instead I saw something slightly different -- I couldn't load all the mail in the folder. When I tried to scroll down to see if I could load all the messages in the offending coversation, the "load more" operation failed and spat out the following: [deb] 18:23:56 geary-controller.vala:552: on_load_more [deb] 18:23:56 imap-engine-replay-queue.vala:260: Replay local error for [7325] ListEmailByID: low=0 count=-200 required_fields=29Fh local_only=false remote_only=false initial_id=4703 excl=true on FooBar: Email ID 4703 in Gmail account eric@yorba.org:FooBar not known to local store [deb] 18:23:56 geary-conversation-monitor.vala:527: Error while assembling conversations in Gmail account eric@yorba.org:FooBar: Email ID 4703 in Gmail account eric@yorba.org:FooBar not known to local store [deb] 18:23:56 geary-controller.vala:563: on load more completed [deb] 18:23:56 geary-controller.vala:567: Error, unable to load conversations: Email ID 4703 in Gmail account eric@yorba.org:FooBar not known to local store #### #5 Updated by Jim Nelson about 1 month ago * **Target version** changed from _0.4.0_ to _0.5.0_ We haven't seen the symptoms of this bug recently (conversation not being displayed), although it's quite possible the underlying problem remains. We need to investigate the code paths leading to this warning message and see if any could trigger this problem, especially in the Search folder, which doesn't go out to network to pull in additionally needed fields. --- Bug imported by chaz@yorba.org 2013-11-21 23:11 UTC --- This bug was previously known as _bug_ 6604 at http://redmine.yorba.org/show_bug.cgi?id=6604 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
I don't think I have ever seen this, so resolving as incomplete until some evidence that it is still a problem pops up.