Further analysis by Milan Crha shows that the issue under Xorg seems to
be caused by Ubuntu's gtk3, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972#note_1524307.

** Bug watch added: gitlab.gnome.org/GNOME/evolution/-/issues #1972
   https://gitlab.gnome.org/GNOME/evolution/-/issues/1972

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1983794

Title:
  Evolution not deleting autosave files

Status in evolution package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
  was installed with the distribution on a new system and received
  settings imported from an earlier version on another computer.

  When composing an email, if the process takes long enough an autosave
  file is created as ~/.local/share/evolution/.evolution-
  composer.autosave-xxxxxx ("xxxxxx" is a random 6 character string).
  When the email is successfully sent, the autosave file SHOULD be
  deleted. It's not. When evolution is shut down and restarted I'm asked
  if I want to recover an unfinished email. Answering No to this will
  delete the autosave file, but otherwise it persists and the recovery
  query recurs the next time I open evolution.

  Other people are having the same issue, see
  https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
  people aren't dealing with it, perhaps considering it a distro-
  specific bug.

  On a system used by many people this is a potential security issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1983794/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to