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 714693 - Geary constantly modifies geary.db even when no activity is occurring (don't write message flags unless necessary)
Geary constantly modifies geary.db even when no activity is occurring (don't ...
Status: RESOLVED DUPLICATE of bug 778276
Product: geary
Classification: Other
Component: engine
master
Other All
: High normal
: ---
Assigned To: Geary Maintainers
Geary Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-01-31 07:21 UTC by Geary Maintainers
Modified: 2018-02-07 22:12 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Charles Lindsay 2013-11-21 20:28:29 UTC


---- Reported by geary-maint@gnome.bugs 2013-01-31 11:21:00 -0800 ----

Original Redmine bug id: 6287
Original URL: http://redmine.yorba.org/issues/6287
Searchable id: yorba-bug-6287
Original author: Ben Booth
Original description:

My home directory is backed up nightly using a remote backup software, however
the backup software is having trouble backing up the geary.db file because it
is constantly being modified during the backup process. It looks like geary.db
is constantly modified, even when there are no new emails being delivered and
I am not actively using the email client. Is there some reason why the
geary.db file needs to be constantly modified while the client is open?



---- Additional Comments From geary-maint@gnome.bugs 2013-05-15 14:31:00 -0700 ----

### History

####

#1

Updated by Jim Nelson 10 months ago

  * **Tracker** changed from _Feature_ to _Bug_
  * **Subject** changed from _Geary constantly modifies geary.db even when no activity is occurring_ to _Geary constantly modifies geary.db even when no activity is occurring (don't write message flags unless necessary)_
  * **Category** set to _engine_
  * **Priority** changed from _Normal_ to _High_
  * **Target version** set to _0.3.0_

There's a couple of things that could be the culprit. First, even if you're
not using Geary, it is contantly monitoring your Inbox, so if new mail arrives
while you're away or if you read or archive mail from another client, Geary
will write those changes almost instantly. If you leave Geary with another
folder selected, it is doing the same for that one as well.

Even if your account is quiet, there's another place this is a problem. IMAP
doesn't notify a client of flag changes, so Geary has to poll to see if any
have changed. (Flags are if a message is marked read/unread, starred, etc.)
Geary is writing those flags to disk whether or not they've changed. We should
fix that.

####

#2

Updated by Jim Nelson 9 months ago

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

####

#3

Updated by Jim Nelson 6 months ago

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



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

This bug was previously known as _bug_ 6287 at http://redmine.yorba.org/show_bug.cgi?id=6287

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 

Comment 1 Michael Gratton 2018-02-07 22:12:13 UTC

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