This release includes various fixes and stability improvements. If you are on a Mac or PC, please also update Docker Desktop to the latest version to get the latest security fixes.
The highlights for this release are:
- Handle timeout errors (
"Timeout after 3 seconds") more gracefully
Several people have encountered timeout errors when converting documents. We have not pinpointed yet the exact reason for these timeouts, but we know they happen once the conversion has finished, either successfully or unsuccessfully, and they are informational in nature. In this release, we improve our handling of termination delays, and users should not experience these timeout errors again. - Support for Fedora 40 and Ubuntu 24.04 (Linux)
Fedora 40 and Ubuntu 24.04 were released recently, so we added support for these platforms. - Sign our release assets
In addition to platform-specific signing procedures, our release assets are now also signed with the Dangerzone signing key (DE28 AB24 1FA4 8260 FAC9 B8BA A7C9 B385 2260 4281). By "release assets", we refer to our installers for Windows and macOS, and our container image, that you see at the bottom of this page. We also provide a guide that explains how to verify these assets on your own. - Community contributions
- We want to thank our first-time contributor, @naglis, who fixed several issues, both user-facing and developer-facing. Notably, Dangerzone's icon and name should now be shown properly on all supported Linux platforms (#402). Also, Linux users can now open multiple documents at once, when they right-click on them, and then click on "Open with" -> "Dangerzone" (#797).
- First-time contributor @maltfield notified us that Dangerzone did not work on macOS releases prior to Ventura (13) (#471). This issue should be resolved with this release.
- Finally, special thanks to our two other first-time contributors, @stepnem and @iArchitSharma, who offered some development improvements (#573, #784).
On a final note, we'd like to inform our Fedora users that Dangerzone has stopped working since May 5th. We have contacted the upstream Python3 maintainers, and we are monitoring the situation.
For a full list of the changes, see our changelog.