Cucumber Reports (no 14) - Failures Overview

Project	Number	Date
test_Tails_ISO_21548-flatpak-install	14	22 May 2026, 14:43

Feature: System memory erasure on shutdown

3:57.282

Scenario Erasure of read and write disk caches of persistent data on shutdown

Hooks

Before features/support/hooks.rb:270 0.000

Before features/support/hooks.rb:277 0.001

Steps

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

Feature

Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:793:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:788:in `each'
./features/step_definitions/usb.rb:788:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150: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:76: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

Hooks

After features/support/hooks.rb:335 4.890

Output 1

SCENARIO FAILED: 'Erasure of read and write disk caches of persistent data on shutdown' (at time 00:29:06)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/00:29:06_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_21548-flatpak-install/14/artifact/build-artifacts/00:29:06_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/00:29:06_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/00:29:06_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.journal

After features/support/hooks.rb:104 0.013

Feature: Installing Tails to a USB drive

Tags: @product

35.738

Scenario Installing Tails with Tails Installer to a used USB drive, cloning the Persistent Storage

Hooks

Before features/support/hooks.rb:270 0.000

Before features/support/hooks.rb:277 0.003

Steps

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

Feature

Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:793:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:788:in `each'
./features/step_definitions/usb.rb:788:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150: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_install.feature:45:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

And I create a file in the Persistent directory 0.000

And I temporarily create a 7200 MiB disk named "install" 0.000

And I create a gpt partition with a vfat filesystem on disk "install" 0.000

And I plug USB drive "install" 0.000

And I install Tails with Persistent Storage to USB drive "install" by cloning 0.000

Then the running Tails is installed on USB drive "install" 0.000

And there is a random seed on USB drive "install" 0.000

And there is a persistence partition on USB drive "install" 0.000

And the USB drive "install" contains the same files as my persistent storage 0.000

Hooks

After features/support/hooks.rb:335 5.243

Output 1

SCENARIO FAILED: 'Installing Tails with Tails Installer to a used USB drive, cloning the Persistent Storage' (at time 00:34:47)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/00:34:47_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/00:34:47_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/00:34:47_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/00:34:47_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.journal

After features/support/hooks.rb:104 0.000

Feature: Installing Tails to a USB drive

Tags: @product

34.331

Scenario Installing Tails with Tails Installer to a pristine USB drive, without cloning the Persistent Storage

Hooks

Before features/support/hooks.rb:270 0.000

Before features/support/hooks.rb:277 0.004

Steps

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

Feature

Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:793:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:788:in `each'
./features/step_definitions/usb.rb:788:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150: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_install.feature:57:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

And I temporarily create a 7200 MiB disk named "install" 0.000

And I plug USB drive "install" 0.000

And I install Tails to USB drive "install" by cloning 0.000

Then the running Tails is installed on USB drive "install" 0.000

And there is a random seed on USB drive "install" 0.000

And there is no persistence partition on USB drive "install" 0.000

Hooks

After features/support/hooks.rb:335 5.093

Output 1

SCENARIO FAILED: 'Installing Tails with Tails Installer to a pristine USB drive, without cloning the Persistent Storage' (at time 00:35:26)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/00:35:26_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive,_without_cloning_the_Persistent_Storage.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/00:35:26_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive,_without_cloning_the_Persistent_Storage.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/00:35:26_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive,_without_cloning_the_Persistent_Storage.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/00:35:26_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive,_without_cloning_the_Persistent_Storage.journal

After features/support/hooks.rb:104 0.000

Feature: Installing Tails to a USB drive

Tags: @product

36.010

Scenario Re-installing Tails over an existing USB installation with a persistent partition

Hooks

Before features/support/hooks.rb:270 0.000

Before features/support/hooks.rb:277 0.002

Steps

# We reach this first checkpoint only to ensure that the ' __internal' disk has reached the state (Tails installed + persistent partition set up) we need before we clone it below.

# This first part is done without Tails Installer (install from Tails USB image)

# Note: the "__internal" disk will keep its state across scenarios

# and features until one of its snapshots is restored.

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

Feature

Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:793:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:788:in `each'
./features/step_definitions/usb.rb:788:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150: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_install.feature:70:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

And I have started Tails from DVD without network and logged in 0.000

And I clone USB drive "__internal" to a temporary USB drive "install" 0.000

