BleachBit

BleachBit, the open source system cleaner, announces the public 1.9.2 beta which includes enhancements, important bug fixes, and translation updates. Please help test today. These particular areas are a priority for testing: Use the preview and ... [More] clean commands to try out the new size column, which shows in the GUI next to the names of the options for each cleaner. Check the option to delete Firefox passwords, and verify it gives a warning. Clean passwords on Firefox version 32 or later, and verify they are deleted. Enable checking for updates, disable the network by toggling the wifi, unplugging the network cable, or turning off the router. Then restart BleachBit, and verify there is a user-friendly error message. Pass relative paths to the command line option --shred. Open the preferences dialog, resize it, and notice it resizes better. Before it wasted whitespace in some places. In the configuration file bleachbit.ini abbreviate True and False to T and F, restart BleachBit, and verify the preferences were maintained. Specific to Linux Under KDE when running BleachBit with administrator privileges, clean KDE - Temporary Files (see LP#1377719). Test the new packages for Ubuntu 15.10, Fedora 22, and Fedora 23. Clean localizations. On many systems, more files should be cleaned than before. When starting BleachBit in a terminal in either GUI or CLI mode, verify in the terminal there is not an error "localizations.xml is not usable." Verify Windows Explorer does not show as an cleaner. Specific to Windows Start BleachBit in standard (GUI) mode, and close it without doing any cleaning or previews. Verify there is a not a pop-up error about bleachbit.exe.log. Clean a non-removable directory (such as a directory with a file that is opened by a running application), close Bleachbit, and verify there is a not a pop-up error about bleachbit.exe.log. Use BleachBit in general, close the application, and verify there is not a pop-up error about bleachbit.exe.log when exiting. On Windows 10 verify the system presents the User Access Control (UAC) dialog when starting BleachBit under an administrator account. Clean Adobe Reader - Most Recently Used. Then open Adobe Reader and verify the list is cleaned. See also the list of bugs targeted to BleachBit version 1.10 and a list of code changes. These links give more details including credits for people contributing patches and reporting bugs. The final release will include some of these details. Since BleachBit 1.0, odd-numbered minor versions are unstable releases, so BleachBit 1.9.2 is the first beta release for 1.10 stable. To look for regressions follow the standard tests on the Testing page. Download UPDATE December 20, 2015: BleachBit 1.9.3 beta has been released. Linux CentOS 6 CentOS 7 Debian 6 (Squeeze) Debian 7 (Wheezy) Debian 8 (Jessie) Fedora 20 (Heisenbug) Fedora 21 Fedora 22 Fedora 23 Linux Mint 13 LTS (Maya) Linux Mint 17 - 17.3 (Qiana/Rebecca/Rafaela/Rosa) RHEL 6 RHEL 7 SLE 11 Ubuntu 12.04 (Precise Pangolin) Ubuntu 14.04 LTS (Trusty Tahr) Ubuntu 14.10 (Utopic Unicorn) Ubuntu 15.04 (Vivid Vervet) Ubuntu 15.10 (Wily Werewolf) openSUSE 13.1 openSUSE 13.2 Windows Microsoft Windows installer (exe) Microsoft Windows installer, English only (exe) Microsoft Windows portable (zip) Source code bleachbit-1.9.2.tar.bz2 Translators Translators, please update your translations. Blog tags: beta [Less]

BleachBit, the open source system cleaner, announces the public 1.9.2 beta which includes enhancements, important bug fixes, and translation updates. Please help test today. These particular areas are a priority for testing: Use the preview and ... [More] clean commands to try out the new size column, which shows in the GUI next to the names of the options for each cleaner. Check the option to delete Firefox passwords, and verify it gives a warning. Clean passwords on Firefox version 32 or later, and verify they are deleted. Enable checking for updates, disable the network by toggling the wifi, unplugging the network cable, or turning off the router. Then restart BleachBit, and verify there is a user-friendly error message. Pass relative paths to the command line option --shred. Open the preferences dialog, resize it, and notice it resizes better. Before it wasted whitespace in some places. In the configuration file bleachbit.ini abbreviate True and False to T and F, restart BleachBit, and verify the preferences were maintained. Specific to Linux Under KDE when running BleachBit with administrator privileges, clean KDE - Temporary Files (see LP#1377719). Test the new packages for Ubuntu 15.10, Fedora 22, and Fedora 23. Clean localizations. On many systems, more files should be cleaned than before. When starting BleachBit in a terminal in either GUI or CLI mode, verify in the terminal there is not an error "localizations.xml is not usable." Verify Windows Explorer does not show as an cleaner. Specific to Windows Start BleachBit in standard (GUI) mode, and close it without doing any cleaning or previews. Verify there is a not a pop-up error about bleachbit.exe.log. Clean a non-removable directory (such as a directory with a file that is opened by a running application), close Bleachbit, and verify there is a not a pop-up error about bleachbit.exe.log. Use BleachBit in general, close the application, and verify there is not a pop-up error about bleachbit.exe.log when exiting. On Windows 10 verify the system presents the User Access Control (UAC) dialog when starting BleachBit under an administrator account. Clean Adobe Reader - Most Recently Used. Then open Adobe Reader and verify the list is cleaned. See also the list of bugs targeted to BleachBit version 1.10 and a list of code changes. These links give more details including credits for people contributing patches and reporting bugs. The final release will include some of these details. Since BleachBit 1.0, odd-numbered minor versions are unstable releases, so BleachBit 1.9.2 is the first beta release for 1.10 stable. To look for regressions follow the standard tests on the Testing page. Download UPDATE December 20, 2015: BleachBit 1.9.3 beta has been released. Linux CentOS 6 CentOS 7 Debian 6 (Squeeze) Debian 7 (Wheezy) Debian 8 (Jessie) Fedora 20 (Heisenbug) Fedora 21 Fedora 22 Fedora 23 Linux Mint 13 LTS (Maya) Linux Mint 17 - 17.3 (Qiana/Rebecca/Rafaela/Rosa) RHEL 6 RHEL 7 SLE 11 Ubuntu 12.04 (Precise Pangolin) Ubuntu 14.04 LTS (Trusty Tahr) Ubuntu 14.10 (Utopic Unicorn) Ubuntu 15.04 (Vivid Vervet) Ubuntu 15.10 (Wily Werewolf) openSUSE 13.1 openSUSE 13.2 Windows Microsoft Windows installer (exe) Microsoft Windows installer, English only (exe) Microsoft Windows portable (zip) Source code bleachbit-1.9.2.tar.bz2 Translators Translators, please update your translations. Blog tags:  beta [Less]

BleachBit, the open source system cleaner, announces the public 1.9.2 beta which includes enhancements, important bug fixes, and translation updates. Please help test today. These particular areas are a priority for testing: Use the preview and ... [More] clean commands to try out the new size column, which shows in the GUI next to the names of the options for each cleaner. Check the option to delete Firefox passwords, and verify it gives a warning. Clean passwords on Firefox version 32 or later, and verify they are deleted. Enable checking for updates, disable the network by toggling the wifi, unplugging the network cable, or turning off the router. Then restart BleachBit, and verify there is a user-friendly error message. Pass relative paths to the command line option --shred. Open the preferences dialog, resize it, and notice it resizes better. Before it wasted whitespace in some places. In the configuration file bleachbit.ini abbreviate True and False to T and F, restart BleachBit, and verify the preferences were maintained. Specific to Linux Under KDE when running BleachBit with administrator privileges, clean KDE - Temporary Files (see LP#1377719). Test the new packages for Ubuntu 15.10, Fedora 22, and Fedora 23. Clean localizations. On many systems, more files should be cleaned than before. When starting BleachBit in a terminal in either GUI or CLI mode, verify in the terminal there is not an error "localizations.xml is not usable." Verify Windows Explorer does not show as an cleaner. Specific to Windows Start BleachBit in standard (GUI) mode, and close it without doing any cleaning or previews. Verify there is a not a pop-up error about bleachbit.exe.log. Clean a non-removable directory (such as a directory with a file that is opened by a running application), close Bleachbit, and verify there is a not a pop-up error about bleachbit.exe.log. Use BleachBit in general, close the application, and verify there is not a pop-up error about bleachbit.exe.log when exiting. On Windows 10 verify the system presents the User Access Control (UAC) dialog when starting BleachBit under an administrator account. Clean Adobe Reader - Most Recently Used. Then open Adobe Reader and verify the list is cleaned. See also the list of bugs targeted to BleachBit version 1.10 and a list of code changes. These links give more details including credits for people contributing patches and reporting bugs. The final release will include some of these details. Since BleachBit 1.0, odd-numbered minor versions are unstable releases, so BleachBit 1.9.2 is the first beta release for 1.10 stable. To look for regressions follow the standard tests on the Testing page. Download UPDATE December 20, 2015: BleachBit 1.9.3 beta has been released. Linux CentOS 6 CentOS 7 Debian 6 (Squeeze) Debian 7 (Wheezy) Debian 8 (Jessie) Fedora 20 (Heisenbug) Fedora 21 Fedora 22 Fedora 23 Linux Mint 13 LTS (Maya) Linux Mint 17 - 17.3 (Qiana/Rebecca/Rafaela/Rosa) RHEL 6 RHEL 7 SLE 11 Ubuntu 12.04 (Precise Pangolin) Ubuntu 14.04 LTS (Trusty Tahr) Ubuntu 14.10 (Utopic Unicorn) Ubuntu 15.04 (Vivid Vervet) Ubuntu 15.10 (Wily Werewolf) openSUSE 13.1 openSUSE 13.2 Windows Microsoft Windows installer (exe) Microsoft Windows installer, English only (exe) Microsoft Windows portable (zip) Source code bleachbit-1.9.2.tar.bz2 Translators Translators, please update your translations. Blog tags:  beta [Less]

BleachBit, the open source system cleaner, announces the public 1.9.2 beta which includes enhancements, important bug fixes, and translation updates. Please help test today. These particular areas are a priority for testing: Use the preview and ... [More] clean commands to try out the new size column, which shows in the GUI next to the names of the options for each cleaner. Check the option to delete Firefox passwords, and verify it gives a warning. Clean passwords on Firefox version 32 or later, and verify they are deleted. Enable checking for updates, disable the network by toggling the wifi, unplugging the network cable, or turning off the router. Then restart BleachBit, and verify there is a user-friendly error message. Pass relative paths to the command line option --shred. Open the preferences dialog, resize it, and notice it resizes better. Before it wasted whitespace in some places. In the configuration file bleachbit.ini abbreviate True and False to T and F, restart BleachBit, and verify the preferences were maintained. Specific to Linux Under KDE when running BleachBit with administrator privileges, clean KDE - Temporary Files (see LP#1377719). Test the new packages for Ubuntu 15.10, Fedora 22, and Fedora 23. Clean localizations. On many systems, more files should be cleaned than before. When starting BleachBit in a terminal in either GUI or CLI mode, verify in the terminal there is not an error "localizations.xml is not usable." Verify Windows Explorer does not show as an cleaner. Specific to Windows Start BleachBit in standard (GUI) mode, and close it without doing any cleaning or previews. Verify there is a not a pop-up error about bleachbit.exe.log. Clean a non-removable directory (such as a directory with a file that is opened by a running application), close Bleachbit, and verify there is a not a pop-up error about bleachbit.exe.log. Use BleachBit in general, close the application, and verify there is not a pop-up error about bleachbit.exe.log when exiting. On Windows 10 verify the system presents the User Access Control (UAC) dialog when starting BleachBit under an administrator account. Clean Adobe Reader - Most Recently Used. Then open Adobe Reader and verify the list is cleaned. See also the list of bugs targeted to BleachBit version 1.10 and a list of code changes. These links give more details including credits for people contributing patches and reporting bugs. The final release will include some of these details. Since BleachBit 1.0, odd-numbered minor versions are unstable releases, so BleachBit 1.9.2 is the first beta release for 1.10 stable. To look for regressions follow the standard tests on the Testing page. Download UPDATE December 20, 2015: BleachBit 1.9.3 beta has been released. Linux CentOS 6 CentOS 7 Debian 6 (Squeeze) Debian 7 (Wheezy) Debian 8 (Jessie) Fedora 20 (Heisenbug) Fedora 21 Fedora 22 Fedora 23 Linux Mint 13 LTS (Maya) Linux Mint 17 - 17.3 (Qiana/Rebecca/Rafaela/Rosa) RHEL 6 RHEL 7 SLE 11 Ubuntu 12.04 (Precise Pangolin) Ubuntu 14.04 LTS (Trusty Tahr) Ubuntu 14.10 (Utopic Unicorn) Ubuntu 15.04 (Vivid Vervet) Ubuntu 15.10 (Wily Werewolf) openSUSE 13.1 openSUSE 13.2 Windows Microsoft Windows installer (exe) Microsoft Windows installer, English only (exe) Microsoft Windows portable (zip) Source code bleachbit-1.9.2.tar.bz2 Translators Translators, please update your translations. Blog tags: beta [Less]

BleachBit, the open source system cleaner, announces the public 1.9.2 beta which includes enhancements, important bug fixes, and translation updates. Please help test today. These particular areas are a priority for testing: Use the preview and ... [More] clean commands to try out the new size column, which shows in the GUI next to the names of the options for each cleaner. Check the option to delete Firefox passwords, and verify it gives a warning. Clean passwords on Firefox version 32 or later, and verify they are deleted. Enable checking for updates, disable the network by toggling the wifi, unplugging the network cable, or turning off the router. Then restart BleachBit, and verify there is a user-friendly error message. Pass relative paths to the command line option --shred. Open the preferences dialog, resize it, and notice it resizes better. Before it wasted whitespace in some places. In the configuration file bleachbit.ini abbreviate True and False to T and F, restart BleachBit, and verify the preferences were maintained. Specific to Linux Under KDE when running BleachBit with administrator privileges, clean KDE - Temporary Files (see LP#1377719). Test the new packages for Ubuntu 15.10, Fedora 22, and Fedora 23. Clean localizations. On many systems, more files should be cleaned than before. When starting BleachBit in a terminal in either GUI or CLI mode, verify in the terminal there is not an error "localizations.xml is not usable." Verify Windows Explorer does not show as an cleaner. Specific to Windows Start BleachBit in standard (GUI) mode, and close it without doing any cleaning or previews. Verify there is a not a pop-up error about bleachbit.exe.log. Clean a non-removable directory (such as a directory with a file that is opened by a running application), close Bleachbit, and verify there is a not a pop-up error about bleachbit.exe.log. Use BleachBit in general, close the application, and verify there is not a pop-up error about bleachbit.exe.log when exiting. On Windows 10 verify the system presents the User Access Control (UAC) dialog when starting BleachBit under an administrator account. Clean Adobe Reader - Most Recently Used. Then open Adobe Reader and verify the list is cleaned. See also the list of bugs targeted to BleachBit version 1.10 and a list of code changes. These links give more details including credits for people contributing patches and reporting bugs. The final release will include some of these details. Since BleachBit 1.0, odd-numbered minor versions are unstable releases, so BleachBit 1.9.2 is the first beta release for 1.10 stable. To look for regressions follow the standard tests on the Testing page. Download Linux CentOS 6 CentOS 7 Debian 6 (Squeeze) Debian 7 (Wheezy) Debian 8 (Jessie) Fedora 20 (Heisenbug) Fedora 21 Fedora 22 Fedora 23 Linux Mint 13 LTS (Maya) Linux Mint 17 - 17.3 (Qiana/Rebecca/Rafaela/Rosa) RHEL 6 RHEL 7 SLE 11 Ubuntu 12.04 (Precise Pangolin) Ubuntu 14.04 LTS (Trusty Tahr) Ubuntu 14.10 (Utopic Unicorn) Ubuntu 15.04 (Vivid Vervet) Ubuntu 15.10 (Wily Werewolf) openSUSE 13.1 openSUSE 13.2 Windows Microsoft Windows installer (exe) Microsoft Windows installer, English only (exe) Microsoft Windows portable (zip) Source code bleachbit-1.9.2.tar.bz2 Translators Translators, please update your translations. Blog tags: beta [Less]

Some people are wondering whether BleachBit will continue to use SourceForge hosting services because this year SourceForge suffered several public embarrassments. History First, SourceForge modified the installer for GIMP and a few other projects ... [More] that were no longer actively maintained on SourceForge. Second, SourceForge suffered a massive outage from July 16 through July 22 that affected the BleachBit web site, which includes the download links, documentation, forums, and software update notifications. Less intensely, SourceForge has generally fallen out of style with developers in favor of GitHub. Nevertheless, SourceForge has provided valuable services to BleachBit: Since 2008 BleachBit has used multiple SourceForge services: file hosting, project web hosting, and SVN. The flexible LAMP system that SourceForge offers powers the BleachBit CMS and discussion forums. However, BleachBit does not rely solely on SourceForge. In 2014 BleachBit migrated from SVN on SourceForge to Git on GitHub. Issues and translations have been managed on Canonical's Launchpad, and most downloads are served through a private mirror (i.e., not SourceForge). The response The issue of the installer is not a concern because: The Windows installer for BleachBit is digitally signed to prevent tampering. It cannot be altered without damaging the signature, and wrapping the installer would show either no signature or another signature. BleachBit is actively maintained, so under the old policy, SourceForge would not have done anything anyway. BleachBit uses the SourceForge download service only as a secondary mirror. In response SourceForge already changed their policies. As an aside, though companies regularly contact me with offers, BleachBit has never included advertising junk in the installer. In response to the outage issue: it was very inconvenient, but is it really worth moving the BleachBit website to another hosting service? I have hosting projects on SourceForge since 2002, and until this outage, SourceForge had a decent reputation for reliability. I hope they have learned a lesson, which I am sure was costly. Looking forward It would have alleviated 95% of the pain if SourceForge offered in case a HTTP redirect when the project web hosting is down to run a temporary site, so I filed a support ticket (support ticket 10988). In the short term BleachBit will continue to use SourceForge for project web hosting and a secondary download mirror. I will consider options for improving the reliability of the BleachBit update notification system for the next release (BleachBit version 1.10). I will consider alternative hosting options, but I will prioritize the development of BleachBit code. UPDATE (February 2016): BleachBit is no longer hosted on SourceForge. Blog tags:  notice [Less]

Some people are wondering whether BleachBit will continue to use SourceForge hosting services because this year SourceForge suffered several public embarrassments. History First, SourceForge modified the installer for GIMP and a few other ... [More] projects that were no longer actively maintained on SourceForge. Second, SourceForge suffered a massive outage from July 16 through July 22 that affected the BleachBit web site, which includes the download links, documentation, forums, and software update notifications. Less intensely, SourceForge has generally fallen out of style with developers in favor of GitHub. Nevertheless, SourceForge has provided valuable services to BleachBit: Since 2008 BleachBit has used multiple SourceForge services: file hosting, project web hosting, and SVN. The flexible LAMP system that SourceForge offers powers the BleachBit CMS and discussion forums. However, BleachBit does not rely solely on SourceForge. In 2014 BleachBit migrated from SVN on SourceForge to Git on GitHub. Issues and translations have been managed on Canonical's Launchpad, and most downloads are served through a private mirror (i.e., not SourceForge). The response The issue of the installer is not a concern because: The Windows installer for BleachBit is digitally signed to prevent tampering. It cannot be altered without damaging the signature, and wrapping the installer would show either no signature or another signature. BleachBit is actively maintained, so under the old policy, SourceForge would not have done anything anyway. BleachBit uses the SourceForge download service only as a secondary mirror. In response SourceForge already changed their policies. As an aside, though companies regularly contact me with offers, BleachBit has never included advertising junk in the installer. In response to the outage issue: it was very inconvenient, but is it really worth moving the BleachBit website to another hosting service? I have hosting projects on SourceForge since 2002, and until this outage, SourceForge had a decent reputation for reliability. I hope they have learned a lesson, which I am sure was costly. Looking forward It would have alleviated 95% of the pain if SourceForge offered in case a HTTP redirect when the project web hosting is down to run a temporary site, so I filed a support ticket (support ticket 10988). In the short term BleachBit will continue to use SourceForge for project web hosting and a secondary download mirror. I will consider options for improving the reliability of the BleachBit update notification system for the next release (BleachBit version 1.10). I will consider alternative hosting options, but I will prioritize the development of BleachBit code. If you are logged in, feel free to post your comments below.Blog tags: notice [Less]

Some people are wondering whether BleachBit will continue to use SourceForge hosting services because this year SourceForge suffered several public embarrassments. History First, SourceForge modified the installer for GIMP and a few other projects ... [More] that were no longer actively maintained on SourceForge. Second, SourceForge suffered a massive outage from July 16 through July 22 that affected the BleachBit web site, which includes the download links, documentation, forums, and software update notifications. Less intensely, SourceForge has generally fallen out of style with developers in favor of GitHub. Nevertheless, SourceForge has provided valuable services to BleachBit: Since 2008 BleachBit has used multiple SourceForge services: file hosting, project web hosting, and SVN. The flexible LAMP system that SourceForge offers powers the BleachBit CMS and discussion forums. However, BleachBit does not rely solely on SourceForge. In 2014 BleachBit migrated from SVN on SourceForge to Git on GitHub. Issues and translations have been managed on Canonical's Launchpad, and most downloads are served through a private mirror (i.e., not SourceForge). The response The issue of the installer is not a concern because: The Windows installer for BleachBit is digitally signed to prevent tampering. It cannot be altered without damaging the signature, and wrapping the installer would show either no signature or another signature. BleachBit is actively maintained, so under the old policy, SourceForge would not have done anything anyway. BleachBit uses the SourceForge download service only as a secondary mirror. In response SourceForge already changed their policies. As an aside, though companies regularly contact me with offers, BleachBit has never included advertising junk in the installer. In response to the outage issue: it was very inconvenient, but is it really worth moving the BleachBit website to another hosting service? I have hosting projects on SourceForge since 2002, and until this outage, SourceForge had a decent reputation for reliability. I hope they have learned a lesson, which I am sure was costly. Looking forward It would have alleviated 95% of the pain if SourceForge offered in case a HTTP redirect when the project web hosting is down to run a temporary site, so I filed a support ticket (support ticket 10988). In the short term BleachBit will continue to use SourceForge for project web hosting and a secondary download mirror. I will consider options for improving the reliability of the BleachBit update notification system for the next release (BleachBit version 1.10). I will consider alternative hosting options, but I will prioritize the development of BleachBit code. UPDATE (February 2016): BleachBit is no longer hosted on SourceForge. Blog tags:  notice [Less]

Some people are wondering whether BleachBit will continue to use SourceForge hosting services because this year SourceForge suffered several public embarrassments. History First, SourceForge modified the installer for GIMP and a few other ... [More] projects that were no longer actively maintained on SourceForge. Second, SourceForge suffered a massive outage from July 16 through July 22 that affected the BleachBit web site, which includes the download links, documentation, forums, and software update notifications. Less intensely, SourceForge has generally fallen out of style with developers in favor of GitHub. Nevertheless, SourceForge has provided valuable services to BleachBit: Since 2008 BleachBit has used multiple SourceForge services: file hosting, project web hosting, and SVN. The flexible LAMP system that SourceForge offers powers the BleachBit CMS and discussion forums. However, BleachBit does not rely solely on SourceForge. In 2014 BleachBit migrated from SVN on SourceForge to Git on GitHub. Issues and translations have been managed on Canonical's Launchpad, and most downloads are served through a private mirror (i.e., not SourceForge). The response The issue of the installer is not a concern because: The Windows installer for BleachBit is digitally signed to prevent tampering. It cannot be altered without damaging the signature, and wrapping the installer would show either no signature or another signature. BleachBit is actively maintained, so under the old policy, SourceForge would not have done anything anyway. BleachBit uses the SourceForge download service only as a secondary mirror. In response SourceForge already changed their policies. As an aside, though companies regularly contact me with offers, BleachBit has never included advertising junk in the installer. In response to the outage issue: it was very inconvenient, but is it really worth moving the BleachBit website to another hosting service? I have hosting projects on SourceForge since 2002, and until this outage, SourceForge had a decent reputation for reliability. I hope they have learned a lesson, which I am sure was costly. Looking forward It would have alleviated 95% of the pain if SourceForge offered in case a HTTP redirect when the project web hosting is down to run a temporary site, so I filed a support ticket (support ticket 10988). In the short term BleachBit will continue to use SourceForge for project web hosting and a secondary download mirror. I will consider options for improving the reliability of the BleachBit update notification system for the next release (BleachBit version 1.10). I will consider alternative hosting options, but I will prioritize the development of BleachBit code. UPDATE (February 2016): BleachBit is no longer hosted on SourceForge. Blog tags: notice [Less]

BleachBit 1.8 fixes important bugs for Windows, enhances Winapp2.ini support, and more. UPDATE December 30, 2015: BleachBit 1.10 has been released. Changes These are the changes since version 1.6: In Preferences, there is a new option "Confirm ... [More] before delete" that disables the confirmation (thanks to codesomniare). When BleachBit starts, the window is centered. The tool "Shred Settings and Quit" in the File menu is fixed. Added cleaning for Opera passwords (Linux support thanks to theatre-x). Shrink storage size of BleachBit icon. Add descriptions to many cleaners (thanks to theatre-x). Add a new command line option --debug-log that logs debug messages to a file.Windows example:"%ProgramFiles(x86)%\BleachBit\Bleachbit.exe" --gui --debug-log=%USERPROFILE%\desktop\bleachbit.log Specific to Linux Replace hard-coded localizations cleaning system with CleanerML entries (thanks to tstenner). Whitelist /tmp/fsa for FSArchiver (reported by Max Miliaan). Suppress GTK+ warning in console (thanks to iliaselmatani). Add packages for Debian 8, Fedora 21, and Ubuntu 15.04. Remove packages for Fedora 19 and Ubuntu 13.10. Specific to Windows Improve support for very long files names and filenames with Unicode characters. Fix support for wiping free space using a long path such as %TEMP%. The symptom was it finished far too quickly. After wiping free space, eliminate spurious error message "no such file or directory." Add support for environment variables: commonappdata, localappdata, music, pictures, video, documents. They are already used in Winapp2.ini, and they can be used in CleanerML too. Fix support for %DOCUMENTS%. Add label for Windows Store section in Winapp2.ini. Expand system log cleaning to %WINDIR%\SoftwareDistribution (thanks to cfoellmann). In the cleaner System - Temporary Files whitelist %TEMP%\Low to avoid causing problems with printing from Internet Explorer (reported by Stewart). When cleaning Windows Explorer - Most Recenty Used avoid causing the recently-used application list in the Start menu to not accumulate new history. Fix decoding of exception messages to avoid crash during startup (reported by goingoin). Clean more SeaMonkey files (thanks to Sherman). Clean Skype uninstallers (thanks to cfoellmann). Development In CleanerML, a cleaner description can have a translation hint. Set up Travis CI for better testing. Improve unit tests. List of bugs targeted to BleachBit version 1.8 List of code changes. Translations Show translation changes Add Norwegian Nynorsk translation thanks to Alexander Mackinnon Jansen. Update Chinese (Traditional) translation thanks to Pin-hsien Li. Update Czech translation thanks to Roman Horník. Update Dutch translation thanks to rob. Update English (United Kingdom) translation thanks to Alexander Mackinnon Jansen and Andi Chandler. Update Estonian translation thanks to Jalakas. Update Finnish translation thanks to Jiri Grönroos. Update French translation thanks to Jean Marc. Update German translation thanks to pitfd and Tobias Bannert. Update Greek translation thanks to Valantis Kamayiannis, DimitrisT, nask00s, mara sdr, Dimitris Mytilinaios. Update Indonesian translation thanks to Andika Triwidada. Update Italian translation thanks to Carml, Jacopo Tumminello. Update Korean translation thanks to B. W. Knight. Update Malay translation thanks to abuyop. Update Norwegian Bokmal translation thanks to Simen Heggestøyl, Åka Sikrom. Update Polish translation thanks to Dariusz Jakoniuk, Piotr Strębski. Update Portuguese translation thanks to asensio, Formatado, Sérgio Marques, Carlos Geadas, Alexandre Fidalgo, Pedro Silva, asensio, DarkVenger, Pedro Folha, Almufadado, Nuno Machado. Update Russian translation thanks to ☠Jay ZDLin☠. Update Slovak translation thanks to Roman Horník. Update Swedish translation thanks to sweidre, Josef Andersson. Update Thai translation thanks to Akom C., shane.fox, SiraNokyoongtong. Update Uzbek translation thanks to Akmal Xushvaqov. Update Vietnamese translation thanks to Nguyen Kim Kha. Be a translator? Known issues On Windows when exiting you may see a notice about bleachbit.exe.log, which contains the error "directory is not empty" (LP#1469588). The error is harmless, and it is fixed in BleachBit 1.9.2 beta. On Windows 10, BleachBit will not show the User Access Control dialog to elevate to administrator privileges (LP#1496629), so you may see access denied error messages for certain options. This issue is fixed in BleachBit 1.9.2 beta. Blog tags:  release [Less]