Project Number Date
test_Tails_ISO_stable 5739 25 Jun 2025, 17:57

Failures Overview

The following summary displays scenarios that failed.

Feature: Emergency shutdown
Tags: @product @not_release_blocker
2:24.893
Scenario Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails from DVD without network and logged in 9.130
And I prepare Tails for memory erasure tests 0.662
And I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 40.518
And I fill the USB drive with a known pattern 1.250
And I read the content of the test FS 0.075
And patterns cover at least 99% of the test FS size in the guest's memory 2.589 
Pattern coverage: 106.113% (97 MiB out of 91 MiB reference memory)
When I eject the boot medium 0.249
And I wait for Tails to finish wiping the memory 1:30.416
cannot 
cannot find MemoryWipeCompleted.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/erase_memory.rb:232:in `/^I wait for Tails to finish wiping the memory$/'
features/emergency_shutdown.feature:44:in `And I wait for Tails to finish wiping the memory'
Then I find very few patterns in the guest's memory 0.000
After features/support/hooks.rb:330 10.565 
SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4' (at time 02:06:39)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/02:06:39_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/02:06:39_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/02:06:39_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.journal
After features/support/hooks.rb:100 0.001
Feature: Tails persistence
Tags: @product
1:13.684
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.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 51.441
And the network is plugged 4.484
And Tor is ready 17.758
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:653:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:607:in `/^Tor is ready$/'
features/persistence.feature:75:in `And Tor is ready'
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 7.129 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition' (at time 03:47:21)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/03:47:21_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_stable/5739/artifact/build-artifacts/03:47:21_Writing_files_to_a_read_write-enabled_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/03:47:21_Writing_files_to_a_read_write-enabled_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/03:47:21_Writing_files_to_a_read_write-enabled_persistent_partition.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
4:12.867
Scenario Persistent Greeter options
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 and stopped at Tails Greeter's login screen 1:10.396
When I enable persistence 1:42.893
Then no persistent Greeter options were restored 21.233
When I set all Greeter options to non-default values 58.344
cannot 
cannot find TailsGreeterAdminPasswordDialog.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:548:in `/^I set an administration password$/'
./features/step_definitions/usb.rb:1585:in `/^I set all Greeter options to non-default values$/'
features/persistence.feature:106:in `When I set all Greeter options to non-default values'
And I log in to a new session in German (de) after having activated the Persistent Storage 0.000
Then all Greeter options are set to non-default values 0.000
When I cold reboot the computer 0.000
And the computer reboots Tails 0.000
Given I enable persistence 0.000
Then persistent Greeter options were restored 0.000
When I log in to a new session after having activated the Persistent Storage 0.000
Then all Greeter options are set to non-default values 0.000
After features/support/hooks.rb:330 6.273 
SCENARIO FAILED: 'Persistent Greeter options' (at time 04:00:44)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:00:44_Persistent_Greeter_options.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:00:44_Persistent_Greeter_options.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:00:44_Persistent_Greeter_options.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:00:44_Persistent_Greeter_options.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:10.560
Scenario Dotfiles persistence
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:10.560
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:136:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
When I write some dotfile expected to persist 0.000
And I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then the expected persistent dotfile is present in the filesystem 0.000
After features/support/hooks.rb:330 7.269 
SCENARIO FAILED: 'Dotfiles persistence' (at time 04:10:40)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:10:40_Dotfiles_persistence.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:10:40_Dotfiles_persistence.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:10:40_Dotfiles_persistence.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:10:40_Dotfiles_persistence.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:37.935
Scenario Feature activation fails
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 and stopped at Tails Greeter's login screen 33.044
And I create a symlink "/home/amnesia/Persistent" to "/etc" 1.411
When I try to enable persistence 3.467
Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated 1:0.012
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:1724:in `/^the Welcome Screen tells me that the Persistent Folder feature couldn't be activated$/'
features/persistence.feature:146:in `Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated'
When I log in to a new session after having activated the Persistent Storage 0.000
And all notifications have disappeared 0.000
Then the Persistent Storage settings tell me that the Persistent Folder feature couldn't be activated 0.000
And all tps features are enabled 0.000
And all tps features but the first one are active 0.000
After features/support/hooks.rb:330 12.364 
SCENARIO FAILED: 'Feature activation fails' (at time 04:12:25)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:12:25_Feature_activation_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:12:25_Feature_activation_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:12:25_Feature_activation_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:37.563
Scenario Manual filesystem repair is successful
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 20.209
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 16.845
When I try to enable persistence 0.506
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 1:0.002
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:1732:in `/^the Welcome Screen tells me that filesystem errors were found on the Persistent Storage$/'
features/persistence.feature:176:in `Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage'
When I repair the filesystem of the Persistent Storage 0.000
Then the Welcome Screen tells me that the filesystem was repaired successfully 0.000
And the filesystem of the Persistent Storage was repaired 0.000
When I close the filesystem repair dialog 0.000
Then persistence is successfully enabled 0.000
After features/support/hooks.rb:330 15.294 
SCENARIO FAILED: 'Manual filesystem repair is successful' (at time 04:26:28)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:26:28_Manual_filesystem_repair_is_successful.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:26:28_Manual_filesystem_repair_is_successful.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:26:28_Manual_filesystem_repair_is_successful.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product @doc
1:36.834
Scenario Manual filesystem repair fails
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 and stopped at Tails Greeter's login screen 31.237
And the Persistent Storage filesystem is corrupted beyond what e2fsck can repair 2.018
When I try to enable persistence 3.566
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 1:0.012
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:1732:in `/^the Welcome Screen tells me that filesystem errors were found on the Persistent Storage$/'
features/persistence.feature:188:in `Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage'
When I repair the filesystem of the Persistent Storage 0.000
Then the Welcome Screen tells me that it failed to repair the Persistent Storage 0.000
When I log in to a new session 0.000
And all notifications have disappeared 0.000
# Now both WhisperBack and Tor Browser has started at the same
# time, so we do not know which window is focused. The steps about
# Tor Browser care about that, but the ones about WhisperBack do
# not, so we first deal with WhisperBack and then kill it to
# ensure that Tor Browser is focused.
Then WhisperBack is prefilled for fsck with summary: "Failed to repair the file system of your Persistent Storage" 0.000
And the file "/var/lib/gdm3/post-greeter-whisperback.json" is empty 0.000
When I close the "whisperback" window 0.000
Then the Tor Browser starts 0.000
And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:330 13.655 
SCENARIO FAILED: 'Manual filesystem repair fails' (at time 04:28:23)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:28:23_Manual_filesystem_repair_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:28:23_Manual_filesystem_repair_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:28:23_Manual_filesystem_repair_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product @doc
1:34.574
Scenario Filesystem and I/O errors
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.051
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 19.641
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 12.619
And Tails detects disk read failures on the boot device 1.951
When I try to enable persistence 0.359
Then the Welcome Screen tells me that my hardware is probably failing 1:0.001
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:1835:in `/^the Welcome Screen tells me that my hardware is probably failing$/'
features/persistence.feature:210:in `Then the Welcome Screen tells me that my hardware is probably failing'
When I log in to a new session 0.000
And all notifications have disappeared 0.000
Then the Tor Browser starts 0.000
And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:330 19.014 
SCENARIO FAILED: 'Filesystem and I/O errors' (at time 04:30:16)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:30:16_Filesystem_and_I_O_errors.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:30:16_Filesystem_and_I_O_errors.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:30:16_Filesystem_and_I_O_errors.journal
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
1:28.041
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 1:28.041
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ without\ a\ persistent\ partition\ and\ logged\ in$/'
features/persistent_tor_bridges.feature:8:in `Given I have started Tails without network from a USB drive without a persistent partition and logged in'
And I create a persistent partition with the default settings 0.000
Then the "TorConfiguration" tps feature is not enabled 0.000
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 0.000
And I wait until Tor is ready 0.000
Then tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 0.000
When I cold reboot the computer 0.000
And the computer reboots Tails 0.000
And I enable persistence 0.000
And I capture all network traffic 0.000
And I log in to a new session 0.000
Then tca.conf includes the configured bridges 0.000
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
Feature: Using persistent Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Using Persistent Tor bridges
Steps
When I choose to connect to Tor automatically 0.000
And I accept Tor Connection's offer to use my persistent bridges 0.000
And I click "Connect to Tor" 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:330 7.063 
SCENARIO FAILED: 'Using Persistent Tor bridges' (at time 04:32:00)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:32:00_Using_Persistent_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:32:00_Using_Persistent_Tor_bridges.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:32:00_Using_Persistent_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:32:00_Using_Persistent_Tor_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
1:15.683
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 1:15.683
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ without\ a\ persistent\ partition\ and\ logged\ in$/'
features/persistent_tor_bridges.feature:8:in `Given I have started Tails without network from a USB drive without a persistent partition and logged in'
And I create a persistent partition with the default settings 0.000
Then the "TorConfiguration" tps feature is not enabled 0.000
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 0.000
And I wait until Tor is ready 0.000
Then tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 0.000
When I cold reboot the computer 0.000
And the computer reboots Tails 0.000
And I enable persistence 0.000
And I capture all network traffic 0.000
And I log in to a new session 0.000
Then tca.conf includes the configured bridges 0.000
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
Feature: Using persistent Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Disabling persistence of Tor bridges
Steps
When I choose to connect to Tor automatically 0.000
And I accept Tor Connection's offer to use my persistent bridges 0.000
And I disable saving bridges to Persistent Storage 0.000
And I configure a direct connection in the Tor Connection Assistant 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes no bridge 0.000
And the "TorConfiguration" tps feature is not enabled and not active 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:330 6.066 
SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 04:33:23)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:33:23_Disabling_persistence_of_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:33:23_Disabling_persistence_of_Tor_bridges.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:33:23_Disabling_persistence_of_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:33:23_Disabling_persistence_of_Tor_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
1:11.499
Scenario Chatting with some friend over XMPP
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Before features/support/hooks.rb:507 0.015
Steps
Given I have started Tails from DVD and logged in and the network is connected 34.689
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 13.096
Then I see Pidgin's account manager window 9.624
When I create my XMPP account 14.088
cannot 
cannot find PidginAddAccountXMPPDomain.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/pidgin.rb:130:in `/^I create my XMPP account$/'
features/pidgin.feature:21:in `When I create my XMPP account'
And I close Pidgin's account manager window 0.000
Then Pidgin automatically enables my XMPP account 0.000
Given my XMPP friend goes online 0.000
When I start a conversation with my friend 0.000
And I say something to my friend 0.000
Then I receive a response from my friend 0.000
After features/support/hooks.rb:515 0.060
After features/support/hooks.rb:330 5.799 
SCENARIO FAILED: 'Chatting with some friend over XMPP' (at time 04:35:40)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:35:40_Chatting_with_some_friend_over_XMPP.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:35:40_Chatting_with_some_friend_over_XMPP.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:35:40_Chatting_with_some_friend_over_XMPP.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:35:40_Chatting_with_some_friend_over_XMPP.journal
After features/support/hooks.rb:100 0.000
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
1:4.855
Scenario Connecting to the tails multi-user chat with my XMPP account
Before features/support/hooks.rb:266 0.006
Before features/support/hooks.rb:273 0.072
Before features/support/hooks.rb:507 0.019
Steps
Given I have started Tails from DVD and logged in and the network is connected 35.165
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.940
Then I see Pidgin's account manager window 7.464
And I create my XMPP account 10.285
cannot 
cannot find PidginAddAccountXMPPDomain.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/pidgin.rb:130:in `/^I create my XMPP account$/'
features/pidgin.feature:54:in `And I create my XMPP account'
And I close Pidgin's account manager window 0.000
Then Pidgin automatically enables my XMPP account 0.000
And I can join the "tails" channel on "chat.disroot.org" 0.000
After features/support/hooks.rb:515 0.039
After features/support/hooks.rb:330 7.354 
SCENARIO FAILED: 'Connecting to the tails multi-user chat with my XMPP account' (at time 04:41:16)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:41:16_Connecting_to_the_tails_multi-user_chat_with_my_XMPP_account.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:41:16_Connecting_to_the_tails_multi-user_chat_with_my_XMPP_account.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:41:16_Connecting_to_the_tails_multi-user_chat_with_my_XMPP_account.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:41:16_Connecting_to_the_tails_multi-user_chat_with_my_XMPP_account.journal
After features/support/hooks.rb:100 0.000
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
1:18.386
Scenario Using a persistent Pidgin configuration
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.021
Before features/support/hooks.rb:507 0.019
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:18.386
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/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:515 0.042
After features/support/hooks.rb:330 6.429 
SCENARIO FAILED: 'Using a persistent Pidgin configuration' (at time 04:42:43)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:42:43_Using_a_persistent_Pidgin_configuration.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:42:43_Using_a_persistent_Pidgin_configuration.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:42:43_Using_a_persistent_Pidgin_configuration.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:42:43_Using_a_persistent_Pidgin_configuration.journal
After features/support/hooks.rb:100 0.000
Feature: Random Seed
Tags: @product
3:49.997
Scenario A random seed is read during boot and written during boot and shutdown
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Steps
Given a computer 0.393
And I temporarily create a 7200 MiB disk named "temp" 0.101
And I plug USB drive "temp" 1.054
And I write the Tails USB image to disk "temp" 1:7.031
Then there is no random seed on USB drive "temp" 12.878
When I start Tails from USB drive "temp" with network unplugged 2:28.538
execution 
execution expired (RemoteShell::Timeout)
./features/support/helpers/misc_helpers.rb:114:in `sleep'
./features/support/helpers/misc_helpers.rb:114:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/common_steps.rb:459:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:284:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/random_seed.feature:12:in `When I start Tails from USB drive "temp" with network unplugged'
Then the random seed was written multiple times on first boot 0.000
And there is a random seed on USB drive "temp" 0.000
When I log in to a new session 0.000
And I wait for the random seed to be updated 0.000
Then there is a random seed on USB drive "temp" 0.000
And the random seed is different from the previous one 0.000
And I shutdown Tails and wait for the computer to power off 0.000
Then there is a random seed on USB drive "temp" 0.000
And the random seed is different from the previous one 0.000
After features/support/hooks.rb:330 7.331 
SCENARIO FAILED: 'A random seed is read during boot and written during boot and shutdown' (at time 04:46:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:46:42_A_random_seed_is_read_during_boot_and_written_during_boot_and_shutdown.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:46:42_A_random_seed_is_read_during_boot_and_written_during_boot_and_shutdown.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:46:42_A_random_seed_is_read_during_boot_and_written_during_boot_and_shutdown.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/04:46:42_A_random_seed_is_read_during_boot_and_written_during_boot_and_shutdown.journal
After features/support/hooks.rb:100 0.331
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
1:6.314
Scenario Use GNOME Disks to unlock a hidden VeraCrypt file container
Steps
When I plug and mount a USB drive containing a hidden VeraCrypt file container 49.248
And I unlock and mount this VeraCrypt file container with GNOME Disks 17.065
The 
The Dogtail init script raised: ActionNotSupported: Cannot do 'activate' action on [DEAD]
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:346:in `call_tree_node_method'
./features/support/helpers/dogtail.rb:350:in `doActionNamed'
./features/support/helpers/dogtail.rb:364:in `activate'
./features/step_definitions/veracrypt.rb:240:in `/^I unlock and mount this VeraCrypt (volume|file container) with GNOME Disks$/'
features/veracrypt.feature:76:in `And I unlock and mount this VeraCrypt file container with GNOME Disks'
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt file container 0.000
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 7.572 
SCENARIO FAILED: 'Use GNOME Disks to unlock a hidden VeraCrypt file container' (at time 06:20:41)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/06:20:41_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/06:20:41_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/06:20:41_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5739/artifact/build-artifacts/06:20:41_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:100 0.014