And I plug USB drive "install" 0.000

# This second part is done with Tails Installer, that's what this scenario is about

When I reinstall Tails to USB drive "install" by cloning 0.000

Then the running Tails is installed on USB drive "install" 0.000

And there is a random seed on USB drive "install" 0.000

And there is no persistence partition on USB drive "install" 0.000

Hooks

After features/support/hooks.rb:335 5.046

Output 1

SCENARIO FAILED: 'Re-installing Tails over an existing USB installation with a persistent partition' (at time 00:36:07)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/00:36:07_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/00:36:07_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/00:36:07_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/00:36:07_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.journal

After features/support/hooks.rb:104 0.000

Feature: Upgrading an old Tails USB installation

Tags: @product @automatic_upgrade

37.448

Scenario Upgrading an initial Tails installation with an incremental upgrade

Hooks

Before features/support/hooks.rb:270 0.000

Before features/support/hooks.rb:277 0.002

Steps

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

Feature

Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:793:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:788:in `each'
./features/step_definitions/usb.rb:788:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150: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:82:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

And no SquashFS delta is installed 0.000

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 file system changes introduced in version 6.2~testoverlayfs are not present 0.000

And the file system changes introduced in version 6.3~testoverlayfs are not present 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

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

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.2~testoverlayfs 0.000

And all tps features are active 0.000

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

And only the 6.2~testoverlayfs SquashFS delta is installed 0.000

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

Given Tails system time is magically synchronized 0.000

# 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.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.3~testoverlayfs 0.000

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

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:335 4.932

Output 1

SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:01:57)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:01:57_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_21548-flatpak-install/14/artifact/build-artifacts/01:01:57_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:01:57_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:01:57_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal

After features/support/hooks.rb:104 0.000

Feature: Upgrading an old Tails USB installation

Tags: @product @automatic_upgrade

34.271

Scenario Upgrading a Tails whose signing key is outdated

Hooks

Before features/support/hooks.rb:270 0.000

Before features/support/hooks.rb:277 0.004

Steps

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

Feature

Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:793:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:788:in `each'
./features/step_definitions/usb.rb:788:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150: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

Hooks

After features/support/hooks.rb:335 5.153

Output 1

SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 01:02:37)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:02:37_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:02:37_Upgrading_a_Tails_whose_signing_key_is_outdated.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:02:37_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:02:37_Upgrading_a_Tails_whose_signing_key_is_outdated.journal

After features/support/hooks.rb:104 0.000

Feature: Emergency shutdown

Tags: @product @not_release_blocker

34.807

Scenario Tails erases memory and shuts down on USB boot medium removal: persistent data

Hooks

Before features/support/hooks.rb:270 0.000

Before features/support/hooks.rb:277 0.003

Steps

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

Feature

Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:793:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:788:in `each'
./features/step_definitions/usb.rb:788:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150: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/emergency_shutdown.feature:48: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

And I fill a 128 MiB file with a known pattern on the persistent filesystem 0.000

And patterns cover at least 100 MiB in the guest's memory 0.000

When I eject the boot medium 0.000

And I wait for Tails to finish wiping the memory 0.000

Then I find very few patterns in the guest's memory 0.000

And Tails eventually shuts down 0.000

Hooks

After features/support/hooks.rb:335 5.070

Output 1

SCENARIO FAILED: 'Tails erases memory and shuts down on USB boot medium removal: persistent data' (at time 01:06:03)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:06:03_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:06:03_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:06:03_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:06:03_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.journal

After features/support/hooks.rb:104 0.000

Feature: Backing up the persistent storage

Tags: @product

34.087

Scenario Using Tails' custom backup tool to backup a newly added file

Hooks

Before features/support/hooks.rb:270 0.000

Before features/support/hooks.rb:277 0.001

Steps

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

Feature

Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:793:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:788:in `each'
./features/step_definitions/usb.rb:788:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150: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/backup.feature:8:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

# The volume cannot be in use when GuestFs clones it, which we do below

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

And I clone USB drive "__internal" to a temporary USB drive "backup" 0.000

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

And I write a file "/live/persistence/TailsData_unlocked/new" with contents "foo" 0.000

When I start Tails' custom backup tool 0.000

Then the backup tool displays "Plug in your backup Tails USB stick" 0.000

