BleachBit 4.6.1 beta
Please test BleachBit 4.6.1 beta, which eventually become the 4.6.2 maintenance release.
UPDATE
October 7, 2024: BleachBit 4.6.2 has been released.
Changes
For a list of changes see the commit log and GitHub bug tracker.
Tests
Please test the application in general with special attention to the following tests.
The following tests apply to both Windows and Linux:
- Clean Google Chrome cookies (see #1509).
- Clean Google Chrome cache, and you will not be an error message ValueError: Unexpected UTF-8 BOM (decode using utf-8-sig) (see 1658).
- Clean Google Chrome sessions.
Linux
- Start the application as normal user with normal privileges under Wayland (PR 1577), and verify that the application starts normally.
- When running KDE, open the BleachBit preferences and toggle the KDE plasma integration.
- On command line under Wayland, use su to run as root.
- Test with Python 3.12 (see #1703), and check the console for SyntaxWarning: invalid escape sequence.
- Test installers for Fedora 39,40
- Test installers for Ubuntu 24.04.
Windows
- In BleachBit 4.6.0, a regression introduced an error message Error "Code execution cannot proceed because msvcr100.dll was not found, and then the application would not start, so verify that the application starts correctly without this error. If you have the Visual Studio 2010 (VC++ 10.0) redistributable SP1 x86 installed, please uninstall it for testing. For more info, see version 4.6.0 known issues and issue 1569.
- This version has a new code signing certificate, so you should not see an error about unsigned code, and instead, it should be signed by Andrew Ziem, Open Source Developer.
- Clean a path containing the name sysnative (1574). These include Internet Explorer cache and logs.
- Check in Task Manager that the process name is shorter (1655).
- In the BleachBit preferences, verify that the option about KDE integration is not shown on Windows.
Downloads
See the downloads folder. Linux users can download .deb or .rpm packages, while Windows users can download a digitally-signed installer or a portable package.
After testing
If something is broken, please file a bug report. If it works well, please post a comment with what you tested in the testing forum, as a comment at the bottom of this page, or as a GitHub issue.
- andrew's blog
- Log in or register to post comments