I haven't seen this happen on my Ubuntu system for a while. I'm now on Evolution 3.22.3 and Ubuntu 16.10, so I'm guessing it was fixed when a newer version of Evolution was included in Ubuntu via the normal release process.
As for how long these things take to get fixed after an upstream fix, it basically depends on whether the distribution consider the bug important enough to warrant an update or backport (doing these is always somewhat risky, because there's the chance that a fix for one bug could end up unintentionally breaking something else, and there's a definite desire that the system should not become worse as the result of an update). Possibilities on Ubuntu involve pushing the bugfix to everyone (this normally only happens if it's a really big problem or a security problem); pushing the bugfix only to people who've opted in to receiving backports faster; pushing the bugfix only to people who have opted into "proposed changes" to the OS (although I don't know for certain, this is typically done if pushing the change more widely is considered a good idea but there's a worry that something might break in the process); or only pushing the changes out with the next version of the OS. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1615732 Title: Execution of filter 'Junk check' fails with "Empty cache file" To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1615732/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