When I plug USB drive "backup" 0.000

And I give the Persistent Storage on drive "backup" its own UUID 0.000

And I click "Retry" in the backup tool 0.000

Then the backup tool displays "Do you want to back up your Persistent Storage now?" 0.000

When I click "Back Up" in the backup tool 0.000

And I enter my persistent storage passphrase into the polkit prompt 0.000

Then the backup tool displays "Your Persistent Storage was backed up successfully to your backup Tails USB stick!" 0.000

# The backup tool ejects the drive, so we have to replug it

When I unplug USB drive "backup" 0.000

And I plug USB drive "backup" 0.000

Then the USB drive "backup" contains the same files as my persistent storage 0.000

Hooks

After features/support/hooks.rb:335 4.748

Output 1

SCENARIO FAILED: 'Using Tails' custom backup tool to backup a newly added file' (at time 01:07:20)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:07:20_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:07:20_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:07:20_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:07:20_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal

After features/support/hooks.rb:104 0.000

Feature: Using Evince

Tags: @product

33.563

Scenario I can view and print a PDF file stored in persistent /home/amnesia/Persistent

Hooks

Before features/support/hooks.rb:270 0.000

Before features/support/hooks.rb:277 0.005

Steps

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

Feature

Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:793:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:788:in `each'
./features/step_definitions/usb.rb:788:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150: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:20: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/Persistent" as user "amnesia" 0.000

Then the file "/home/amnesia/Persistent/default-testpage.pdf" exists 0.000

When I open "/home/amnesia/Persistent/default-testpage.pdf" with Evince 0.000

Then I see "CupsTestPage.png" after at most 40 seconds 0.000

And I can print the current document to "/home/amnesia/Persistent/output.pdf" 0.000

Hooks

After features/support/hooks.rb:335 4.831

Output 1

SCENARIO FAILED: 'I can view and print a PDF file stored in persistent /home/amnesia/Persistent' (at time 01:11:10)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:11:10_I_can_view_and_print_a_PDF_file_stored_in_persistent__home_amnesia_Persistent.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:11:10_I_can_view_and_print_a_PDF_file_stored_in_persistent__home_amnesia_Persistent.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:11:10_I_can_view_and_print_a_PDF_file_stored_in_persistent__home_amnesia_Persistent.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:11:10_I_can_view_and_print_a_PDF_file_stored_in_persistent__home_amnesia_Persistent.journal

After features/support/hooks.rb:104 0.000

Feature: GNOME is well-integrated into Tails

Tags: @product

33.797

Scenario I can launch various apps via GNOME Activities Overview

Hooks

Before features/support/hooks.rb:270 0.000

Before features/support/hooks.rb:277 0.004

Steps

# Some apps (Electrum and Persistent Storage Backup) only start when

# a Persistent Storage is available.

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

Feature

Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:793:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:788:in `each'
./features/step_definitions/usb.rb:788:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150: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/gnome.feature:22:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

# Some apps (Tor Browser) only start when the network is plugged.

And the network is plugged 0.000

And Tor is ready 0.000

And all notifications have disappeared 0.000

When I start "Additional Software" via GNOME Activities Overview 0.000

And I close the "tails-additional-software-config" window 0.000

When I start "Disks" via GNOME Activities Overview 0.000

# The close button of GNOME Disks is not accessible

And I close the "gnome-disks" window via Alt+F4 0.000

When I start "Console" via GNOME Activities Overview 0.000

And I close Console 0.000

When I start "Files" via GNOME Activities Overview 0.000

And I close the "org.gnome.Nautilus" window 0.000

When I start "Persistent Storage" via GNOME Activities Overview 0.000

And I close the "tps-frontend" window 0.000

When I start "Back Up Persistent Storage" via GNOME Activities Overview 0.000

And I close the "zenity" window 0.000

When I start "Pidgin" via GNOME Activities Overview 0.000

And I close the "Pidgin" window via Alt+F4 0.000

When I start "Thunderbird" via GNOME Activities Overview 0.000

And I click "Learn More" in the "Install Thunderbird" zenity dialog 0.000

And I close the "Firefox" window 0.000

When I start "Tor Browser" via GNOME Activities Overview 0.000

And I close the "Firefox" window 0.000

When I start "Unlock VeraCrypt Volumes" via GNOME Activities Overview 0.000

