BleachBit 4.9.1 alpha

We invite you to test BleachBit 4.9.1 alpha, a precursor to our 5.0.0 major release.

Changes

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

The Windows build includes a fix for DLL-related system vulnerabilities (one, two) that exist in BleachBit 4.6.2 and earlier versions.

Tests new to 4.9.1

Please test the application in general with special attention to the following tests.

The following tests apply to both Windows and Linux:

• Clean Discord.

• In the application menu, click Wipe free space and choose a directory to wipe. Choose any directory on a partition. (You do not need to wipe multiple directories per partition.) Check for a regression: it should succeed without any error messages. It can take a long time proportional to the amount of free space available. Test it on various filesystems, such as NTFS, FAT32, ext2, ext3, ext4, vfat, xfs, and btrfs.

  Tip: On Linux, you can make extra partitions using a loopback file system. On Windows, use a virtual drive. To test the condition of wiping a partition that is not full, make a sparse file to fill it to about 95%. Leave more than 5GB free.

• Also, test "wipe free space" on a partition that was already 100% full. See How to fill up a partition.

• In the preferences, disable the option for debug logging. Open a terminal and run:

  python3 bleachbit.py --debug --gui

  (Linux) or

  bleachbit_console.exe --debug --gui

  (Windows). You should see many lines such as "automatically hiding" and "Cleaner is not usable on this OS".

• Check that the preferences dialog opens.
• Check for extra space in the language selection combobox in the preferences (issue 1764).
• In the same combo box, browse the list of language names. Most should be in the format like "English United States (en_US)" with the native name and a language code.

• Test the feature to restore window size and position. Every time BleachBit starts, it should restore the application with the same size, position, and maximized state. First, in the preferences, check the option remember window geometry.

  The complexity involves that it may not be possible to honor the request exactly because the number of monitors changed or the resolution of the monitors changed.

  • Basic test: Change the default position and size, close and restart the application. Verify the window is restored to the same size and position.
  • Maximized test: Maximize the application, restart it, and verify it was maximized.
  • Multiple monitors test: Start the application on the second monitor, close the application, disconnect the monitor, and restart the application. Verify it appears on the primary monitor.
  • Resolution change test: Start the application in the bottom right corner of the primary monitor (not using a secondary monitor), reduce the resolution, and restart the application. Verify the application appears visible (instead of off screen). Tip: Either reduce the resolution on your regular display or use a virtual machine like VirtualBox that allows dynamic resolution changes.

• Test deleting files and registry keys (on Windows) that cause "access denied" errors, and the error messages should be a single line (instead of multiple lines). Also, on Windows, the slashes should not be doubled like c:\windows\logs\log.txt.

  To trigger these errors, run BleachBit without administrator privileges (Windows) or sudo (Linux), and then clean system files such as APT (Linux) or System - Windows Update (Windows). Test variations such as toggling "overwrite files" in the preferences: test it both ways.

  Some common options for registry keys that require elevated permissions (marked by HKLM, HKU, HKCR) can be found under the section Microsoft Windows (when winapp2.ini is installed): Regedit, Windows Error Reporting, Windows Notification, and Windows Logs. See also issue 1790.

• Test starting the application when its configuration directory is full. See How to fill up a partition. Test two variations: the bleachbit.ini file did or did not exist before filling the partition.

  On Windows, the file is located at %appdata%\bleachbit\bleachbit.ini and on Linux in ~/.config/bleachbit/bleachbit.ini.

• Test starting the application when access to its configuration file is locked (but the partition is not full).

  Scenario 1: The bleachbit.ini file already exists. Own it by root:

  sudo chown root ~/.config/bleachbit/bleachbit.ini

  Or equivalent on Windows.

  Scenario 2: Delete it and lock the directory:

  sudo chown root ~/.config/bleachbit/

• Clean a CleanerML file with a space (871) and dconf (1096). Download test491.xml and put it in the personal cleaners directory.

  On Windows, it's %appdata%\bleachbit\cleaners\, and on Linux, it's ~/.config/bleachbit/cleaners/.

  Restart BleachBit, and test the new options. Note: dconf applies only to Linux.

• Click the application menu and choose System Information. Verify it doesn't crash, and check that the information is correct.