GitLab

In gettext-base < 1.8.2, like the one we had in Wheezy, gettext.sh
references the environment variable ZSH_VERSION, which we do not
set. This has prevented us from doing `set -u` in all gettext:ized
shell scripts unless we first initialize that variable before sourcing
gettext.sh.

Now that we install a new enough gettext-base, we can finally do this
and remove the initialization hacks.

Will-fix: #9371

I.e. also the Unsafe and I2P Browser's. The main reason is so we do
not need different images for these and the Tor browser in the
automated test suite. One may argue, though, that for the Unsafe
Browser this list of fonts would be fingerprintable, but I would be
surprised if it already isn't so due to the Tor Browser Firefox
patches.

The Tor Browser assumes that the working directory is the directory
where the browser lives (e.g. the executable). For instance, the
fonts.conf (for fontconfig) the Tor Browser uses looks for the fonts
in the "fonts" sub-directory of the current working directory. This
will fix issues with "empty boxes" as characters in the Save As/Open
dialoges.

Will-fix: #11097

E.g. for our custom/undocumented (but so far unused)
`--force-net-config` option.

The path hasn't existed for a long while, and places.sqlite hasn't
been created there for even longer.

... instead of polluting the complete environment with it.

It feels like it belongs better in the script where we actually start
Tor Launcher than the wrapper that makes root invoke it in the way we
want. Also, we have to think less about how sudo propagates
environment variables so we can simplify its setup.

To simplify some paths.

... where we have the Tor Browser. For consistency.

Let's not pretend the current script is similar to what upstream would
use, since it has Tails specific stuff in it.

... instead of the crazy workaround we had to use before. It turns out
you *can* use -app and -profile together, but only if -profile is
given last. It may be that it was fixed recently, because I'm pretty
sure it didn't work last time I wroked on this.

Also, in /usr/share/TorBrowser/Data/Browser (which is the "default"
profile directory relative to the Tor Launcher applocation.ini file)
the Caches directory must exist and be accessible for the tor-launcher
user even if -profile is used, so we just have to ensure it exists.

Will-fix: #7943

It didn't apply cleanly against the profile shipped in torbrowser-launcher
0.2.2-3, due to quilt patches that were not upstreamed yet.

Will-fix: #11078

Will-fix: #11007

Sadly this was missed so we won't have it in Tails 2.0.

Fix-committed: #11000

Revert "Enable and use the Debian jessie-proposed-updates APT repository, anticipating on the Jessie 8.3 point-release."

This reverts commit 2bf73b19.

Debian 8.3 has been released.

Fix-committed: #10898

This reverts commit 2f16f2d1.

In the final Tor Browser 5.5 release the window resizing issue that
caused issues for us in the automated test suite should be fixed.

Will-fix: #10892

Will-fix: #10983

Bugfix on 2.0~beta1.

Will-fix: #10925

Some USB input devices don't support autosuspend, see e.g.:
https://github.com/systemd/systemd/issues/340

This change might help fix #10850, but even if it doesn't, it makes
sense to me that we don't let laptop-mode-tools fiddle with this
on a Live system.

Refs: #10850

refs: #10943

It feels more maintainable to use a standalone file, than to patch an existing
one in /etc.

refs: #10943