After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 720942 - Error while Unknown background operation.
Error while Unknown background operation.
Status: RESOLVED DUPLICATE of bug 767564
Product: evolution
Classification: Applications
Component: Mailer
3.10.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2013-12-22 17:49 UTC by Hans Petter Jansson
Modified: 2016-08-12 16:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Hans Petter Jansson 2013-12-22 17:49:29 UTC
I had left Evolution in offline mode and was working in another workspace when a notification popped up that I had received a new mail (judging by the sender and subject, it was from a mailing list -- I'm hard pressed to find it again, since it probably went to the corresponding mailing list folder).

I clicked on the "Go to inbox" option offered by the notification, and when I checked Evolution, it was showing a blue ribbon saying:

"Error while Unknown background operation." There was something about one of my filters not being able to run in offline mode (I don't have the precise wording anymore, since the ribbon seems to have disappeared while I was typing this).

It seemed odd that mail would arrive while in offline mode, and that it would not be possible to apply filters to it when it did.

I doubt it's rule-specific, but in any case, the failed rule looks like this:

    <rule enabled="true" grouping="any" source="incoming">
      <title>SPAM</title>
      <partset>
        <part name="header">
          <value name="header-field" type="string">
            <string>X-Spam-Status</string>
          </value>
          <value name="header-type" type="option" value="contains"/>
          <value name="word" type="string">
            <string>Yes,</string>
          </value>
        </part>
        <part name="header">
          <value name="header-field" type="string">
            <string>X-Spam-Flag</string>
          </value>
          <value name="header-type" type="option" value="is"/>
          <value name="word" type="string">
            <string>YES</string>
          </value>
        </part>
      </partset>
      <actionset>
        <part name="move-to-folder">
          <value name="folder" type="folder">
            <folder uri="email://local@local/Spam"/>
          </value>
        </part>
        <part name="stop"/>
      </actionset>
    </rule>
Comment 1 Hans Petter Jansson 2014-01-04 15:04:35 UTC
I'm also getting these occasionally, even when working online:

Execution of filter 'SPAM' failed: Empty cache file: /home/hpj/.cache/evolution/mail/1122844282.10563.0@avarice.monx/folders/INBOX/cur/24/1299397

I don't know if it's related or not.
Comment 2 Milan Crha 2014-02-05 17:24:38 UTC
Thanks for a bug report. The 3.10.4 (to be released the next week) should be better with offline understanding, due to a change in bug #702709. It will most likely fix also the message download while in offline.

The "empty cache file" error is new to me. I suppose you see this from an IMAP+ account, right?
Comment 3 Hans Petter Jansson 2014-02-07 18:30:34 UTC
(In reply to comment #2)

> Thanks for a bug report. The 3.10.4 (to be released the next week) should be
> better with offline understanding, due to a change in bug #702709. It will most
> likely fix also the message download while in offline.

Awesome. Thank you!

> The "empty cache file" error is new to me. I suppose you see this from an IMAP+
> account, right?

Yes.
Comment 4 John Mellor 2014-05-14 14:42:51 UTC
This problem is severe and occurring routinely in a completely stock Fedora-20 installation when HTML email rendering is enabled.  When disabled, Evolution again works properly.
Comment 5 Milan Crha 2016-08-12 16:47:26 UTC
I think (it seems to me) this left opened for the "empty cache file" error. I made a fix for this issue within bug #767564, thus I mark this as a duplicate of it.

*** This bug has been marked as a duplicate of bug 767564 ***