BleachBit 3.1 beta

Please test BleachBit 3.1 beta. This is a maintenance release to fix bugs in BleachBit 3.0 (final).

Like BleachBit 3.0, BleachBit 3.1 requires Python 2. (For Microsoft Windows, the Python runtime is installed automatically, as always.) Once beta testing is done, BleachBit 3.1 will be released as BleachBit 3.2 final.

In a separate branch, much progress has been made for BleachBit to run on Python 3. While these changes are not in the BleachBit 3.x series, watch for a release soon after Bleachbit 3.2.


February 5, 2020: BleachBit 3.2.0 has been released.


For a list of changes see the commit log and GitHub bug tracker.


These tests are for both Windows and Linux.

  • Start the GUI. The toolbar should have text and larger icons.
  • Clean Google Chrome history, and verify there is no OperationalError error message.
  • In the Google Chrome profile directory, delete or rename the History file. Then, use BleachBit to clean Google Chrome history. There should be no error message.
  • If you do not use VIM, verify it is automatically hidden from the list of cleaners.
  • Copy information to the system clipboard. Use BleachBit to clean the system clipboard. Verify it is empty by pasting from the clipboard.


  • Verify the installer works.
  • Start the GUI. Minimize and maximize it. Move it between monitors. Verify the BleachBit GUI does not disappear.
  • Start the application, and you should not get a popup error "There is no disk in the drive."
  • Check the box for Windows Explorer - Shellbags, and it should give you a helpful warning.
  • Run the Internet Explorer cleaner, and verify it does not delete audio mixer settings.
  • Put a junction in the recycle bin, and verify BleachBit does not follow it. See #668.


  • Test new distributions: Fedora 30, Fedora 31.
  • Install from .rpm, and it should require the package python-gobject.
  • Install from .deb on Ubuntu 16.04, and it should not fail because the package python-scandir is not available.
  • Verify there is a launcher to start BleachBit.
  • Run BleachBit in CLI mode where an X session is not available.
  • Verify there are translations on RHEL and CentOS.
  • Preview the VIM swap cleaners, and verify it does not list ~/.htpasswd. This assumes you had that file or made it for testing.
  • Clean the DNF package manager, especially if you have it installed (Fedora, RHEL, and CentOS).


See the downloads folder for BleachBit 3.1 beta. For Linux, there are .deb and .rpm packages. For Windows, there is a digitally signed installer and 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 or at the bottom of this page.

Blog tags: