Project Number Date
test_Tails_ISO_devel 3812 15 May 2025, 09:49

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
5:30.361
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 11.545
And I wait until Tor is ready 3.545
When I disconnect the network through GNOME 3.263
And I connect the network through GNOME 2.800
Then the Tor Connection Assistant autostarts 2.487
And the Tor Connection Assistant connects to Tor 6.352
And I wait until Tor is ready 5:0.367
Time 
Time syncing failed (HtpdateError)
./features/step_definitions/common_steps.rb:711:in `rescue in block in <top (required)>'
./features/step_definitions/common_steps.rb:709:in `/^the time has synced$/'
./features/step_definitions/common_steps.rb:662:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:89:in `And I wait until Tor is ready'
And Tor is using the same configuration as before 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:330 5.608 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:32:39)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/00:32:39_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/00:32:39_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.file_content_var_log_boot.log
Htpdate logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/00:32:39_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.htpdate
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/00:32:39_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/00:32:39_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/00:32:39_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/00:32:39_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.041
Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
7:50.908
Scenario Erasure of read and write disk caches of persistent data on shutdown
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7:50.908
Feature 
Feature 'GnuPG' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:760:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:755:in `each'
./features/step_definitions/usb.rb:755: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:75:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I prepare Tails for memory erasure tests 0.000
When I fill a 128 MiB file with a known pattern on the persistent filesystem 0.000
When I trigger shutdown 0.000
Then I find very few patterns in the guest's memory after 20 seconds 0.000
After features/support/hooks.rb:330 6.183 
SCENARIO FAILED: 'Erasure of read and write disk caches of persistent data on shutdown' (at time 00:46:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/00:46:42_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_devel/3812/artifact/build-artifacts/00:46:42_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/00:46:42_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/00:46:42_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.journal
After features/support/hooks.rb:100 0.010
Feature: Installing Tails to a USB drive
Tags: @product
1:24.813
Scenario Installing Tails with Tails Installer to a used USB drive, cloning the Persistent Storage
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:24.813
Feature 
Feature 'GnuPG' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:760:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:755:in `each'
./features/step_definitions/usb.rb:755: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
After features/support/hooks.rb:330 6.510 
SCENARIO FAILED: 'Installing Tails with Tails Installer to a used USB drive, cloning the Persistent Storage' (at time 00:54:19)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/00:54:19_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_devel/3812/artifact/build-artifacts/00:54:19_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_devel/3812/artifact/build-artifacts/00:54:19_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_devel/3812/artifact/build-artifacts/00:54:19_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.journal
After features/support/hooks.rb:100 0.000
Feature: Installing Tails to a USB drive
Tags: @product
1:22.132
Scenario Installing Tails with Tails Installer to a pristine USB drive, without cloning the Persistent Storage
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 1:22.132
Feature 
Feature 'GnuPG' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:760:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:755:in `each'
./features/step_definitions/usb.rb:755: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
After features/support/hooks.rb:330 5.844 
SCENARIO FAILED: 'Installing Tails with Tails Installer to a pristine USB drive, without cloning the Persistent Storage' (at time 00:55:47)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/00:55:47_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_devel/3812/artifact/build-artifacts/00:55:47_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_devel/3812/artifact/build-artifacts/00:55:47_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_devel/3812/artifact/build-artifacts/00:55:47_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive,_without_cloning_the_Persistent_Storage.journal
After features/support/hooks.rb:100 0.000
Feature: Installing Tails to a USB drive
Tags: @product
1:18.565
Scenario Re-installing Tails over an existing USB installation with a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 1:18.565
Feature 
Feature 'GnuPG' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:760:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:755:in `each'
./features/step_definitions/usb.rb:755: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
After features/support/hooks.rb:330 5.884 
SCENARIO FAILED: 'Re-installing Tails over an existing USB installation with a persistent partition' (at time 00:57:12)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/00:57:12_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_devel/3812/artifact/build-artifacts/00:57:12_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/00:57:12_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/00:57:12_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.journal
After features/support/hooks.rb:100 0.000
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
1:44.158
Scenario Upgrading an initial Tails installation with an incremental upgrade
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 1:44.158
Feature 
Feature 'GnuPG' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:760:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:755:in `each'
./features/step_definitions/usb.rb:755: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
After features/support/hooks.rb:330 6.377 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:46:49)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/01:46:49_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_devel/3812/artifact/build-artifacts/01:46:49_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/01:46:49_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/01:46:49_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
1:23.999
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:23.999
Feature 
Feature 'GnuPG' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:760:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:755:in `each'
./features/step_definitions/usb.rb:755: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
After features/support/hooks.rb:330 6.335 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 01:48:20)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/01:48:20_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/01:48:20_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/01:48:20_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/01:48:20_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000
Feature: Emergency shutdown
Tags: @product @not_release_blocker
1:36.750
Scenario Tails erases memory and shuts down on USB boot medium removal: persistent data
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 1:36.750
Feature 
Feature 'GnuPG' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:760:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:755:in `each'
./features/step_definitions/usb.rb:755: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
After features/support/hooks.rb:330 6.162 
SCENARIO FAILED: 'Tails erases memory and shuts down on USB boot medium removal: persistent data' (at time 01:53:38)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/01:53:38_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_devel/3812/artifact/build-artifacts/01:53:38_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/01:53:38_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_devel/3812/artifact/build-artifacts/01:53:38_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.journal
After features/support/hooks.rb:100 0.000
Feature: Backing up the persistent storage
Tags: @product
1:21.960
Scenario Using Tails' custom backup tool to backup a newly added file
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 1:21.960
Feature 
Feature 'GnuPG' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:760:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:755:in `each'
./features/step_definitions/usb.rb:755: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
After features/support/hooks.rb:330 5.786 
SCENARIO FAILED: 'Using Tails' custom backup tool to backup a newly added file' (at time 01:56:06)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/01:56:06_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_devel/3812/artifact/build-artifacts/01:56:06_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/01:56:06_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/01:56:06_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal
After features/support/hooks.rb:100 0.000
Feature: Using Evince
Tags: @product
1:21.553
Scenario I can view and print a PDF file stored in persistent /home/amnesia/Persistent
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:21.553
Feature 
Feature 'GnuPG' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:760:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:755:in `each'
./features/step_definitions/usb.rb:755: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:45: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
After features/support/hooks.rb:330 5.869 
SCENARIO FAILED: 'I can view and print a PDF file stored in persistent /home/amnesia/Persistent' (at time 02:02:02)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/02:02:02_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_devel/3812/artifact/build-artifacts/02:02:02_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_devel/3812/artifact/build-artifacts/02:02:02_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_devel/3812/artifact/build-artifacts/02:02:02_I_can_view_and_print_a_PDF_file_stored_in_persistent__home_amnesia_Persistent.journal
After features/support/hooks.rb:100 0.000
Feature: Using Evince
Tags: @product @not_release_blocker
1:32.445
Scenario I cannot view a PDF file stored in persistent /home/amnesia/.gnupg
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:32.445
Feature 
Feature 'GnuPG' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:760:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:755:in `each'
./features/step_definitions/usb.rb:755: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:54:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I copy "/usr/share/cups/data/default-testpage.pdf" to "/home/amnesia/.gnupg" as user "amnesia" 0.000
Then the file "/home/amnesia/.gnupg/default-testpage.pdf" exists 0.000
Given I start monitoring the AppArmor log of "/usr/bin/evince" 0.000
And I try to open "/home/amnesia/.gnupg/default-testpage.pdf" with Evince 0.000
Then Evince tells me it cannot open "/home/amnesia/.gnupg/default-testpage.pdf" 0.000
And AppArmor has denied "/usr/bin/evince" from opening "/home/amnesia/.gnupg/default-testpage.pdf" 0.000
After features/support/hooks.rb:330 6.320 
SCENARIO FAILED: 'I cannot view a PDF file stored in persistent /home/amnesia/.gnupg' (at time 02:03:40)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/02:03:40_I_cannot_view_a_PDF_file_stored_in_persistent__home_amnesia_.gnupg.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/02:03:40_I_cannot_view_a_PDF_file_stored_in_persistent__home_amnesia_.gnupg.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/02:03:40_I_cannot_view_a_PDF_file_stored_in_persistent__home_amnesia_.gnupg.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/02:03:40_I_cannot_view_a_PDF_file_stored_in_persistent__home_amnesia_.gnupg.journal
After features/support/hooks.rb:100 0.000
Feature: GNOME is well-integrated into Tails
Tags: @product
3:55.383
Scenario I can launch various apps via GNOME Activities Overview
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
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 3:55.383
cannot 
cannot find GnomeApplicationsMenu.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/common_steps.rb: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/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 "GNOME Terminal" via GNOME Activities Overview 0.000
And I close the "gnome-terminal-server" window 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 "Persistent Storage Backup" 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 close the "Thunderbird" 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
After features/support/hooks.rb:330 5.870 
SCENARIO FAILED: 'I can launch various apps via GNOME Activities Overview' (at time 02:08:13)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/02:08:13_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_devel/3812/artifact/build-artifacts/02:08:13_I_can_launch_various_apps_via_GNOME_Activities_Overview.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/02:08:13_I_can_launch_various_apps_via_GNOME_Activities_Overview.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/02:08:13_I_can_launch_various_apps_via_GNOME_Activities_Overview.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
1:24.821
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given a computer 0.197
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:24.623
Feature 
Feature 'GnuPG' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:760:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:755:in `each'
./features/step_definitions/usb.rb:755: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
After features/support/hooks.rb:330 6.060 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 02:11:47)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/02:11:47_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_devel/3812/artifact/build-artifacts/02:11:47_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/02:11:47_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/02:11:47_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
1:15.273
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given a computer 0.219
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:15.054
Feature 
Feature 'GnuPG' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:760:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:755:in `each'
./features/step_definitions/usb.rb:755: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
After features/support/hooks.rb:330 6.005 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 02:13:08)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/02:13:08_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_devel/3812/artifact/build-artifacts/02:13:08_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/02:13:08_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/02:13:08_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
1:24.788
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given a computer 0.219
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:24.569
Feature 
Feature 'GnuPG' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:760:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:755:in `each'
./features/step_definitions/usb.rb:755: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
After features/support/hooks.rb:330 5.685 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 02:14:39)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/02:14:39_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_devel/3812/artifact/build-artifacts/02:14:39_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/02:14:39_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/02:14:39_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal
After features/support/hooks.rb:100 0.000
Feature: Packages are up-to-date
Tags: @source
3.666
Scenario All packages are up-to-date
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:538 0.000
Steps
Given I have the build manifest for the image under test 0.000
Then all packages listed in the build manifest are up-to-date 3.666
Command 
Command failed (returned pid 64772 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_devel/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_devel/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_devel/tmp/tails-amd64-devel@470a0a36b3-20250515T0336Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_devel/tmp/tails-amd64-devel@470a0a36b3-20250515T0336Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - flatpak (1.14.10-1~deb12u1+tails1) to Debian bookworm-backports (1.16.0-2~bpo12+1)
.
<0> expected but was
<#<Process::Status: pid 64772 exit 1>>. (Test::Unit::AssertionFailedError)
/var/lib/jenkins/workspace/test_Tails_ISO_devel/features/support/helpers/misc_helpers.rb:307:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_devel/features/support/helpers/misc_helpers.rb:303:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_devel/features/support/helpers/misc_helpers.rb:303:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_devel/features/step_definitions/needed_package_updates.rb:8:in `/^all packages listed in the build manifest are up-to-date$/'
features/needed_package_updates.feature:12:in `Then all packages listed in the build manifest are up-to-date'
After features/support/hooks.rb:545 0.000
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:50.843
Scenario Booting Tails from a USB drive with an enabled persistent partition and reconfiguring it
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:50.843
Feature 
Feature 'GnuPG' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:760:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:755:in `each'
./features/step_definitions/usb.rb:755: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
After features/support/hooks.rb:330 6.290 
SCENARIO FAILED: 'Booting Tails from a USB drive with an enabled persistent partition and reconfiguring it' (at time 03:22:36)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/03:22:36_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_devel/3812/artifact/build-artifacts/03:22:36_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_devel/3812/artifact/build-artifacts/03:22:36_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_devel/3812/artifact/build-artifacts/03:22:36_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:34.266
Scenario Activating and deactivating Persistent Storage features
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 1:34.266
Feature 
Feature 'GnuPG' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:760:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:755:in `each'
./features/step_definitions/usb.rb:755: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
After features/support/hooks.rb:330 6.336 
SCENARIO FAILED: 'Activating and deactivating Persistent Storage features' (at time 03:24:16)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/03:24:16_Activating_and_deactivating_Persistent_Storage_features.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/03:24:16_Activating_and_deactivating_Persistent_Storage_features.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/03:24:16_Activating_and_deactivating_Persistent_Storage_features.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/03:24:16_Activating_and_deactivating_Persistent_Storage_features.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
2:5.251
Scenario Deleting data of a Persistent Storage feature
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 2:5.251
Feature 
Feature 'GnuPG' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:760:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:755:in `each'
./features/step_definitions/usb.rb:755: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
After features/support/hooks.rb:330 7.093 
SCENARIO FAILED: 'Deleting data of a Persistent Storage feature' (at time 03:26:28)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/03:26:28_Deleting_data_of_a_Persistent_Storage_feature.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/03:26:28_Deleting_data_of_a_Persistent_Storage_feature.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/03:26:28_Deleting_data_of_a_Persistent_Storage_feature.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/03:26:28_Deleting_data_of_a_Persistent_Storage_feature.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:34.313
Scenario Writing files to a read/write-enabled persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.021
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:34.313
Feature 
Feature 'GnuPG' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:760:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:755:in `each'
./features/step_definitions/usb.rb:755: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?
Then only the expected files are present on the persistence partition on USB drive "__internal" 0.000
After features/support/hooks.rb:330 6.350 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition' (at time 03:28:10)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/03:28:10_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_devel/3812/artifact/build-artifacts/03:28:10_Writing_files_to_a_read_write-enabled_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/03:28:10_Writing_files_to_a_read_write-enabled_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/03:28:10_Writing_files_to_a_read_write-enabled_persistent_partition.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:37.691
Scenario Creating and using a persistent NetworkManager connection
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:37.691
Feature 
Feature 'GnuPG' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:760:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:755:in `each'
./features/step_definitions/usb.rb:755: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
After features/support/hooks.rb:330 6.190 
SCENARIO FAILED: 'Creating and using a persistent NetworkManager connection' (at time 03:29:53)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/03:29:53_Creating_and_using_a_persistent_NetworkManager_connection.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/03:29:53_Creating_and_using_a_persistent_NetworkManager_connection.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/03:29:53_Creating_and_using_a_persistent_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/03:29:53_Creating_and_using_a_persistent_NetworkManager_connection.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:30.212
Scenario Changing the Persistent Storage passphrase
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 1:30.212
Feature 
Feature 'GnuPG' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:760:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:755:in `each'
./features/step_definitions/usb.rb:755: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:117: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
After features/support/hooks.rb:330 6.061 
SCENARIO FAILED: 'Changing the Persistent Storage passphrase' (at time 03:37:49)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/03:37:49_Changing_the_Persistent_Storage_passphrase.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/03:37:49_Changing_the_Persistent_Storage_passphrase.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/03:37:49_Changing_the_Persistent_Storage_passphrase.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/03:37:49_Changing_the_Persistent_Storage_passphrase.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:33.058
Scenario Dotfiles persistence
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:33.058
Feature 
Feature 'GnuPG' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:760:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:755:in `each'
./features/step_definitions/usb.rb:755: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:136:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
When I write some dotfile expected to persist 0.000
And I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then the expected persistent dotfile is present in the filesystem 0.000
After features/support/hooks.rb:330 6.355 
SCENARIO FAILED: 'Dotfiles persistence' (at time 03:40:29)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/03:40:29_Dotfiles_persistence.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/03:40:29_Dotfiles_persistence.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/03:40:29_Dotfiles_persistence.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/03:40:29_Dotfiles_persistence.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:55.270
Scenario Feature activation fails
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 and stopped at Tails Greeter's login screen 9.150
And I create a symlink "/home/amnesia/Persistent" to "/etc" 0.163
When I try to enable persistence 0.463
Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated 36.302
When I log in to a new session after having activated the Persistent Storage 50.466
And all notifications have disappeared 9.020
Then the Persistent Storage settings tell me that the Persistent Folder feature couldn't be activated 6.497
And all tps features are enabled 3.207
Feature 
Feature 'GnuPG' is not enabled.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:773:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:768:in `each'
./features/step_definitions/usb.rb:768:in `/^all tps features(| but the first one) are enabled$/'
features/persistence.feature:150:in `And all tps features are enabled'
And all tps features but the first one are active 0.000
After features/support/hooks.rb:330 5.839 
SCENARIO FAILED: 'Feature activation fails' (at time 03:42:31)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/03:42:31_Feature_activation_fails.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/03:42:31_Feature_activation_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/03:42:31_Feature_activation_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/03:42:31_Feature_activation_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
1:44.363
Scenario Using a persistent Pidgin configuration
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.027
Before features/support/hooks.rb:513 0.022
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:44.363
Feature 
Feature 'GnuPG' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:760:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:755:in `each'
./features/step_definitions/usb.rb:755: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/pidgin.feature:61: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 available upgrades have been checked 0.000
And all notifications have disappeared 0.000
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 0.000
Then I see Pidgin's account manager window 0.000
When I create my XMPP account 0.000
And I close Pidgin's account manager window 0.000
Then Pidgin automatically enables my XMPP account 0.000
When I close Pidgin 0.000
And I take note of the configured Pidgin accounts 0.000
And I shutdown Tails and wait for the computer to power off 0.000
Given a computer 0.000
And I start Tails from USB drive "__internal" and I login with persistence enabled 0.000
And Pidgin has the expected persistent accounts configured 0.000
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 0.000
Then Pidgin automatically enables my XMPP account 0.000
And I join some empty multi-user chat 0.000
# Exercise Pidgin AppArmor profile with persistence enabled.
# This should really be in dedicated scenarios, but it would be
# too costly to set up the virtual USB drive with persistence more
# than once in this feature.
Given I start monitoring the AppArmor log of "/usr/bin/pidgin" 0.000
Then I cannot add a certificate from the "/home/amnesia/.gnupg" directory to Pidgin 0.000
And AppArmor has denied "/usr/bin/pidgin" from opening "/home/amnesia/.gnupg/test.crt" 0.000
When I close Pidgin's certificate import failure dialog 0.000
And I close Pidgin's certificate manager 0.000
Given I restart monitoring the AppArmor log of "/usr/bin/pidgin" 0.000
Then I cannot add a certificate from the "/live/persistence/TailsData_unlocked/gnupg" directory to Pidgin 0.000
And AppArmor has denied "/usr/bin/pidgin" from opening "/live/persistence/TailsData_unlocked/gnupg/test.crt" 0.000
When I close Pidgin's certificate import failure dialog 0.000
And I close Pidgin's certificate manager 0.000
Then I can add a certificate from the "/home/amnesia" directory to Pidgin 0.000
After features/support/hooks.rb:521 0.046
After features/support/hooks.rb:330 6.453 
SCENARIO FAILED: 'Using a persistent Pidgin configuration' (at time 04:13:37)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/04:13:37_Using_a_persistent_Pidgin_configuration.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/04:13:37_Using_a_persistent_Pidgin_configuration.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/04:13:37_Using_a_persistent_Pidgin_configuration.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/04:13:37_Using_a_persistent_Pidgin_configuration.journal
After features/support/hooks.rb:100 0.000
Feature: Tails has a sane default configuration
Tags: @product
1:51.516
Scenario No unexpected error messages in the journal after booting from USB drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.028
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:51.516
Feature 
Feature 'GnuPG' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:760:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:755:in `each'
./features/step_definitions/usb.rb:755: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:24:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
Then there are no unexpected messages of priority "err" or higher in the journal 0.000
After features/support/hooks.rb:330 6.175 
SCENARIO FAILED: 'No unexpected error messages in the journal after booting from USB drive' (at time 04:19:57)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/04:19:57_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_devel/3812/artifact/build-artifacts/04:19:57_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/04:19:57_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/04:19:57_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:29.932
Scenario The persistent Tor Browser directory is usable
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:29.932
Feature 
Feature 'GnuPG' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:760:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:755:in `each'
./features/step_definitions/usb.rb:755: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:105: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
Then the persistent Tor Browser directory exists 0.000
And there is a GNOME bookmark for the persistent Tor Browser directory 0.000
When I start the Tor Browser 0.000
And I open the address "https://tails.net/about" in the Tor Browser 0.000
And "Tails - How Tails works" has loaded in the Tor Browser 0.000
Then I can save the current page as "index.html" to the persistent Tor Browser GNOME bookmark 0.000
And I open the address "file:///home/amnesia/Persistent/Tor Browser/index.html" 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 Tor Browser directory 0.000
After features/support/hooks.rb:330 6.526 
SCENARIO FAILED: 'The persistent Tor Browser directory is usable' (at time 05:00:20)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/05:00:20_The_persistent_Tor_Browser_directory_is_usable.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/05:00:20_The_persistent_Tor_Browser_directory_is_usable.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/05:00:20_The_persistent_Tor_Browser_directory_is_usable.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/05:00:20_The_persistent_Tor_Browser_directory_is_usable.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:30.124
Scenario Persistent browser bookmarks
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 1:30.124
Feature 
Feature 'GnuPG' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:760:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:755:in `each'
./features/step_definitions/usb.rb:755: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:135: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
After features/support/hooks.rb:330 6.167 
SCENARIO FAILED: 'Persistent browser bookmarks' (at time 05:06:27)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/05:06:27_Persistent_browser_bookmarks.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/05:06:27_Persistent_browser_bookmarks.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/05:06:27_Persistent_browser_bookmarks.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/05:06:27_Persistent_browser_bookmarks.journal
After features/support/hooks.rb:100 0.000
Feature: Using Totem
Tags: @product
1:34.221
Scenario Watching MP4 videos stored on the persistent volume should work as expected given our AppArmor confinement
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:34.221
Feature 
Feature 'GnuPG' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:760:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:755:in `each'
./features/step_definitions/usb.rb:755: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:55: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
Given I close Totem 0.000
And I start monitoring the AppArmor log of "/usr/bin/totem" 0.000
And I copy the sample videos to "/home/amnesia/.gnupg" as user "amnesia" 0.000
When I try to open "/home/amnesia/.gnupg/video.mp4" with Totem 0.000
Then Totem tells me it is not allowed to open this file 0.000
And AppArmor has denied "/usr/bin/totem" from opening "/home/amnesia/.gnupg/video.mp4" 0.000
After features/support/hooks.rb:330 6.355 
SCENARIO FAILED: 'Watching MP4 videos stored on the persistent volume should work as expected given our AppArmor confinement' (at time 05:10:46)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/05:10:46_Watching_MP4_videos_stored_on_the_persistent_volume_should_work_as_expected_given_our_AppArmor_confinement.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/05:10:46_Watching_MP4_videos_stored_on_the_persistent_volume_should_work_as_expected_given_our_AppArmor_confinement.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/05:10:46_Watching_MP4_videos_stored_on_the_persistent_volume_should_work_as_expected_given_our_AppArmor_confinement.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3812/artifact/build-artifacts/05:10:46_Watching_MP4_videos_stored_on_the_persistent_volume_should_work_as_expected_given_our_AppArmor_confinement.journal
After features/support/hooks.rb:100 0.000