GitLab

Fixes syntax problem introduced in e80f093c.
For some reason I don't understand, the script works either way.

On #17199 (and possibly #17228) I've seen breakage that seems to be caused by
udevadm trigger: the Greeter starts just fine, but on login, systemd-logind is
confused about the state of FDs (for /dev/dri/card{0,1}) it passes to X.Org:
when amnesia's X.Org starts, it gets passed paused FDs which makes it abort.
I suspect that's because at least one of /dev/dri/card{0,1} seem to briefly
disappear and come back again when we run udevadm trigger.

So let's try to avoid replaying kernel events for graphics-related devices.

Change the name of the database that will be opened by default (if it
exists) when KeePassXC is started to "Passwords.kdbx".

Previously, that was "keepassx.kdbx", because old KeePassX used that
name, but we decided to embrace the default of KeePassXC now.

The argument passed to sort_gpus() looks like this:

  [{'Slot': '00:02.0',
    'Class': 'VGA compatible controller [0300]',
    'Vendor-code': '8086',
    'Vendor': 'Intel Corporation',
    'Device-code': '5917',
    'Device': 'UHD Graphics 620',
    'SVendor': 'Lenovo [17aa]',
    'SDevice': 'UHD Graphics 620 [225c]',
    'Rev': '07'}]

So sorting the list based on whether the Vendor ends with "[8086]" did not do
what we want, i.e. sort Intel GPUs last (which we do because the Plymouth
message will be truncated, and we want to display the most relevant GPUs first,
which usually are not the Intel integrated GPU).

This will be needed for #17902.

This reverts commit 03dd03b8.

The reverted commit contains an unrelated change: disabling the
extension signing hacks. That was supposed to be in a separate commit,
but it's fine to revert it too now that the related patches have been
refreshed.

Otherwise this command fails because "Daemon not running",
and thus we abort our wrapper script and Electrum won't start.

refs #17828

There is no langpack tarball for the 10.x nightly builds, so let's
just skip all other locales and focus on getting the browser starting
for now.

This code has been a no-op in practice since at least Tails 4.0.
We've decided to reject #17276 and investigate what the biggest
problems are for email in Tails with slow/shitty Internet connections:
default'ing to IMAP may, or may not, be part of these problems.

Closes #17276

As tails-spoof-mac is running as root, its messages cannot be translated
according to the user settings. This commit solves this problem by reading the
localization settings from the environment (/etc/default/locale) in
tails-spoof-mac initialization. To make this work, we also set up the desired
localization environment before launching tails-unblock-network and
tails-spoof-mac.

On MAC spoofing failure, include the name of the disabled network card in the title of the notification

That was the intention since 988b4186
but in that commit, we forgot to replace gettext with eval_gettext
when introducing variables in the translatable string. Let's fix this
and accordingly, drop the test suite workaround for this bug.

refs: #17784

This will ease my review of !70 and future work on the panic mode
code paths.

Delegate the discover of interface names to udev, instead of relying
on reading and parsing /sys and lspci ourself, to make the discover
more resilient to missing files, bus agnostic (allowing to discover
non PCI devices like USB ones), and explicit (using udev's own hwdb).

Suggested-by: ShellCheck
Documentation: https://www.shellcheck.net/wiki/SC2148

Suggested-by: ShellCheck
Documentation: https://www.shellcheck.net/wiki/SC2145

Suggested-by: ShellCheck
Documentation: https://www.shellcheck.net/wiki/SC2068

this takes in consideration the case of revision or other message that
might follow the device code.
I don't have HW that has revisions, so I don't know if they are put
before or after the device code.

The code is now defensive on this: the device code is extracted as the
last block which might look like a device code, and the rest is kept as
device name.

the codes are put at the left: this makes it less probable that they are
trimmed away.

filtering with -d::0300 is enough

just run with "doctest" on the cmdline

We'll get a KeyError for the Debian-gdm user that now owns a preset,
since we try to find 'HOME' in its environment, but it's not defined.

Udev may close child processes when a process associated with a rule
(/etc/udev/rules) terminates. As mac spoofing notifications processes
are launched in background, with a static wait, they may be killed
before the message is effectively displayed.
This patch makes tails-spoof-mac wait for those processes before exiting.
It may makes tails-spoof-mac wait indefinitely. However, udev will ensure
it terminates after 120 seconds.

This reverts commit d2a4be58.

(/etc/udev/rules) terminates. As mac spoofing notifications processes
are launched in background, with a static wait, they may be killed
before the message is effectively displayed.
This patch makes tails-spoof-mac wait for those processes before
exiting. It may makes tails-spoof-mac wait indefinitely. However,
udev will ensure it terminates after 120 seconds.

This reverts commit 64e7378e.

Udev may close child processes when a process associated with a rule
(/etc/udev/rules) terminates. As mac spoofing notifications processes
are launched in background, with a static wait, they may be killed before
the message is effectively displayed.
This patch disable the background call of the notifications messages to
ensure they wont be killed.

... and disable it by default.

To make it easier to persist all of these settings.

Setting that env var does not seem to work.