And I close the "unlock-veracrypt-volumes" window 0.000

When I start "Unsafe Browser" via GNOME Activities Overview 0.000

And I close the "Firefox" window 0.000

When I start "Secrets" via GNOME Activities Overview 0.000

And I close the "secrets" window 0.000

Hooks

After features/support/hooks.rb:335 5.109

Output 1

SCENARIO FAILED: 'I can launch various apps via GNOME Activities Overview' (at time 01:12:16)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:12:16_I_can_launch_various_apps_via_GNOME_Activities_Overview.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:12:16_I_can_launch_various_apps_via_GNOME_Activities_Overview.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:12:16_I_can_launch_various_apps_via_GNOME_Activities_Overview.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:12:16_I_can_launch_various_apps_via_GNOME_Activities_Overview.journal

After features/support/hooks.rb:104 0.000

Feature: Hardware failures

Tags: @product @doc

34.900

Scenario Outline Alerting about disk read failures in GNOME

Hooks

Before features/support/hooks.rb:270 0.000

Before features/support/hooks.rb:277 0.013

Steps

Given a computer 0.089

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

Feature

Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:793:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:788:in `each'
./features/step_definitions/usb.rb:788:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150: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

Hooks

After features/support/hooks.rb:335 5.171

Output 1

SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 01:14:26)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:14:26_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_21548-flatpak-install/14/artifact/build-artifacts/01:14:26_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:14:26_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:14:26_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal

After features/support/hooks.rb:104 0.000

Feature: Hardware failures

Tags: @product @doc

35.591

Scenario Outline Alerting about disk read failures in GNOME

Hooks

Before features/support/hooks.rb:270 0.000

Before features/support/hooks.rb:277 0.011

Steps

Given a computer 0.249

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

Feature

Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:793:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:788:in `each'
./features/step_definitions/usb.rb:788:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150: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:30: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 boot device 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

Hooks

After features/support/hooks.rb:335 4.842

Output 1

SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 01:15:06)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:15:06_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:15:06_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:15:06_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:15:06_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal

After features/support/hooks.rb:104 0.000

Feature: Hardware failures

Tags: @product @doc

33.894

Scenario Outline Alerting about disk read failures in GNOME

Hooks

Before features/support/hooks.rb:270 0.000

Before features/support/hooks.rb:277 0.004

Steps

Given a computer 0.073

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

Feature

Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:793:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:788:in `each'
./features/step_definitions/usb.rb:788:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150: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:31: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 boot device with a target error 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

Hooks

After features/support/hooks.rb:335 4.918

Output 1

SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 01:15:45)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:15:45_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_21548-flatpak-install/14/artifact/build-artifacts/01:15:45_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:15:45_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:15:45_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal

After features/support/hooks.rb:104 0.000

Feature: Localization

Tags: @product

26.190

Scenario Outline Do not localize the XDG User Dirs to be able to use those dirs in Tor Browser (#19255)

Hooks

Before features/support/hooks.rb:270 0.000

Before features/support/hooks.rb:277 0.003

Steps

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

And I log in to a new session in German (de) 18.094

The

The Dogtail init script raised: Error: atspi_error: timeout from dbind (1)
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:360:in `click'
./features/step_definitions/common_steps.rb:526: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:15:in `And I log in to a new session in German (de)'
features/localization.feature:9:in `And I log in to a new session in German (de)'

Then the live user's Downloads directory exists 0.000

And there is a GNOME bookmark for the Downloads directory 0.000

Hooks

After features/support/hooks.rb:335 5.182

Output 1

SCENARIO FAILED: 'Do not localize the XDG User Dirs to be able to use those dirs in Tor Browser (#19255), Examples (#2)' (at time 01:25:35)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:25:35_Do_not_localize_the_XDG_User_Dirs_to_be_able_to_use_those_dirs_in_Tor_Browser___19255_,_Examples___2_.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:25:35_Do_not_localize_the_XDG_User_Dirs_to_be_able_to_use_those_dirs_in_Tor_Browser___19255_,_Examples___2_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:25:35_Do_not_localize_the_XDG_User_Dirs_to_be_able_to_use_those_dirs_in_Tor_Browser___19255_,_Examples___2_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/01:25:35_Do_not_localize_the_XDG_User_Dirs_to_be_able_to_use_those_dirs_in_Tor_Browser___19255_,_Examples___2_.journal

