Skip to content

Commit a878bff

Browse files
committed
Make the FAQ dynamic
1 parent 80dc90f commit a878bff

2 files changed

Lines changed: 313 additions & 236 deletions

File tree

_data/faqs.yml

Lines changed: 295 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,295 @@
1+
main:
2+
- question: Why do I see permissions denied errors on Linux?
3+
answer: 'If you are trying to clean the system (for example, localizations, APT,
4+
or DNF), run BleachBit with root permissions. To elevate permissions, choose the
5+
menu option "BleachBit as Administrator" _or_ run <tt>sudo</tt> on the command
6+
line.
7+
8+
9+
Alternatively, when running as a normal user, uncheck options that require root
10+
permissions.'
11+
- question: Why do I see permission denied errors on Windows?
12+
answer: 'This happens when cleaning certain files, such as Windows system logs under
13+
``c:\windows``.
14+
15+
When you first launch BleachBit it should prompt you with the User Access Control
16+
dialog, which asks, "Do you want to allow the following program to make changes
17+
to this computer." Answer *Yes* to grant BleachBit the privileges to modify all
18+
files.
19+
20+
21+
If you answer *No*, then BleachBit will start, and it will still be able to clean
22+
data under your user profile. However, it will not have access to clean system
23+
data.'
24+
- question: On Linux do I need to run BleachBit both as a normal user and as an administrator?
25+
answer: 'It depends how your system elevates privileges. Linux has various tools
26+
(for example, kdesudo, gksudo sudo, su-to-root, and PolicyKit) with various options
27+
to elevate to root (administrator) privileges, and they create two different situations.
28+
29+
30+
In the first case, they switch the user to the root account, so BleachBit cleans
31+
the root account and not the non-privileged account. For example, BleachBit will
32+
clean root''s web browsers, which are probably never used, so it may seem BleachBit
33+
is not finding the files you expect. In this case, use the Bleachbit as Administrator
34+
option to clean any system files that require special privileges, and then use
35+
regular BleachBit to clean files in your personal profile.
36+
37+
38+
In the second case, BleachBit runs with elevated privileges in the context of
39+
the non-privileged account, so all options can cleaned from one session.
40+
41+
42+
To check which case applies to you, start BleachBit as Administrator, click on
43+
Help - System Information, and look at the value for ```os.path.expanduser(''~'')```.
44+
If it equals ```/root```, then the first case is happening, so run BleachBit both
45+
as administrator and as a regular user to clean all files.
46+
47+
48+
Another way to check is first to run BleachBit as administrator. Then run BleachBit
49+
as a regular user, and if the preview shows any files, then you may need to run
50+
BleachBit as a regular user.'
51+
- question: How to run the GUI as root on Linux under Wayland?
52+
answer: 'As the unprivileged user, run this command to allow the local user''s X
53+
session:
54+
55+
56+
```xhost si:localuser:root```
57+
58+
59+
When finished, disable the access:
60+
61+
62+
```xhost -si:localuser:root```
63+
64+
65+
Avoid running GUI applications as root.
66+
67+
68+
Source: [[ArchWiki]](https://wiki.archlinux.org/title/Running_GUI_applications_as_root)'
69+
- question: How do I recover a file deleted by BleachBit?
70+
answer: '"I had BleachBit delete data, but now I want it back. Is there an undo
71+
command?"
72+
73+
74+
The success of recovery depends on whether the file was overwritten, and the ease
75+
of recovery depends on whether the metadata was overwritten. If in the preferences
76+
the option "Overwrite files to prevent recovery" was enabled, the file probably
77+
cannot be recovered. There is an exception if the file system is ext3 or ext4
78+
in `data=journal` mode. The default file system on Ubuntu is ext4 with `data=ordered`
79+
mode, which makes recovery unlikely.
80+
81+
82+
If the *wipe free space* command was used on the same file system, the file probably
83+
cannot be deleted regardless of the type of file system. See also [Shred files
84+
and wipe disks](/doc/shred-files-and-wipe-disks.html) for more information.
85+
86+
87+
The chances of recovery decline as data is written to the drive and as time passes.
88+
89+
90+
Immediately the file is deleted in a normal way (in other words, if it is not
91+
overwritten), the full contents still exist and full recovery is stil possible.
92+
To maximize the chance of recovery, avoid writing any data to the file system.
93+
This step is most important when there is little free space. Often the file system
94+
for which recovery is desired is also the primary file system, so the computer
95+
should be turned off and rebooted into a bootable operating system from a bootable
96+
CD or USB drive.
97+
98+
99+
Finally, run a file recovery tool. Do a search on the web for "undelete" or "file
100+
recovery."'
101+
- question: Why does BleachBit take a long time while filling up the hard drive?
102+
answer: 'Check under the System cleaner whether the option **Free disk space**
103+
104+
(version 5.0.2 and prior) or **Empty Space** (version 5.1.0 and later) is enabled.
105+
106+
The purpose is not to increase the amount of available space. Instead, its purpose
107+
108+
is to make previously deleted files unrecoverable.
109+
110+
111+
This feature works by creating large, empty files (see [Shred files and wipe disks](/doc/shred-files-and-wipe-disks.html)
112+
113+
for more information). The duration to wipe empty space depends on the speed of
114+
the
115+
116+
hardware and the free capacity, and it commonly takes more than five minutes.
117+
118+
119+
When the hard drive is full, BleachBit immediately deletes the file, and there
120+
will
121+
122+
be no net change in disk space.
123+
124+
125+
Wiping empty space is not necessary if your drive is protected with full-disk
126+
encryption
127+
128+
such as BitLocker or LUKS. Wiping works best on traditional hard drives. On solid-state
129+
130+
drives, it is less reliable, and frequent use contributes to wear.
131+
132+
133+
If wiping empty space is disabled, but BleachBit is still slow, look at the option
134+
135+
**Edit - Preferences - General - Overwrite Contents**. Enabling this option makes
136+
BleachBit
137+
138+
slower because more work is required to make files unrecoverable.'
139+
- question: I closed BleachBit while it was working for a long time, and now my hard
140+
drive is full. How do I fix it?
141+
answer: 'Run BleachBit, and clean the option **System - Temporary Files**. On Linux,
142+
also clean **System - Cache**. This will delete one or more files that are gigantic
143+
and have random filenames.
144+
145+
146+
In case you are using the command line or another application to delete these
147+
files, the default location on Linux is `~/.cache/`. If it is not the same partition,
148+
`/tmp/` is also used. On Windows, the default locations are `%TMP%`. If there
149+
are other fixed drives such as `D:`, they are also used.
150+
151+
152+
If you changed the default options under **Preferences - Drives**, look there
153+
for the large files.
154+
155+
156+
If you cannot boot Ubuntu because the disk is full, use the [Ubuntu Recovery Mode](https://wiki.ubuntu.com/RecoveryMode)
157+
like this:
158+
159+
160+
1. Reboot the system.
161+
162+
1. Choose the boot option *Advanced options for Ubuntu*.
163+
164+
1. Choose a recent kernel with *(recovery mode)*.
165+
166+
1. In the Recovery Menu, choose _clean_. Note: this will mount your filesystem.
167+
168+
1. If this cleans enough space, boot normally and then clean the cache as mentioned
169+
above.
170+
171+
1. Otherwise, choose _root_ from the Recovery Menu.
172+
173+
1. Type this command to switch to your normal user account: <tt>su <i>username</i>
174+
-</tt>. (Replace _username_ with your username.)
175+
176+
1. Run this command to clean the user''s cache: `rm -rf ~/.cache/`.
177+
178+
1. Reboot.
179+
180+
181+
In the future, you may avoid this situation by disabling the BleachBit option
182+
**System - Free Disk Space**. Otherwise, do not interrupt BleachBit while it is
183+
working.'
184+
- question: How many passes does BleachBit make for the overwrite file option (shredding
185+
file)?
186+
answer: See [Shred files and wipe disks](/doc/shred-files-and-wipe-disks.html).
187+
- question: How do I see BleachBit in my own language on Microsoft Windows?
188+
answer: 'There are a few ways to affect the language of the BleachBit user interface.
189+
190+
191+
In the Windows search bar, type "Language settings" and open it. Under the Windows
192+
display language, choose the preferred language, and then restart BleachBit.
193+
194+
195+
To force BleachBit to always show in English, you have a few options:
196+
197+
198+
* Download and install the English installer instead of the regular installer.
199+
200+
* If using the regular (non-English-only) installer, uncheck the option to install
201+
translations.
202+
203+
* Manually delete the translations. The default location for translations is `c:\Program
204+
Files (x86)\BleachBit\share\locale`.
205+
206+
207+
The language chosen in the BleachBit installer does not affect the BleachBit application:
208+
it affects only the language of the installer.
209+
210+
211+
Since [BleachBit 4.9.0 alpha](https://www.bleachbit.org/news/bleachbit-490-alpha),
212+
there is an option in the BleachBit preferences to change the language ([video
213+
demonstration](https://github.com/bleachbit/bleachbit/issues/1758#issuecomment-2603127349)).
214+
Most changes take effect immediately. To reflect changes for the application menu,
215+
restart the application.'
216+
things_to_know:
217+
- question: What is format for the versioning number system?
218+
answer: 'Since BleachBit version 1.0 the numbering system is like that of GNOME,
219+
Linux between 1.0 and 2.6, and other projects: the format is basically *a.b*.
220+
When *b* is odd like 1.1, it is an unstable release (alpha or beta), and when
221+
*b* is even like 1.2, it is a stable release. Also, *b* can be greater than 9,
222+
so version 1.10 is newer than version 1.8.'
223+
- question: Should I delete cache?
224+
answer: 'Cache generally improves the performance of your computer. For example,
225+
browser cache prevents many files (such as pieces of web pages) from being downloaded
226+
again. Getting the file from the cache is much faster than downloading it&mdash;even
227+
with fast bandwidth. Applications (such as web browsers) normally delete the useless
228+
parts of cache to prevent it from growing too large and to make room for new,
229+
potentially-useful data.
230+
231+
232+
Yet, cache contains content you have viewed and can be used to reconstruct some
233+
of your browsing history. Especially for applications that you deleted, some cache
234+
is never used, so the space is wasted. Finally, deleting a large cache saves time
235+
and storage space before making a backup.'
236+
- question: Should I delete cookies?
237+
answer: 'Cookies are not inherently evil or dangerous. The following statements
238+
are *false*:
239+
240+
241+
* Cookies have no uses besides advertising
242+
243+
* Cookies can infect a computer like a virus
244+
245+
* Cookies cause popup ads
246+
247+
* Cookies can read arbitrary information from your computer (such as your name,
248+
your credit card, or private documents)
249+
250+
251+
Cookies perform useful functions such as maintaining your login information: this
252+
saves you the time of logging in again. Many web sites use cookies to make honest
253+
improvements such as simplifying confusing navigation. Cookies rarely contain
254+
personally identifiable information (such as a name or email address). With a
255+
high degree of success (but a greater hassle for the web operator), web sites
256+
can still track visitors who have cookies disabled (using unique information such
257+
as IP address, user agent, plugins, etc), so disabling cookies may not have the
258+
intended effect.
259+
260+
261+
On the other hand, some web sites use tricks (e.g., "evercookie" technology) to
262+
resurrect deleted cookies and try to track users between browsers on the same
263+
computer. Using another trick, cookies can track visitors between web sites for
264+
behavioural ad targeting: for example, once you visited an online camping store,
265+
and suddenly every other web site shows you ads for that camping store.'
266+
- question: Is BleachBit "safe"?
267+
answer: BleachBit identifies and organizes the files you are most likely want to
268+
delete. For a few options which are most likely to cause you regret, it shows
269+
a popup warning. In that sense, BleachBit is much safer for a novice computer
270+
user than poking through the random directories hunting for files to delete. On
271+
the other hand, if the saying "One man's trash is another man's treasure" were
272+
not true or the saying "one size fits all" applied here, BleachBit would have
273+
no options. Carefully read the descriptions and warnings, and do not choose any
274+
options you do not understand or which make you uncomfortable.
275+
- question: Will BleachBit make my computer faster?
276+
answer: 'BleachBit probably will not make your computer faster in general, but there
277+
are two specific ways you may see your computer become faster. First, by removing
278+
excess files, you may see an improvement in the speed of virus scanning and for
279+
disk backups. Second, vacuuming SQLite databases speed up applications that use
280+
them. Firefox, Safari, and Google Chrome are some applications that stores various
281+
data, such as URL history, in an SQLite database. With heavy browsing, the databases
282+
become fragmented and bloated, and this happens at a level higher than the disk
283+
storage, so standard disk defragmentation tools are completely useless. BleachBit
284+
shrinks the SQLite database (saving disk space and disk I/O effort) and defragments
285+
them. You are most likely to see a dramatic benefit by not vacuuming for a while,
286+
using the application heavily, and then vacuuming it once, but to keep the application
287+
running quickly, vacuum often. Vacuuming is not a single solution to all performance
288+
problems, but it does complement other solutions. People buy faster computers
289+
with better CPUs and more RAM, but hard drive technology (other than the rare
290+
SSDs) has not become much faster than they were years ago. The hard disk is often
291+
the bottleneck, and vacuuming is one way to overcome this limitation.
292+
293+
294+
Yet, deleting cache may make your computer slower because data will have to be
295+
re-downloaded or re-generated.'

0 commit comments

Comments
 (0)