Project Number Date
test_Tails_ISO_codespell 10 24 Jun 2025, 12:49

Failures Overview

The following summary displays scenarios that failed.

Feature: Untrusted partitions
Tags: @product
2:36.808
Scenario Tails ignores a swap volume and another Tails that are on an internal hard drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.021
Steps
Given a computer 0.562
And I temporarily create a 100 MiB disk named "swap" 0.130
And I create a gpt swap partition on disk "swap" 16.142
And I plug SATA drive "swap" 1.084
And I temporarily create a 2 GiB disk named "live_hd" 0.076
And I write the Tails ISO image to disk "live_hd" 32.491
And I plug SATA drive "live_hd" 1.165
When I start Tails with network unplugged and I login 1:45.154
try_for() 
try_for() timeout expired
Last ignored exception was: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/gdm-env'
./features/support/helpers/remote_shell.rb:71:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/dogtail.rb:80:in `new'
./features/support/helpers/dogtail.rb:80:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/usb.rb:108:in `new'
./features/step_definitions/usb.rb:108:in `greeter'
./features/step_definitions/common_steps.rb:460:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/common_steps.rb:459:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:263:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:459:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:263:in `/^I start Tails( from DVD)?( with network unplugged)?( and I login)?$/'
features/untrusted_partitions.feature:14:in `When I start Tails with network unplugged and I login'
Then a "swap" partition was detected by Tails on drive "swap" 0.000
And drive "live_hd" is detected by Tails 0.000
But Tails has no disk swap enabled 0.000
And drive "live_hd" is not mounted 0.000
After features/support/hooks.rb:330 5.660 
SCENARIO FAILED: 'Tails ignores a swap volume and another Tails that are on an internal hard drive' (at time 00:02:57)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/00:02:57_Tails_ignores_a_swap_volume_and_another_Tails_that_are_on_an_internal_hard_drive.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/00:02:57_Tails_ignores_a_swap_volume_and_another_Tails_that_are_on_an_internal_hard_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/00:02:57_Tails_ignores_a_swap_volume_and_another_Tails_that_are_on_an_internal_hard_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/00:02:57_Tails_ignores_a_swap_volume_and_another_Tails_that_are_on_an_internal_hard_drive.journal
After features/support/hooks.rb:100 0.405
Feature: Time syncing
Tags: @product @check_tor_leaks
34.435
Scenario I can connect to obfs4 bridges having a clock East of UTC while hiding that I am using Tor
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Before features/support/hooks.rb:507 0.016
Steps
Given I have started Tails from DVD without network and logged in 10.813
When I bump the system time with "+8 hours +15 minutes" 1.545
And all notifications have disappeared 11.516
And I capture all network traffic 0.005
And the network is plugged 0.106
And the Tor Connection Assistant autostarts 4.638
# Anti-test: Users east of UTC can't connect to obfs4 bridges
And I configure some obfs4 bridges in the Tor Connection Assistant in hide mode without connecting 5.808
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:637:in `block (2 levels) in <top (required)>'
./features/step_definitions/tor.rb:499:in `tca_configure'
./features/step_definitions/tor.rb:628:in `/^I configure (?:some|the) (persistent )?(\w+) bridges (from a QR code )?in the Tor Connection Assistant(?: in (easy|hide) mode)?( without connecting|)$/'
features/time_syncing.feature:90:in `And I configure some obfs4 bridges in the Tor Connection Assistant in hide mode without connecting'
And I click "Connect to Tor" 0.000
Then the Tor Connection Assistant reports that it failed to connect 0.000
# The "Fix Clock" button allows users to recover from this bug
When I set the time zone in Tor Connection to "Asia/Shanghai" 0.000
Then the system clock is less than 20 minutes incorrect 0.000
# "Asia/Shanghai" is UTC+08:00 all year long (no DST)
And the displayed clock is less than 20 minutes incorrect in "+08:00" 0.000
When I click "Connect to Tor" 0.000
Then I wait until Tor is ready 0.000
And all Internet traffic has only flowed through the configured bridges 0.000
# check that htpdate has done its job
And the system clock is less than 5 minutes incorrect 0.000
And the displayed clock is less than 5 minutes incorrect in "+08:00" 0.000
After features/support/hooks.rb:515 0.037
After features/support/hooks.rb:330 7.215 
SCENARIO FAILED: 'I can connect to obfs4 bridges having a clock East of UTC while hiding that I am using Tor' (at time 00:31:49)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/00:31:49_I_can_connect_to_obfs4_bridges_having_a_clock_East_of_UTC_while_hiding_that_I_am_using_Tor.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/00:31:49_I_can_connect_to_obfs4_bridges_having_a_clock_East_of_UTC_while_hiding_that_I_am_using_Tor.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/00:31:49_I_can_connect_to_obfs4_bridges_having_a_clock_East_of_UTC_while_hiding_that_I_am_using_Tor.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/00:31:49_I_can_connect_to_obfs4_bridges_having_a_clock_East_of_UTC_while_hiding_that_I_am_using_Tor.journal
After features/support/hooks.rb:100 0.050
Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
13:39.249
Scenario Erasure of read and write disk caches of persistent data on shutdown
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.260
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13:39.249
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:139:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/erase_memory.feature:75:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I prepare Tails for memory erasure tests 0.000
When I fill a 128 MiB file with a known pattern on the persistent filesystem 0.000
When I trigger shutdown 0.000
Then I find very few patterns in the guest's memory after 20 seconds 0.000
After features/support/hooks.rb:330 7.402 
SCENARIO FAILED: 'Erasure of read and write disk caches of persistent data on shutdown' (at time 01:10:28)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/01:10:28_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/01:10:28_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/01:10:28_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/01:10:28_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.journal
After features/support/hooks.rb:100 0.008
Feature: Additional software
Tags: @product @check_tor_leaks @slow
6:46.706
Scenario My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Before features/support/hooks.rb:507 0.007
Steps
Given a computer 0.455
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 5:38.464
When I uninstall "popularity-contest" using apt 32.161
And I accept removing "popularity-contest" from Additional Software 2.798
Then "popularity-contest" is not in the list of Additional Software 0.849
When I start Synaptic 31.977
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: "synaptic" application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/apt.rb:143:in `new'
./features/step_definitions/apt.rb:143:in `/^I start Synaptic$/'
features/additional_software_packages.feature:59:in `When I start Synaptic'
And I update APT using Synaptic 0.000
And I install "cowsay" using Synaptic 0.000
And I accept adding "cowsay" to Additional Software 0.000
Then Additional Software is correctly configured for package "cowsay" 0.000
When I uninstall "cowsay" using apt 0.000
And I refuse removing "cowsay" from Additional Software 0.000
Then Additional Software is correctly configured for package "cowsay" 0.000
When I start "Additional Software" via GNOME Activities Overview 0.000
And I remove "cowsay" from the list of Additional Software using Additional Software GUI 0.000
Then "cowsay" is not in the list of Additional Software 0.000
When I install "cowsay" using apt 0.000
And I refuse adding "cowsay" to Additional Software 0.000
Then "cowsay" is not in the list of Additional Software 0.000
After features/support/hooks.rb:515 0.090
After features/support/hooks.rb:330 7.323 
SCENARIO FAILED: 'My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic' (at time 02:25:49)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/02:25:49_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.file_content_var_log_boot.log
Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/02:25:49_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.file_content_run_live-additional-software_log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/02:25:49_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/02:25:49_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/02:25:49_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/02:25:49_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/02:25:49_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/02:25:49_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/02:25:49_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.journal
After features/support/hooks.rb:100 0.009
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
10:29.745
Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Before features/support/hooks.rb:507 0.015
Steps
Given a computer 0.274
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 4:22.290
And I configure APT to prefer an old version of cowsay 0.033
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 54.872
And I accept adding "cowsay" to Additional Software 6.736
And Additional Software is correctly configured for package "cowsay" 4.819
And I shutdown Tails and wait for the computer to power off 11.823
And I start Tails from USB drive "__internal" with network unplugged 1:59.478
And I enable persistence 27.972
# We need to add back this custom APT source for the Additional Software
# install step, as it was not saved in persistence
And I configure APT to prefer an old version of cowsay 0.356
# Prevent the "Warning: virtual machine detected!" notification from racing
# with the one we'll be interacting with below.
And I disable the tails-virt-notify-user.service user unit 0.929
And I log in to a new session 1:13.404
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 50.292
And I revert the APT tweaks that made it prefer an old version of cowsay 0.636
# We remove the newest package after it has been downloaded and before
# it is installed, so that the upgrade process fails
And I prepare the Additional Software upgrade process to fail 0.753
And the network is plugged 0.792
And Tor is ready 14.278
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:653:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:607:in `/^Tor is ready$/'
features/additional_software_packages.feature:100:in `And Tor is ready'
And available upgrades have been checked 0.000
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 0.000
And I can open the Additional Software configuration window from the notification 0.000
And I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged 0.000
And I enable persistence 0.000
# We need to add back this custom APT source for the Additional Software
# install step, as it was not saved in persistence
And I configure APT to prefer an old version of cowsay 0.000
And I log in to a new session 0.000
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 0.000
And I revert the APT tweaks that made it prefer an old version of cowsay 0.000
And the network is plugged 0.000
And Tor is ready 0.000
Then the Additional Software upgrade service has started 0.000
And the installed version of package "cowsay" is newer than "3.03+dfsg2-1" 0.000
After features/support/hooks.rb:515 0.056
After features/support/hooks.rb:330 6.478 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 02:36:29)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/02:36:29_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_var_log_boot.log
Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/02:36:29_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_run_live-additional-software_log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/02:36:29_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/02:36:29_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/02:36:29_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/02:36:29_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/02:36:29_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/02:36:29_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/02:36:29_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal
After features/support/hooks.rb:100 0.024
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
1:29.858
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.225
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:29.858
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_upgrade.feature:127:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.000
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.000
And the signing key used by the Upgrader is outdated 0.000
But a current signing key is available on our website 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.000
After features/support/hooks.rb:330 7.481 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 03:19:12)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/03:19:12_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/03:19:12_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/03:19:12_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/03:19:12_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000
Feature: Using Evince
Tags: @product @not_release_blocker
1:12.995
Scenario I cannot view a PDF file stored in persistent /home/amnesia/.gnupg
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.026
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:12.995
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/evince.feature:54:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I copy "/usr/share/cups/data/default-testpage.pdf" to "/home/amnesia/.gnupg" as user "amnesia" 0.000
Then the file "/home/amnesia/.gnupg/default-testpage.pdf" exists 0.000
Given I start monitoring the AppArmor log of "/usr/bin/evince" 0.000
And I try to open "/home/amnesia/.gnupg/default-testpage.pdf" with Evince 0.000
Then Evince tells me it cannot open "/home/amnesia/.gnupg/default-testpage.pdf" 0.000
And AppArmor has denied "/usr/bin/evince" from opening "/home/amnesia/.gnupg/default-testpage.pdf" 0.000
After features/support/hooks.rb:330 7.673 
SCENARIO FAILED: 'I cannot view a PDF file stored in persistent /home/amnesia/.gnupg' (at time 03:48:09)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/03:48:09_I_cannot_view_a_PDF_file_stored_in_persistent__home_amnesia_.gnupg.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/03:48:09_I_cannot_view_a_PDF_file_stored_in_persistent__home_amnesia_.gnupg.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/03:48:09_I_cannot_view_a_PDF_file_stored_in_persistent__home_amnesia_.gnupg.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/03:48:09_I_cannot_view_a_PDF_file_stored_in_persistent__home_amnesia_.gnupg.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
1:11.900
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Steps
Given a computer 0.233
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:11.666
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/hardware_failure.feature:29:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
features/hardware_failure.feature:23:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
When Tails detects disk read failures on the SquashFS 0.000
Then I see a disk failure message 0.000
Then I can open the hardware failure documentation from the disk failure message 0.000
After features/support/hooks.rb:330 7.784 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 04:01:08)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/04:01:08_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/04:01:08_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/04:01:08_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/04:01:08_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
33.435
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given a computer 0.294
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 22.235
When Tails detects disk read failures on the boot device with a target error 0.885
Then I see a disk failure message 10.019
FindTextFailed 
FindTextFailed (FindTextFailed)
./features/support/helpers/screen.rb:274:in `rescue in wait_text'
./features/support/helpers/screen.rb:266:in `wait_text'
./features/step_definitions/hardware.rb:39:in `/^I see a disk failure message$/'
features/hardware_failure.feature:31:in `Then I see a disk failure message'
features/hardware_failure.feature:25:in `Then I see a disk failure message'
Then I can open the hardware failure documentation from the disk failure message 0.000
After features/support/hooks.rb:330 6.093 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 04:03:50)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/04:03:50_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/04:03:50_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/04:03:50_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/04:03:50_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
2:17.834
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 11.781
When I log in to a new session in French (fr) 47.431
Then the keyboard layout is set to "fr" 0.145
When the network is plugged 0.066
And Tor is ready 19.950
Then I successfully start the Unsafe Browser 20.884
And I kill the Unsafe Browser 6.812
When I enable the screen keyboard 0.653
Then the screen keyboard works in Tor Browser 30.107
cannot 
cannot find TorBrowserNewTabButton.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:468:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:455:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:411:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:47:in `Then the screen keyboard works in Tor Browser'
features/localization.feature:30:in `Then the screen keyboard works in Tor Browser'
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "fr" 0.000
After features/support/hooks.rb:330 8.702 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#4)' (at time 04:50:12)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/04:50:12_Tails_is_localized_for_every_tier-1_language,_Examples___4_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/04:50:12_Tails_is_localized_for_every_tier-1_language,_Examples___4_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/04:50:12_Tails_is_localized_for_every_tier-1_language,_Examples___4_.journal
After features/support/hooks.rb:100 0.000
Feature: Spoofing MAC addresses
Tags: @product
52.142
Scenario MAC address spoofing is successful
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 11.091
And I capture all network traffic 0.088
When I log in to a new session 29.078
And the network is plugged 0.099
And Tor is ready 11.785
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:653:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:607:in `/^Tor is ready$/'
features/mac_spoofing.feature:27:in `And Tor is ready'
Then 1 network interface is enabled 0.000
And the 1st network device has a spoofed MAC address configured 0.000
When I hotplug a network device and wait for it to be initialized 0.000
Then 2 network interfaces are enabled 0.000
And the 2nd network device has a spoofed MAC address configured 0.000
And no network device leaked the real MAC address 0.000
After features/support/hooks.rb:330 6.156 
SCENARIO FAILED: 'MAC address spoofing is successful' (at time 05:18:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/05:18:26_MAC_address_spoofing_is_successful.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/05:18:26_MAC_address_spoofing_is_successful.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/05:18:26_MAC_address_spoofing_is_successful.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/05:18:26_MAC_address_spoofing_is_successful.journal
After features/support/hooks.rb:100 0.043
Feature: Packages are up-to-date
Tags: @source
3.685
Scenario All packages are up-to-date
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:532 0.000
Steps
Given I have the build manifest for the image under test 0.000
Then all packages listed in the build manifest are up-to-date 3.685
Command 
Command failed (pid 51868 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_codespell/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_codespell/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_codespell/tmp/tails-amd64-codespell@a79b8ced92+stable@9c8c625ee5-20250624T0344Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_codespell/tmp/tails-amd64-codespell@a79b8ced92+stable@9c8c625ee5-20250624T0344Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - ublock-origin (1.62.0+dfsg-1) to Debian trixie (1.62.0+dfsg-2)
 (CommandFailed)
/var/lib/jenkins/workspace/test_Tails_ISO_codespell/features/support/helpers/misc_helpers.rb:321:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_codespell/features/support/helpers/misc_helpers.rb:314:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_codespell/features/support/helpers/misc_helpers.rb:314:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_codespell/features/step_definitions/needed_package_updates.rb:8:in `/^all packages listed in the build manifest are up-to-date$/'
features/needed_package_updates.feature:12:in `Then all packages listed in the build manifest are up-to-date'
After features/support/hooks.rb:539 0.000
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
18.903
Scenario Booting Tails from a USB drive with a disabled persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 13.240
When I log in to a new session without activating the Persistent Storage 5.662
<false> 
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/common_steps.rb:519:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
features/persistence.feature:14:in `When I log in to a new session without activating the Persistent Storage'
Then Tails is running from USB drive "__internal" 0.000
And persistence is disabled 0.000
But a Tails persistence partition exists on USB drive "__internal" 0.000
After features/support/hooks.rb:330 5.331 
SCENARIO FAILED: 'Booting Tails from a USB drive with a disabled persistent partition' (at time 05:32:05)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/05:32:05_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/05:32:05_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/05:32:05_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/05:32:05_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:32.102
Scenario Creating persistence from the Welcome Screen
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 1:32.102
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ without\ a\ persistent\ partition\ and\ stopped\ at\ Tails\ Greeter's\ login\ screen$/'
features/persistence.feature:97:in `Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen'
And I enable persistence creation in Tails Greeter 0.000
And I log in to a new session expecting no warning about the Persistent Storage not being activated 0.000
Then I create a persistent partition with the default settings using the wizard that was already open 0.000
After features/support/hooks.rb:330 5.904 
SCENARIO FAILED: 'Creating persistence from the Welcome Screen' (at time 05:54:52)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/05:54:52_Creating_persistence_from_the_Welcome_Screen.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/05:54:52_Creating_persistence_from_the_Welcome_Screen.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/05:54:52_Creating_persistence_from_the_Welcome_Screen.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/05:54:52_Creating_persistence_from_the_Welcome_Screen.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
2:54.208
Scenario Persistent Greeter options
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 26.894
When I enable persistence 1:27.835
Then no persistent Greeter options were restored 20.095
When I set all Greeter options to non-default values 39.382
cannot 
cannot find TailsGreeterDisableMACSpoofing.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/mac_spoofing.rb:13:in `/^I disable MAC spoofing in Tails Greeter$/'
./features/step_definitions/usb.rb:1581:in `/^I set all Greeter options to non-default values$/'
features/persistence.feature:106:in `When I set all Greeter options to non-default values'
And I log in to a new session in German (de) after having activated the Persistent Storage 0.000
Then all Greeter options are set to non-default values 0.000
When I cold reboot the computer 0.000
And the computer reboots Tails 0.000
Given I enable persistence 0.000
Then persistent Greeter options were restored 0.000
When I log in to a new session after having activated the Persistent Storage 0.000
Then all Greeter options are set to non-default values 0.000
After features/support/hooks.rb:330 7.147 
SCENARIO FAILED: 'Persistent Greeter options' (at time 05:57:52)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/05:57:52_Persistent_Greeter_options.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/05:57:52_Persistent_Greeter_options.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/05:57:52_Persistent_Greeter_options.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/05:57:52_Persistent_Greeter_options.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:38.552
Scenario Changing the Persistent Storage passphrase
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.889
# Note that if anything fails after the passphrase was changed and
# before it's changed back below, subsequent scenarios might fail
# because the Persistent Storage doesn't have the expected passphrase.
When I change the passphrase of the Persistent Storage 1:16.662
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:475:in `/^I change the passphrase of the Persistent Storage( back to the original)?$/'
features/persistence.feature:121:in `When I change the passphrase of the Persistent Storage'
And I shutdown Tails and wait for the computer to power off 0.000
Then I start Tails from USB drive "__internal" with network unplugged and I login with the changed persistence passphrase 0.000
And I change the passphrase of the Persistent Storage back to the original 0.000
After features/support/hooks.rb:330 21.854 
SCENARIO FAILED: 'Changing the Persistent Storage passphrase' (at time 05:59:50)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/05:59:50_Changing_the_Persistent_Storage_passphrase.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/05:59:50_Changing_the_Persistent_Storage_passphrase.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/05:59:50_Changing_the_Persistent_Storage_passphrase.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:22.890
Scenario Dotfiles persistence
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.067
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:22.890
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:136:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
When I write some dotfile expected to persist 0.000
And I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then the expected persistent dotfile is present in the filesystem 0.000
After features/support/hooks.rb:330 7.055 
SCENARIO FAILED: 'Dotfiles persistence' (at time 06:03:32)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/06:03:32_Dotfiles_persistence.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/06:03:32_Dotfiles_persistence.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/06:03:32_Dotfiles_persistence.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/06:03:32_Dotfiles_persistence.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:20.634
Scenario Feature activation fails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 20.238
And I create a symlink "/home/amnesia/Persistent" to "/etc" 0.094
When I try to enable persistence 0.301
Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated 1:0.001
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:1724:in `/^the Welcome Screen tells me that the Persistent Folder feature couldn't be activated$/'
features/persistence.feature:146:in `Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated'
When I log in to a new session after having activated the Persistent Storage 0.000
And all notifications have disappeared 0.000
Then the Persistent Storage settings tell me that the Persistent Folder feature couldn't be activated 0.000
And all tps features are enabled 0.000
And all tps features but the first one are active 0.000
After features/support/hooks.rb:330 18.368 
SCENARIO FAILED: 'Feature activation fails' (at time 06:05:08)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/06:05:08_Feature_activation_fails.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/06:05:08_Feature_activation_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/06:05:08_Feature_activation_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/06:05:08_Feature_activation_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:38.409
Scenario Manual filesystem repair is successful
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 22.195
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 15.698
When I try to enable persistence 0.514
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 1:0.001
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:1732:in `/^the Welcome Screen tells me that filesystem errors were found on the Persistent Storage$/'
features/persistence.feature:176:in `Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage'
When I repair the filesystem of the Persistent Storage 0.000
Then the Welcome Screen tells me that the filesystem was repaired successfully 0.000
And the filesystem of the Persistent Storage was repaired 0.000
When I close the filesystem repair dialog 0.000
Then persistence is successfully enabled 0.000
After features/support/hooks.rb:330 16.096 
SCENARIO FAILED: 'Manual filesystem repair is successful' (at time 06:19:35)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/06:19:35_Manual_filesystem_repair_is_successful.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/06:19:35_Manual_filesystem_repair_is_successful.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/06:19:35_Manual_filesystem_repair_is_successful.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product @doc
1:15.159
Scenario Manual filesystem repair fails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.047
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 12.036
And the Persistent Storage filesystem is corrupted beyond what e2fsck can repair 0.645
When I try to enable persistence 2.383
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 1:0.093
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:1732:in `/^the Welcome Screen tells me that filesystem errors were found on the Persistent Storage$/'
features/persistence.feature:188:in `Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage'
When I repair the filesystem of the Persistent Storage 0.000
Then the Welcome Screen tells me that it failed to repair the Persistent Storage 0.000
When I log in to a new session 0.000
And all notifications have disappeared 0.000
# Now both WhisperBack and Tor Browser has started at the same
# time, so we do not know which window is focused. The steps about
# Tor Browser care about that, but the ones about WhisperBack do
# not, so we first deal with WhisperBack and then kill it to
# ensure that Tor Browser is focused.
Then WhisperBack is prefilled for fsck with summary: "Failed to repair the file system of your Persistent Storage" 0.000
And the file "/var/lib/gdm3/post-greeter-whisperback.json" is empty 0.000
When I close the "whisperback" window 0.000
Then the Tor Browser starts 0.000
And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:330 12.417 
SCENARIO FAILED: 'Manual filesystem repair fails' (at time 06:21:11)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/06:21:11_Manual_filesystem_repair_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/06:21:11_Manual_filesystem_repair_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/06:21:11_Manual_filesystem_repair_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Tails has a sane default configuration
Tags: @product
1:18.558
Scenario No unexpected error messages in the journal after booting from USB drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.035
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:18.558
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/sane_defaults.feature:24:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
Then there are no unexpected messages of priority "err" or higher in the journal 0.000
After features/support/hooks.rb:330 6.943 
SCENARIO FAILED: 'No unexpected error messages in the journal after booting from USB drive' (at time 06:51:10)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/06:51:10_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/06:51:10_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/06:51:10_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/06:51:10_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.journal
After features/support/hooks.rb:100 0.000
Feature: Tor Connection helps the user in connecting to Tor
Tags: @product
11.198
Scenario Starting Tor Connection before connecting to Wi-Fi
Steps
When I start "Tor Connection" via GNOME Activities Overview 11.198
cannot 
cannot find GnomeApplicationsMenu.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/common_steps.rb:1141:in `/^I start "([^"]+)" via GNOME Activities Overview$/'
features/tor_connection.feature:10:in `When I start "Tor Connection" via GNOME Activities Overview'
Then the Tor Connection Assistant reports that I am not connected to a local network 0.000
When I plug a Wi-Fi adapter 0.000
Then Tor Connection suggests me to connect to Wi-Fi 0.000
And I click on the Wi-Fi settings 0.000
And The Wi-Fi settings are displayed 0.000
After features/support/hooks.rb:330 5.665 
SCENARIO FAILED: 'Starting Tor Connection before connecting to Wi-Fi' (at time 07:01:52)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/07:01:52_Starting_Tor_Connection_before_connecting_to_Wi-Fi.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/07:01:52_Starting_Tor_Connection_before_connecting_to_Wi-Fi.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/07:01:52_Starting_Tor_Connection_before_connecting_to_Wi-Fi.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/07:01:52_Starting_Tor_Connection_before_connecting_to_Wi-Fi.journal
After features/support/hooks.rb:100 0.000
Feature: Tor stream isolation is effective
1:14.528
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Before features/support/hooks.rb:507 0.020
Steps
Given I have started Tails from DVD and logged in and the network is connected 1:14.528
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/tor_stream_isolation.feature:7:in `Given I have started Tails from DVD and logged in and the network is connected'
Feature: Tor stream isolation is effective
Tags: @product @check_tor_leaks @not_release_blocker
0.000
Scenario tails-security-check is using the Tails-specific SocksPort
Steps
When I monitor the network connections of tails-security-check 0.000
And I re-run tails-security-check 0.000
Then I see that tails-security-check is properly stream isolated after 10 seconds 0.000
After features/support/hooks.rb:515 0.051
After features/support/hooks.rb:330 5.545 
SCENARIO FAILED: 'tails-security-check is using the Tails-specific SocksPort' (at time 07:15:51)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/07:15:51_tails-security-check_is_using_the_Tails-specific_SocksPort.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/07:15:51_tails-security-check_is_using_the_Tails-specific_SocksPort.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/07:15:51_tails-security-check_is_using_the_Tails-specific_SocksPort.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/07:15:51_tails-security-check_is_using_the_Tails-specific_SocksPort.journal
After features/support/hooks.rb:100 0.000
Feature: Tor stream isolation is effective
1:17.124
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Before features/support/hooks.rb:507 0.011
Steps
Given I have started Tails from DVD and logged in and the network is connected 1:17.124
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/tor_stream_isolation.feature:7:in `Given I have started Tails from DVD and logged in and the network is connected'
Feature: Tor stream isolation is effective
Tags: @product @check_tor_leaks @not_release_blocker
0.000
Scenario tails-upgrade-frontend-wrapper is using the Tails-specific SocksPort
Steps
When I monitor the network connections of tails-upgrade-frontend-wrapper 0.000
And I re-run tails-upgrade-frontend-wrapper 0.000
Then I see that tails-upgrade-frontend-wrapper is properly stream isolated 0.000
After features/support/hooks.rb:515 0.033
After features/support/hooks.rb:330 5.672 
SCENARIO FAILED: 'tails-upgrade-frontend-wrapper is using the Tails-specific SocksPort' (at time 07:17:52)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/07:17:52_tails-upgrade-frontend-wrapper_is_using_the_Tails-specific_SocksPort.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/07:17:52_tails-upgrade-frontend-wrapper_is_using_the_Tails-specific_SocksPort.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/07:17:52_tails-upgrade-frontend-wrapper_is_using_the_Tails-specific_SocksPort.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/07:17:52_tails-upgrade-frontend-wrapper_is_using_the_Tails-specific_SocksPort.journal
After features/support/hooks.rb:100 0.000
Feature: Tor stream isolation is effective
Tags: @product @check_tor_leaks
30.270
Scenario The Tor Browser is using the web browser-specific SocksPort
Steps
When I monitor the network connections of Tor Browser 0.076
And I start the Tor Browser 30.193
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: "Firefox" application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:1047:in `new'
./features/step_definitions/common_steps.rb:1047:in `block in launch_app'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/common_steps.rb:1046:in `launch_app'
./features/step_definitions/common_steps.rb:1101:in `launch_tor_browser'
./features/step_definitions/browser.rb:445:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:1046:in `launch_app'
./features/step_definitions/common_steps.rb:1101:in `launch_tor_browser'
./features/step_definitions/browser.rb:445:in `/^I start the Tor Browser( in offline mode)?$/'
features/tor_stream_isolation.feature:29:in `And I start the Tor Browser'
And the Tor Browser loads the startup page 0.000
Then I see that Tor Browser is properly stream isolated 0.000
After features/support/hooks.rb:515 0.174
After features/support/hooks.rb:330 12.644 
SCENARIO FAILED: 'The Tor Browser is using the web browser-specific SocksPort' (at time 07:19:31)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/07:19:31_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/07:19:31_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/07:19:31_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product @check_tor_leaks
55.020
Scenario Watching a WebM video
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Before features/support/hooks.rb:507 0.015
Steps
Given I have started Tails from DVD and logged in and the network is connected 17.932
When I start the Tor Browser 37.087
cannot 
cannot find TorBrowserNewTabButton.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:468:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:455:in `/^I start the Tor Browser( in offline mode)?$/'
features/torified_browsing.feature:45:in `When I start the Tor Browser'
And the Tor Browser loads the startup page 0.000
Then I can watch a WebM video in Tor Browser 0.000
After features/support/hooks.rb:515 0.052
After features/support/hooks.rb:330 6.797 
SCENARIO FAILED: 'Watching a WebM video' (at time 07:28:33)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/07:28:33_Watching_a_WebM_video.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/07:28:33_Watching_a_WebM_video.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/07:28:33_Watching_a_WebM_video.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/10/artifact/build-artifacts/07:28:33_Watching_a_WebM_video.journal
After features/support/hooks.rb:100 0.000