After features/support/hooks.rb:104 0.000

Feature: Tails persistence

Tags: @product

36.366

Scenario Booting Tails from a USB drive with an enabled persistent partition and reconfiguring it

Hooks

Before features/support/hooks.rb:270 0.000

Before features/support/hooks.rb:277 0.003

Steps

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

Feature

Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:793:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:788:in `each'
./features/step_definitions/usb.rb:788:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150: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:42:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

Then Tails is running from USB drive "__internal" 0.000

And all tps features are active 0.000

And all persistent directories have safe access rights 0.000

When I disable the first tps feature 0.000

Then all tps features but the first one are active 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 all tps features but the first one are active 0.000

Hooks

After features/support/hooks.rb:335 4.992

Output 1

SCENARIO FAILED: 'Booting Tails from a USB drive with an enabled persistent partition and reconfiguring it' (at time 02:11:37)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:11:37_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:11:37_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:11:37_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:11:37_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.journal

After features/support/hooks.rb:104 0.000

Feature: Tails persistence

Tags: @product

34.025

Scenario Activating and deactivating Persistent Storage features

Hooks

Before features/support/hooks.rb:270 0.000

Before features/support/hooks.rb:277 0.003

Steps

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

Feature

Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:793:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:788:in `each'
./features/step_definitions/usb.rb:788:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150: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:53:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

Then persistence for "Persistent" is active 0.000

And I create a file in the Persistent directory 0.000

Then the file I created was copied to the Persistent Storage 0.000

When I disable the first tps feature 0.000

Then persistence for "Persistent" is not active 0.000

And the Persistent directory does not exist 0.000

When I enable the first tps feature 0.000

Then persistence for "Persistent" is active 0.000

And the file I created in the Persistent directory exists 0.000

Hooks

After features/support/hooks.rb:335 4.890

Output 1

SCENARIO FAILED: 'Activating and deactivating Persistent Storage features' (at time 02:12:16)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:12:16_Activating_and_deactivating_Persistent_Storage_features.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:12:16_Activating_and_deactivating_Persistent_Storage_features.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:12:16_Activating_and_deactivating_Persistent_Storage_features.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:12:16_Activating_and_deactivating_Persistent_Storage_features.journal

After features/support/hooks.rb:104 0.000

Feature: Tails persistence

Tags: @product

32.044

Scenario Deleting data of a Persistent Storage feature

Hooks

Before features/support/hooks.rb:270 0.000

Before features/support/hooks.rb:277 0.003

Steps

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

Feature

Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:793:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:788:in `each'
./features/step_definitions/usb.rb:788:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150: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:65:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

Then persistence for "Persistent" is active 0.000

When I create a file in the Persistent directory 0.000

And I disable the first tps feature 0.000

And I delete the data of the Persistent Folder feature 0.000

Then the file I created does not exist on the Persistent Storage 0.000

Hooks

After features/support/hooks.rb:335 4.853

Output 1

SCENARIO FAILED: 'Deleting data of a Persistent Storage feature' (at time 02:12:53)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:12:53_Deleting_data_of_a_Persistent_Storage_feature.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:12:53_Deleting_data_of_a_Persistent_Storage_feature.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:12:53_Deleting_data_of_a_Persistent_Storage_feature.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:12:53_Deleting_data_of_a_Persistent_Storage_feature.journal

After features/support/hooks.rb:104 0.000

Feature: Tails persistence

Tags: @product

31.740

Scenario Writing files to a read/write-enabled persistent partition

Hooks

Before features/support/hooks.rb:270 0.000

Before features/support/hooks.rb:277 0.026

Steps

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

Feature

Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:793:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:788:in `each'
./features/step_definitions/usb.rb:788:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150: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:73:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

And the network is plugged 0.000

And Tor is ready 0.000

And I take note of which tps features are available 0.000

When I write some files expected to persist 0.000

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

# XXX: The next step succeeds (and the --debug output confirms that it's actually looking for the files) but will fail in a subsequent scenario restoring the same snapshot. This exactly what we want, but why does it work? What is guestfs's behaviour when qcow2 internal snapshots are involved? (tails/tails#10330)

Then only the expected files are present on the persistence partition on USB drive "__internal" 0.000

