On Fri, 2023-01-27 at 17:06 +0000, Timo Aaltonen wrote:
> Hello Lindsay, or anyone else affected,
>
> Accepted libcanberra into jammy-proposed. The package will build now
> and
> be available at
> https://launchpad.net/ubuntu/+source/libcanberra/0.30-10ubuntu1.22.04.1
> in a few hours, and then in the -proposed repository.
>
> Please help us by testing this new package.
I'll be happy to test this out, but I'm a bit out to sea on building
from source these days. I couple of issues:
First, I received an email about 4 hours after yours with the
following:
libcanberra (0.30-10ubuntu1 to 0.30-10ubuntu1.22.04.1)
Migration status for libcanberra (0.30-10ubuntu1 to 0.30-
10ubuntu1.22.04.1): BLOCKED: Rejected/violates migration
policy/introduces a regression
Is there an issue here about which I should be concerned? is the .deb
in the -proposed repository, or has it gone back to the shop for minor
repairs?
Second, I downloaded libcanberra_0.30-10ubuntu1.22.04.1.debian.tar.xz,
unpacked it, and apparently times have changed. I've built dozens of
packages using the autogen.sh; configure; make; sudo mail install
routine but although this source has an autogen.sh script, it lacks a
configure.in file and autogen.sh fails.
No need to bring me up to speed in public. A private reply re. the
required build technique will do.
Thanks for your work!!!
--
Lindsay Haisley | "The world is full of monsters with friendly
FMP Computer Services | faces and angels with scars."
512-496-7118 |
http://www.fmp.com | - Heather Brewer
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
Fix Released
Status in libcanberra source package in Jammy:
Fix Committed
Status in evolution source package in Kinetic:
New
Status in libcanberra source package in Kinetic:
Fix Committed
Bug description:
[ Impact ]
Autosave files are not removed from evolution local state directories
(and windows leaked)
[ Test case ]
1. Open evolution, and start to compose a new email
2. Write enough text and wait few minutes so that this command returns a file
ls -l ~/.local/share/evolution/.evolution-composer.autosave-*
3. Close the email composer window, hitting "Do not save"
4. ls -l ~/.local/share/evolution/.evolution-composer.autosave-* should list
no files
5. Opening and closing again evolution should not ask to restore the previous
email
[ Regression potential ]
No sounds could be performed during some UI actions
---
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/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
