Cucumber Reports (no 3) - Failures Overview

Project	Number	Date
test_Tails_ISO_test-suite-options	3	19 Jun 2025, 01:24

Feature: Additional software

7:10.089

Scenario My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.014

Before features/support/hooks.rb:507 0.007

Steps

Given a computer 0.303

And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 5:44.477

When I uninstall "popularity-contest" using apt 37.756

And I accept removing "popularity-contest" from Additional Software 2.337

Then "popularity-contest" is not in the list of Additional Software 2.877

When I start Synaptic 42.336

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

Hooks

After features/support/hooks.rb:515 0.103

After features/support/hooks.rb:330 9.429

Output 1

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 01:45:30)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/3/artifact/build-artifacts/01:45:30_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_test-suite-options/3/artifact/build-artifacts/01:45:30_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_test-suite-options/3/artifact/build-artifacts/01:45:30_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_test-suite-options/3/artifact/build-artifacts/01:45:30_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_test-suite-options/3/artifact/build-artifacts/01:45:30_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_test-suite-options/3/artifact/build-artifacts/01:45:30_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_test-suite-options/3/artifact/build-artifacts/01:45:30_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_test-suite-options/3/artifact/build-artifacts/01:45:30_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_test-suite-options/3/artifact/build-artifacts/01:45:30_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.012

Feature: Upgrading an old Tails USB installation

Tags: @product @automatic_upgrade

5:28.125

Scenario Upgrading an initial Tails installation with an incremental upgrade

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.008

Steps

Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.288

And no SquashFS delta is installed 0.437

And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.467

And Tails is fooled to think it is running version 6.0~testoverlayfs 0.095

And the file system changes introduced in version 6.2~testoverlayfs are not present 0.372

And the file system changes introduced in version 6.3~testoverlayfs are not present 0.542

When the network is plugged 0.162

And Tor is ready 29.317

Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.566

And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 21.235

Given I shutdown Tails and wait for the computer to power off 17.572

When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:0.452

Then Tails is running version 6.2~testoverlayfs 0.015

And all tps features are active 2.520

And the file system changes introduced in version 6.2~testoverlayfs are present 0.686

And only the 6.2~testoverlayfs SquashFS delta is installed 0.176

# Our IUK sets a release date that can make Tor bootstrapping impossible

Given Tails system time is magically synchronized 0.326

# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk

# but we need some way to force upgrading a second time in a row

# even if only the initially installed version is considered

And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.364

When the network is plugged 0.078

And Tor is ready 29.567

Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.972

And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.906

cannot

cannot find TailsUpgraderApplyUpgradeButton.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/usb.rb:1327:in `/^I can successfully install the incremental upgrade to version (.+)$/'
features/usb_upgrade.feature:107:in `And I can successfully install the incremental upgrade to version 6.3~testoverlayfs'

Given I shutdown Tails and wait for the computer to power off 0.000

When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000

Then Tails is running version 6.3~testoverlayfs 0.000

And all tps features are active 0.000

And the file system changes introduced in version 6.3~testoverlayfs are present 0.000

And only the 6.3~testoverlayfs SquashFS delta is installed 0.000

# Regression test for #17425 (i.e. the Upgrader would propose

# upgrading to the version that's already running)

Given Tails system time is magically synchronized 0.000

And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000

When the network is plugged 0.000

And Tor is ready 0.000

Then the Upgrader considers the system as up-to-date 0.000

# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)

And I successfully start the Unsafe Browser 0.000

And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000

Hooks

After features/support/hooks.rb:330 5.642

Output 1

SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:33:28)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/3/artifact/build-artifacts/02:33:28_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/3/artifact/build-artifacts/02:33:28_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/3/artifact/build-artifacts/02:33:28_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/3/artifact/build-artifacts/02:33:28_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal

After features/support/hooks.rb:100 0.036

Feature: Localization

Tags: @product @doc @slow @not_release_blocker

3:31.019

Scenario Outline Tails is localized for every tier-1 language

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.025

Steps

Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 10.976

When I log in to a new session in Persian (fa) 3:20.043

cannot

cannot find GnomeApplicationsMenuPersian.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:566:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:522: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/localization.feature:53:in `When I log in to a new session in Persian (fa)'
features/localization.feature:23:in `When I log in to a new session in <language> (<lang_code>)'

Then the keyboard layout is set to "ir" 0.000

When the network is plugged 0.000

And Tor is ready 0.000

Then I successfully start the Unsafe Browser 0.000

And I kill the Unsafe Browser 0.000

When I enable the screen keyboard 0.000

Then the screen keyboard works in Tor Browser 0.000

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 "ir" 0.000

Hooks

After features/support/hooks.rb:330 7.929

Output 1

SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#7)' (at time 03:56:36)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/3/artifact/build-artifacts/03:56:36_Tails_is_localized_for_every_tier-1_language,_Examples___7_.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/3/artifact/build-artifacts/03:56:36_Tails_is_localized_for_every_tier-1_language,_Examples___7_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/3/artifact/build-artifacts/03:56:36_Tails_is_localized_for_every_tier-1_language,_Examples___7_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/3/artifact/build-artifacts/03:56:36_Tails_is_localized_for_every_tier-1_language,_Examples___7_.journal

After features/support/hooks.rb:100 0.000

Feature: Tails persistence

Tags: @product

26.544

Scenario Booting Tails from a USB drive with a disabled persistent partition

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.029