Hooks

After features/support/hooks.rb:335 5.160

Output 1

SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition' (at time 02:13:30)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:13:30_Writing_files_to_a_read_write-enabled_persistent_partition.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:13:30_Writing_files_to_a_read_write-enabled_persistent_partition.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:13:30_Writing_files_to_a_read_write-enabled_persistent_partition.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:13:30_Writing_files_to_a_read_write-enabled_persistent_partition.journal

After features/support/hooks.rb:104 0.000

Feature: Tails persistence

Tags: @product

33.526

Scenario Creating and using a persistent NetworkManager connection

Hooks

Before features/support/hooks.rb:270 0.000

Before features/support/hooks.rb:277 0.005

Steps

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

Feature

Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:793:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:788:in `each'
./features/step_definitions/usb.rb:788:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150: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:83:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

And the network is plugged 0.000

And Tor is ready 0.000

And I add a wired DHCP NetworkManager connection called "persistent-con-current" 0.000

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

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

And I capture all network traffic 0.000

And the network is plugged 0.000

And Tor is ready 0.000

And I switch to the "persistent-con-current" NetworkManager connection 0.000

And the 1st network device has a spoofed MAC address configured 0.000

And no network device leaked the real MAC address 0.000

Hooks

After features/support/hooks.rb:335 4.869

Output 1

SCENARIO FAILED: 'Creating and using a persistent NetworkManager connection' (at time 02:14:08)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:14:08_Creating_and_using_a_persistent_NetworkManager_connection.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:14:08_Creating_and_using_a_persistent_NetworkManager_connection.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:14:08_Creating_and_using_a_persistent_NetworkManager_connection.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:14:08_Creating_and_using_a_persistent_NetworkManager_connection.journal

After features/support/hooks.rb:104 0.000

Feature: Tails persistence

Tags: @product

31.661

Scenario Changing the Persistent Storage passphrase

Hooks

Before features/support/hooks.rb:270 0.000

Before features/support/hooks.rb:277 0.002

Steps

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

Feature

Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:793:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:788:in `each'
./features/step_definitions/usb.rb:788:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150: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:124:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

# 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 0.000

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

Hooks

After features/support/hooks.rb:335 4.736

Output 1

SCENARIO FAILED: 'Changing the Persistent Storage passphrase' (at time 02:18:19)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:18:19_Changing_the_Persistent_Storage_passphrase.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:18:19_Changing_the_Persistent_Storage_passphrase.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:18:19_Changing_the_Persistent_Storage_passphrase.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:18:19_Changing_the_Persistent_Storage_passphrase.journal

After features/support/hooks.rb:104 0.000

Feature: Tails persistence

Tags: @product

32.891

Scenario Dotfiles persistence

Hooks

Before features/support/hooks.rb:270 0.000

Before features/support/hooks.rb:277 0.003

Steps

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

Feature

Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:793:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:788:in `each'
./features/step_definitions/usb.rb:788:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150: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:143: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

Hooks

After features/support/hooks.rb:335 5.000

Output 1

SCENARIO FAILED: 'Dotfiles persistence' (at time 02:19:36)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:19:36_Dotfiles_persistence.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:19:36_Dotfiles_persistence.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:19:36_Dotfiles_persistence.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:19:36_Dotfiles_persistence.journal

After features/support/hooks.rb:104 0.000

Feature: Tails persistence

Tags: @product

40.346

Scenario Feature activation fails

Hooks

Before features/support/hooks.rb:270 0.000

Before features/support/hooks.rb:277 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 7.684

And I create a symlink "/home/amnesia/Persistent" to "/etc" 0.062

When I try to enable persistence 1.252

Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated 10.710

When I log in to a new session after having activated the Persistent Storage 10.401

And all notifications have disappeared 7.979

Then the Persistent Storage settings tell me that the Persistent Folder feature couldn't be activated 1.307

And all tps features are enabled 0.948

Feature

Feature 'Flatpak' is not enabled.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:806:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:801:in `each'
./features/step_definitions/usb.rb:801:in `/^all tps features(| but the first one) are enabled$/'
features/persistence.feature:157:in `And all tps features are enabled'

And all tps features but the first one are active 0.000

Hooks

After features/support/hooks.rb:335 5.223

Output 1

