Project Number Date
test_Tails_ISO_21734-bump-snapshot-restore-timeout 3 18 Aug 2026, 15:52

Failures Overview

The following summary displays scenarios that failed.

Feature: Time syncing
Tags: @product @check_tor_leaks @not_release_blocker
1:38.650
Scenario The system time is not synced to the hardware clock
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Before features/support/hooks.rb:527 0.002
Steps
Given I have started Tails from DVD without network and logged in 3.383
When I bump the system time with "-15 days" 0.215
And I warm reboot the computer 0.006
And the computer reboots Tails 1:35.045
can 
can not find any of the patterns ["TailsGreeter.png", "PlymouthGraphicsCardFailureMessage.png"] on the screen (FindFailed)
./features/support/helpers/screen.rb:248:in `rescue in wait_any'
./features/support/helpers/screen.rb:232:in `wait_any'
./features/step_definitions/common_steps.rb:448:in `/^the computer (?:re)?boots Tails$/'
features/time_syncing.feature:37:in `And the computer reboots Tails'
Then Tails' hardware clock is close to the host system's time 0.000
After features/support/hooks.rb:535 0.038
After features/support/hooks.rb:339 4.923 
SCENARIO FAILED: 'The system time is not synced to the hardware clock' (at time 00:18:43)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/00:18:43_The_system_time_is_not_synced_to_the_hardware_clock.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/00:18:43_The_system_time_is_not_synced_to_the_hardware_clock.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/00:18:43_The_system_time_is_not_synced_to_the_hardware_clock.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/00:18:43_The_system_time_is_not_synced_to_the_hardware_clock.journal
After features/support/hooks.rb:108 0.006
Feature: Time syncing
Tags: @product @check_tor_leaks
20.235
Scenario I can manually recover from time sync failure when connecting automatically to obfs4 bridges with a clock East of UTC
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Before features/support/hooks.rb:527 0.012
Steps
Given I have started Tails from DVD without network and logged in 3.544
When I bump the system time with "+8 hours +15 minutes" 0.160
And all notifications have disappeared 4.254
And I capture all network traffic 0.002
And I make sure time sync before Tor connects fails 0.056
And the network is plugged 0.027
And the Tor Connection Assistant autostarts 1.629
When I configure the default bridges in the Tor Connection Assistant in easy mode without connecting 10.561
The 
The Dogtail init script raised: SearchError: descendant of [application | Tor Connection]: child with name='Connect to Tor automatically' roleName='radio button'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/tor.rb:533:in `tca_configure'
./features/step_definitions/tor.rb:670:in `/^I configure (?:some|the) (persistent )?(\w+) bridges (from a QR code )?in the Tor Connection Assistant(?: in (easy|hide) mode)?( without connecting|)$/'
features/time_syncing.feature:70:in `When I configure the default bridges in the Tor Connection Assistant in easy mode without connecting'
And I click "Connect to Tor" 0.000
And the Tor Connection Assistant fails to connect to Tor 0.000
# The "Fix Clock" button allows users to recover from this bug
Then I set the time zone in Tor Connection to "Asia/Shanghai" 0.000
Then the system clock is less than 20 minutes incorrect 0.000
When I click "Connect to Tor" 0.000
Then I wait until Tor is ready 0.000
And all Internet traffic has only flowed through the default bridges or fake connectivity check service 0.000
# check that htpdate has done its job
And the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:535 0.030
After features/support/hooks.rb:339 5.358 
SCENARIO FAILED: 'I can manually recover from time sync failure when connecting automatically to obfs4 bridges with a clock East of UTC' (at time 00:20:57)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/00:20:57_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/00:20:57_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/00:20:57_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/00:20:57_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.journal
After features/support/hooks.rb:108 0.060
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
17.851
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 4.623
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 12.879
The 
The Dogtail init script raised: SearchError: descendant of [application | Tor Connection]: child with name='Connect to Tor automatically' roleName='radio button'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/tor.rb:533:in `tca_configure'
./features/step_definitions/tor.rb:553:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:706:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:660:in `/^Tor is ready$/'
features/usb_upgrade.feature:133:in `And Tor is ready'
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.000
After features/support/hooks.rb:339 5.112 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 01:20:59)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/01:20:59_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/01:20:59_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/01:20:59_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/01:20:59_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:108 0.000
Feature: Using Evince
Tags: @product
26.735
Scenario I can view and print a PDF file stored in persistent /home/amnesia/Persistent
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 4.443
And I copy "/usr/share/cups/data/default-testpage.pdf" to "/home/amnesia/Persistent" as user "amnesia" 0.058
Then the file "/home/amnesia/Persistent/default-testpage.pdf" exists 0.057
When I open "/home/amnesia/Persistent/default-testpage.pdf" with Evince 22.174
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/common_steps.rb:1019:in `/^I run "([^"]+)" in Console$/'
./features/step_definitions/evince.rb:2:in `/^I open "([^"]+)" with Evince$/'
features/evince.feature:23:in `When I open "/home/amnesia/Persistent/default-testpage.pdf" with Evince'
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:339 5.441 
SCENARIO FAILED: 'I can view and print a PDF file stored in persistent /home/amnesia/Persistent' (at time 01:31:16)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/01:31:16_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_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/01:31:16_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_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/01:31:16_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_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/01:31:16_I_can_view_and_print_a_PDF_file_stored_in_persistent__home_amnesia_Persistent.journal
After features/support/hooks.rb:108 0.000
Feature: Networking
Tags: @product
52.839
Scenario No initial network
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Steps
Given I have started Tails from DVD without network and logged in 3.794
And I wait between 30 and 60 seconds 39.000 
Slept for 39 seconds
Then the Tor Status icon tells me that Tor is not usable 10.044
cannot 
cannot find TorStatusNotUsable.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/checks.rb:335:in `/^the Tor Status icon tells me that Tor is( not)? usable$/'
features/networking.feature:7:in `Then the Tor Status icon tells me that Tor is not usable'
When the network is plugged 0.000
Then I successfully configure Tor 0.000
And the Tor Status icon tells me that Tor is usable 0.000
And all notifications have disappeared 0.000
And the time has synced 0.000
After features/support/hooks.rb:339 5.244 
SCENARIO FAILED: 'No initial network' (at time 02:20:12)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/02:20:12_No_initial_network.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/02:20:12_No_initial_network.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/02:20:12_No_initial_network.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/02:20:12_No_initial_network.journal
After features/support/hooks.rb:108 0.000
Feature: Tails persistence
Tags: @product
16.605
Scenario Changing the Persistent Storage passphrase
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 5.143
# 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 11.462
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/support/helpers/dogtail.rb:371:in `grabFocus'
./features/step_definitions/usb.rb:484:in `/^I change the passphrase of the Persistent Storage( back to the original)?$/'
features/persistence.feature:128:in `When I change the passphrase of the Persistent Storage'
And I shutdown Tails and wait for the computer to power off 0.000
Then I start Tails from USB drive "__internal" with network unplugged and I login with the changed persistence passphrase 0.000
And I change the passphrase of the Persistent Storage back to the original 0.000
After features/support/hooks.rb:339 4.940 
SCENARIO FAILED: 'Changing the Persistent Storage passphrase' (at time 02:33:15)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/02:33:15_Changing_the_Persistent_Storage_passphrase.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/02:33:15_Changing_the_Persistent_Storage_passphrase.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/02:33:15_Changing_the_Persistent_Storage_passphrase.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/02:33:15_Changing_the_Persistent_Storage_passphrase.journal
After features/support/hooks.rb:108 0.000
Feature: Using persistent Tor bridges and pluggable transports
20.245
Background
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 5.839
And I create a persistent partition with the default settings 14.406
The 
The Dogtail init script raised: SearchError: descendant of [frame | Persistent Storage]: 'Create Persistent Storage' button
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:272:in `button'
./features/step_definitions/usb.rb:386:in `/^I try to create a persistent partition( for Additional Software)?( using the wizard that was already open)?$/'
./features/step_definitions/usb.rb:355:in `/^I create a persistent partition( with the default settings)?( for Additional Software)?( using the wizard that was already open)?$/'
features/persistent_tor_bridges.feature:9:in `And I create a persistent partition with the default settings'
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:339 5.272 
SCENARIO FAILED: 'Using Persistent Tor bridges' (at time 02:42:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/02:42:26_Using_Persistent_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/02:42:26_Using_Persistent_Tor_bridges.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/02:42:26_Using_Persistent_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/02:42:26_Using_Persistent_Tor_bridges.journal
After features/support/hooks.rb:108 0.000
Feature: Tor Connection helps the user in connecting to Tor
Tags: @product
18.894
Scenario Starting Tor Connection before connecting to Wi-Fi
Steps
When I start "Tor Connection" via GNOME Activities Overview 8.566
Then the Tor Connection Assistant reports that I am not connected to a local network 10.327
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'Tor Connection' application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/tor.rb:418:in `new'
./features/step_definitions/tor.rb:418:in `tor_connection_assistant'
./features/step_definitions/tor.rb:1248:in `/^the Tor Connection Assistant reports that I am not connected to a local network$/'
features/tor_connection.feature:11:in `Then the Tor Connection Assistant reports that I am not connected to a local network'
When I plug a Wi-Fi adapter 0.000
Then Tor Connection suggests me to connect to Wi-Fi 0.000
And I click on the Wi-Fi settings 0.000
And The Wi-Fi settings are displayed 0.000
After features/support/hooks.rb:339 5.260 
SCENARIO FAILED: 'Starting Tor Connection before connecting to Wi-Fi' (at time 02:56:31)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/02:56:31_Starting_Tor_Connection_before_connecting_to_Wi-Fi.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/02:56:31_Starting_Tor_Connection_before_connecting_to_Wi-Fi.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/02:56:31_Starting_Tor_Connection_before_connecting_to_Wi-Fi.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/02:56:31_Starting_Tor_Connection_before_connecting_to_Wi-Fi.journal
After features/support/hooks.rb:108 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
38.145
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 25.314
And I unlock and mount this VeraCrypt file container with GNOME Disks 12.830
The 
The Dogtail init script raised: SearchError: descendant of [application | gnome-disks]: 'Attach Disk Image… (.iso, .img)' button
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:272:in `button'
./features/step_definitions/veracrypt.rb:211: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:339 5.122 
SCENARIO FAILED: 'Use GNOME Disks to unlock a hidden VeraCrypt file container' (at time 03:24:57)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/03:24:57_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_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/03:24:57_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/03:24:57_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/3/artifact/build-artifacts/03:24:57_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:108 0.020