Steps

Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 17.384

When I log in to a new session without activating the Persistent Storage 9.159

<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

Hooks

After features/support/hooks.rb:330 5.594

Output 1

SCENARIO FAILED: 'Booting Tails from a USB drive with a disabled persistent partition' (at time 04:29:31)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/3/artifact/build-artifacts/04:29:31_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_test-suite-options/3/artifact/build-artifacts/04:29:31_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/3/artifact/build-artifacts/04:29:31_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/3/artifact/build-artifacts/04:29:31_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 @doc

1:56.662

Scenario Manual filesystem repair fails

Hooks

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 48.896

And the Persistent Storage filesystem is corrupted beyond what e2fsck can repair 3.719

When I try to enable persistence 3.886

Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 1:0.160

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

Hooks

After features/support/hooks.rb:330 14.535

Output 1

SCENARIO FAILED: 'Manual filesystem repair fails' (at time 05:23:13)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/3/artifact/build-artifacts/05:23:13_Manual_filesystem_repair_fails.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/3/artifact/build-artifacts/05:23:13_Manual_filesystem_repair_fails.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/3/artifact/build-artifacts/05:23:13_Manual_filesystem_repair_fails.journal

After features/support/hooks.rb:100 0.000

Feature: Using persistent Tor bridges and pluggable transports

2:38.504

Background

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.031

Steps

Given I have started Tails without network from a USB drive without a persistent partition and logged in 1:16.642

And I create a persistent partition with the default settings 53.585

Then the "TorConfiguration" tps feature is not enabled 3.451

When the network is plugged 0.095

And the Tor Connection Assistant autostarts 15.480

And I configure some persistent obfs4 bridges in the Tor Connection Assistant 9.249

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: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/persistent_tor_bridges.feature:13:in `And I configure some persistent obfs4 bridges in the Tor Connection Assistant'

And I wait until Tor is ready 0.000

Then tca.conf includes the configured bridges 0.000

And the "TorConfiguration" tps feature is enabled and active 0.000

When I cold reboot the computer 0.000

And the computer reboots Tails 0.000

And I enable persistence 0.000

And I capture all network traffic 0.000

And I log in to a new session 0.000

Then tca.conf includes the configured bridges 0.000

When the network is plugged 0.000

And the Tor Connection Assistant autostarts 0.000

Feature: Using persistent Tor bridges and pluggable transports

Tags: @product

0.000

Scenario Using Persistent Tor bridges

Steps

When I choose to connect to Tor automatically 0.000

And I accept Tor Connection's offer to use my persistent bridges 0.000

And I click "Connect to Tor" 0.000

Then I wait until Tor is ready 0.000

And tca.conf includes the configured bridges 0.000

And the "TorConfiguration" tps feature is enabled and active 0.000

And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000

Hooks

After features/support/hooks.rb:330 7.661

Output 1

SCENARIO FAILED: 'Using Persistent Tor bridges' (at time 05:30:10)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/3/artifact/build-artifacts/05:30:10_Using_Persistent_Tor_bridges.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/3/artifact/build-artifacts/05:30:10_Using_Persistent_Tor_bridges.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/3/artifact/build-artifacts/05:30:10_Using_Persistent_Tor_bridges.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/3/artifact/build-artifacts/05:30:10_Using_Persistent_Tor_bridges.journal

After features/support/hooks.rb:100 0.000

Feature: Using persistent Tor bridges and pluggable transports

Tags: @product

15.610

Scenario Disabling persistence of Tor bridges

Steps

When I choose to connect to Tor automatically 4.744

And I accept Tor Connection's offer to use my persistent bridges 10.865

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:785:in `/^I accept Tor Connection's offer to use my persistent bridges$/'
features/persistent_tor_bridges.feature:37:in `And I accept Tor Connection's offer to use my persistent bridges'

And I disable saving bridges to Persistent Storage 0.000

And I configure a direct connection in the Tor Connection Assistant 0.000

Then I wait until Tor is ready 0.000

And tca.conf includes no bridge 0.000

And the "TorConfiguration" tps feature is not enabled and not active 0.000

And all Internet traffic has only flowed through Tor or connectivity check service 0.000

Hooks

After features/support/hooks.rb:330 5.157

Output 1

SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 05:37:13)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/3/artifact/build-artifacts/05:37:13_Disabling_persistence_of_Tor_bridges.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/3/artifact/build-artifacts/05:37:13_Disabling_persistence_of_Tor_bridges.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/3/artifact/build-artifacts/05:37:13_Disabling_persistence_of_Tor_bridges.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/3/artifact/build-artifacts/05:37:13_Disabling_persistence_of_Tor_bridges.journal

After features/support/hooks.rb:100 0.084

Feature: Tails has a sane default configuration

Tags: @product

1:22.490

Scenario No unexpected error messages in the journal after booting from USB drive

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.041

Steps

Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:22.490

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

Hooks

After features/support/hooks.rb:330 7.104

Output 1

SCENARIO FAILED: 'No unexpected error messages in the journal after booting from USB drive' (at time 05:48:34)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/3/artifact/build-artifacts/05:48:34_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_test-suite-options/3/artifact/build-artifacts/05:48:34_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/3/artifact/build-artifacts/05:48:34_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/3/artifact/build-artifacts/05:48:34_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.journal

After features/support/hooks.rb:100 0.000