SCENARIO FAILED: 'Feature activation fails' (at time 02:20:22)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:20:22_Feature_activation_fails.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:20:22_Feature_activation_fails.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:20:22_Feature_activation_fails.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:20:22_Feature_activation_fails.journal

After features/support/hooks.rb:104 0.000

Feature: Tails has a sane default configuration

Tags: @product

36.668

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

Hooks

Before features/support/hooks.rb:270 0.000

Before features/support/hooks.rb:277 0.003

Steps

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

Feature

Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:793:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:788:in `each'
./features/step_definitions/usb.rb:788:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150: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:25: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:335 4.843

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:31:48_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_21548-flatpak-install/14/artifact/build-artifacts/02:31:48_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:31:48_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:31:48_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.journal

After features/support/hooks.rb:104 0.000

Feature: The Tor enforcement is effective

Tags: @product

11.082

Scenario The firewall configuration is very restrictive

Hooks

Before features/support/hooks.rb:270 0.000

Before features/support/hooks.rb:277 0.007

Steps

Given I have started Tails from DVD and logged in and the network is connected 10.843

Then the firewall's policy is to drop all IPv4 traffic 0.046

And the firewall is configured to only allow the clearnet and debian-tor users to connect directly to the Internet over IPv4 0.192

The

The following rule has an unexpected destination:
<rule byte-count='0' packet-count='0'>
       <conditions>
        <match>
          <d>127.0.0.1/32</d>
          <o invert='1'>lo</o>
          <p>tcp</p>
        </match>
        <tcp>
          <dport>9040</dport>
        </tcp>
        <owner>
          <uid-owner>1000</uid-owner>
        </owner>
       </conditions>
       <actions>
        <ACCEPT/>
       </actions>

      </rule>.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/tor.rb:100:in `block (3 levels) in <top (required)>'
./features/step_definitions/tor.rb:96:in `block (2 levels) in <top (required)>'
./features/step_definitions/tor.rb:95:in `each'
./features/step_definitions/tor.rb:95:in `/^the firewall is configured to only allow the (.+) users? to connect directly to the Internet over IPv4$/'
features/tor_enforcement.feature:11:in `And the firewall is configured to only allow the clearnet and debian-tor users to connect directly to the Internet over IPv4'

And the firewall's NAT rules only redirect traffic for the Unsafe Browser, Tor's TransPort, and DNSPort 0.000

And the firewall is configured to block all external IPv6 traffic 0.000

Hooks

After features/support/hooks.rb:335 4.757

Output 1

SCENARIO FAILED: 'The firewall configuration is very restrictive' (at time 02:41:32)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:41:32_The_firewall_configuration_is_very_restrictive.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:41:32_The_firewall_configuration_is_very_restrictive.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:41:32_The_firewall_configuration_is_very_restrictive.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:41:32_The_firewall_configuration_is_very_restrictive.journal

After features/support/hooks.rb:104 0.000

Feature: The Tor enforcement is effective

Tags: @product @check_tor_leaks

10.245

Scenario The Tor enforcement is effective at blocking untorified TCP connection attempts

Hooks

Before features/support/hooks.rb:270 0.000

Before features/support/hooks.rb:277 0.006

Before features/support/hooks.rb:523 0.004

Steps

Given I have started Tails from DVD and logged in and the network is connected 9.933

When I open an untorified TCP connection to 1.2.3.4 on port 42 0.311

Then the untorified connection fails 0.001

The

The untorified TCP connection didn't fail as expected:
Return status: 0
STDOUT:
STDERR:
1.2.3.4: inverse host lookup failed: Unknown host
(UNKNOWN) [1.2.3.4] 42 (?) open
.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/tor.rb:255:in `/^the untorified connection fails$/'
features/tor_enforcement.feature:49:in `Then the untorified connection fails'

And the untorified connection is logged as dropped by the firewall 0.000

Hooks

After features/support/hooks.rb:531 0.045

After features/support/hooks.rb:335 4.982

Output 1

SCENARIO FAILED: 'The Tor enforcement is effective at blocking untorified TCP connection attempts' (at time 02:42:51)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:42:51_The_Tor_enforcement_is_effective_at_blocking_untorified_TCP_connection_attempts.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:42:51_The_Tor_enforcement_is_effective_at_blocking_untorified_TCP_connection_attempts.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:42:51_The_Tor_enforcement_is_effective_at_blocking_untorified_TCP_connection_attempts.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:42:51_The_Tor_enforcement_is_effective_at_blocking_untorified_TCP_connection_attempts.journal

