[Evolution] More info on my intermittent failure of messages to mark themselves as read
Hi all, I think this problem has several root causes, any one of which can cause it. First, there's a difference between the light blue background on an email when you first select a folder, and the dark blue background when you click on that message. I think I need to click on it in order to mark as read. Second, I must wait the entire 2 seconds, that I specified in the config, for the message to realize it's been read. However, there are still intermittent situations where a message stubbornly refuses to mark itself as read. This occurs almost exclusively on the message that first gets the light blue background when I move to the folder. I click on that message and wait 2 seconds, 5 seconds or whatever, and it remains unread. These pesky messages soon mark themselves as read when I leave the folder and come back once or twice, but it's inconvenient because I keep clicking on folders having nothing unread due to the false unread status. Given this new info, any ideas for either a root cause or diagnostic tests I can perform? SteveT ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Synchronisation problem
Hi, I understand what could happen. I regularly perform a cleanup of the cache by 'Bleachbit'. I will try to set ~/.local/share/evolution/* into the white list. Tks a lot for decoding the error message. Bye. David. Le lundi 05 septembre 2022 à 10:01 +0200, Milan Crha via evolution-list a écrit : > On Fri, 2022-09-02 at 22:16 +0200, David Lemonnier wrote: > > > Le moteur « David » de la liste de tâches a rencontré une erreur. > > > > > > L’erreur signalée était « SQLite error code '8': attempt to write > > > a > > > readonly database > > Hi, > I'm sorry, I do not speak (nor write) French. I hope it will be > helpful > anyway. > > There happened something to the underlying database, where the task > list stores its data. The usual location is either > > ~/.local/share/evolution/tasks/ > > for On This Computer tasks lists and > > ~/.cache/evolution/tasks/ > > for remote task lists (I speak of the task lists, because the error > message you pasted claims VTODO, which are tasks; you can get similar > errors for calendar, where the end of the path will not be `tasks`, > but > it'll be `calendar`, and for memos it'll be `memos`). > > The last time I saw a similar error was when I deleted the files from > the ~/.cache/evolution/tasks/ while the evolution-calendar-factory > process had been running. To fix that, I simply restarted the > process, > either manually (`pkill -TERM evolution-calendar-factory`) or just by > `evolution --force-shutdown`. You should make sure Evolution itself > is > not running when you are killing the background process. > > Try to find out what deletes the files from the ~/.cache/evolution/ > for > you. Maybe you've setup some regular automatic cleanup of the cache > data, which is harmful for the evolution-data-server itself, because > the data stored in the cache is re-downloaded on demand, whenever > missing. > > Bye, > Milan > > ___ > evolution-list mailing list > evolution-list@gnome.org > To change your list options or unsubscribe, visit ... > https://mail.gnome.org/mailman/listinfo/evolution-list ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
[Evolution] ews api -> graph api question
Hi, like most of us know the ews api is considered deprecated and graph api is the one which should be used in the future. I found this which is dated 05/19/2022: https://docs.microsoft.com/en-us/graph/migrate-exchange-web-services-api-mapping and it looks like all ews api calls have now a pendant on the graph side (under the assumption the left ews one is a complete listing - I did not double check this). Is: https://gitlab.gnome.org/GNOME/evolution-ews/-/tree/master/src/Microsoft365 already ready to use? Is there a document I can read how much progress the new connector has already made? I am just curious to know what is the current state of evolution and the graph api, thanks in advance for some insights on that topic. kind regards Torsten -- ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
