- 24 Jul, 2020 1 commit
-
-
boyska authored
-
- 23 Jul, 2020 3 commits
-
-
intrigeri authored
-
- 21 Jul, 2020 16 commits
-
-
sajolida authored
-
IkiWiki authored
-
sajolida authored
-
sajolida authored
-
segfault authored
I see that this is not super obvious, but KeyboardSettingUI.apply() assumes that the keyboard setting was changed by the user, so it sets IS_DEFAULT (which is somewhat misnamed, it should rather be WAS_SET_AUTOMATICALLY (or WAS_SET_BY_USER, with the opposite value)) to false. When the keyboard layout is changed automatically because the language was changed, we want to set IS_DEFAULT to true, so we don't call KeyboardSettingUI.apply(), but directly self._setting.save(). What was missing was the call to apply_layout_to_current_screen(), which was causing #17794.
-
boyska authored
the previous behaviour was confusing: changing the language was changing the keyboard layout in the UI, but not really changing it.
-
geb authored
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.
-
intrigeri authored
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
-
IkiWiki authored
-
IkiWiki authored
-
sajolida authored
-
- 20 Jul, 2020 5 commits
-
-
intrigeri authored
Before 91674552, FindFailed inherited from RuntimeError, but it now inherits from StandardError, so we did not catch this exception anymore, and thus: - The scenario aborted immediately, instead of testing other locales. - We lacked the nice "Unsafe Browser failed to launch in the following locale(s): " message ⇒ need to read debug.log to figure out which locale failed. This commit does *not* fix another problem though: if the Unsafe Browser did start but the expected startup page is not visible, then we would leave it open and testing the next language will fail.
-
intrigeri authored
It's a known-special case, due to advertising the homepage to be RTL, while actually having English text (until those strings are actually translated), which results in weird behavior. Better ensure our test suite always exercises this case, rather than see the occasional seemingly random test failure, that cannot be triaged without looking at the debug log.
-
intrigeri authored
Merge branch 'stable' into wip/bugfix/17784-make-MAC-spoofing-failure-msgs-more-useful-and-resilient
-
boyska authored
A bug in the rendering of dots in RTL languages provoked an unrelated test case to be broken. This fixes the problem removing the dot from the image, so that it displayed incorrectly is less than a problem.
- 19 Jul, 2020 9 commits
- 18 Jul, 2020 6 commits
-
-
sajolida authored
-