After features/support/hooks.rb:104 0.000

Feature: Browsing the web using the Tor Browser

Tags: @product

35.850

Scenario The Persistent directory is usable in Tor Browser

Hooks

Before features/support/hooks.rb:270 0.000

Before features/support/hooks.rb:277 0.008

Steps

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

Feature

Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:793:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:788:in `each'
./features/step_definitions/usb.rb:788:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150: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/torified_browsing.feature:102:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

And the network is plugged 0.000

And I successfully configure Tor 0.000

And available upgrades have been checked 0.000

And all notifications have disappeared 0.000

And there is a GNOME bookmark for the Persistent directory 0.000

When I start the Tor Browser 0.000

And I download some file in the Tor Browser to the Persistent directory 0.000

Then the file is saved to the Persistent directory 0.000

When I open the address "https://tails.net/about" in the Tor Browser 0.000

Then "Tails - How Tails works" has loaded in the Tor Browser 0.000

And I can print the current page as "output.pdf" to the Persistent directory 0.000

Hooks

After features/support/hooks.rb:335 4.975

Output 1

SCENARIO FAILED: 'The Persistent directory is usable in Tor Browser' (at time 02:52:00)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:52:00_The_Persistent_directory_is_usable_in_Tor_Browser.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:52:00_The_Persistent_directory_is_usable_in_Tor_Browser.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:52:00_The_Persistent_directory_is_usable_in_Tor_Browser.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:52:00_The_Persistent_directory_is_usable_in_Tor_Browser.journal

After features/support/hooks.rb:104 0.000

Feature: Browsing the web using the Tor Browser

Tags: @product

33.799

Scenario Persistent browser bookmarks

Hooks

Before features/support/hooks.rb:270 0.000

Before features/support/hooks.rb:277 0.008

Steps

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

Feature

Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:793:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:788:in `each'
./features/step_definitions/usb.rb:788:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150: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/torified_browsing.feature:130:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

And all tps features are active 0.000

And all persistent filesystems have safe access rights 0.000

And all persistence configuration files have safe access rights 0.000

And all persistent directories have safe access rights 0.000

When I start the Tor Browser in offline mode 0.000

And I add a bookmark to eff.org in the Tor Browser 0.000

And I cold reboot the computer 0.000

And the computer reboots Tails 0.000

And I enable persistence 0.000

And I log in to a new session 0.000

And all notifications have disappeared 0.000

And I start the Tor Browser in offline mode 0.000

Then the Tor Browser has a bookmark to eff.org 0.000

Hooks

After features/support/hooks.rb:335 5.067

Output 1

SCENARIO FAILED: 'Persistent browser bookmarks' (at time 02:56:10)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:56:10_Persistent_browser_bookmarks.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:56:10_Persistent_browser_bookmarks.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:56:10_Persistent_browser_bookmarks.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:56:10_Persistent_browser_bookmarks.journal

After features/support/hooks.rb:104 0.000

Feature: Using Totem

Tags: @product

34.530

Scenario Watching MP4 videos stored in the Persistent Storage

Steps

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

Feature

Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:793:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:788:in `each'
./features/step_definitions/usb.rb:788:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150: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/totem.feature:24:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

And I plug and mount a USB drive containing sample videos 0.000

And I copy the sample videos to "/home/amnesia/Persistent" as user "amnesia" 0.000

When I open "/home/amnesia/Persistent/video.mp4" with Totem 0.000

Then I see "SampleLocalMp4VideoFrame.png" after at most 40 seconds 0.000

Hooks

After features/support/hooks.rb:335 4.767

Output 1

SCENARIO FAILED: 'Watching MP4 videos stored in the Persistent Storage' (at time 02:58:34)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:58:34_Watching_MP4_videos_stored_in_the_Persistent_Storage.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:58:34_Watching_MP4_videos_stored_in_the_Persistent_Storage.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:58:34_Watching_MP4_videos_stored_in_the_Persistent_Storage.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/14/artifact/build-artifacts/02:58:34_Watching_MP4_videos_stored_in_the_Persistent_Storage.journal

After features/support/hooks.rb:104 0.000