Project Number Date
test_Tails_ISO_stable 5746 28 Jun 2025, 10:22

Failures Overview

The following summary displays scenarios that failed.

Feature: Localization
Tags: @product @doc @slow @not_release_blocker
1:10.723
Scenario Outline Tails is localized for every tier-1 language
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 stopped at Tails Greeter's login screen 13.781
When I log in to a new session in Arabic (ar) 43.884
Then the keyboard layout is set to "us" 0.389
When the network is plugged 0.094
And Tor is ready 12.574
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/localization.feature:44:in `And Tor is ready'
features/localization.feature:26:in `And Tor is ready'
Then I successfully start the Unsafe Browser 0.000
And I kill the Unsafe Browser 0.000
When I enable the screen keyboard 0.000
Then the screen keyboard works in Tor Browser 0.000
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 5.639 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#1)' (at time 03:02:34)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/03:02:34_Tails_is_localized_for_every_tier-1_language,_Examples___1_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/03:02:34_Tails_is_localized_for_every_tier-1_language,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/03:02:34_Tails_is_localized_for_every_tier-1_language,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/03:02:34_Tails_is_localized_for_every_tier-1_language,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
52.571
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 9.161
When I log in to a new session in English (en) 31.883
Then the keyboard layout is set to "us" 0.168
When the network is plugged 0.114
And Tor is ready 11.243
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/localization.feature:46:in `And Tor is ready'
features/localization.feature:26:in `And Tor is ready'
Then I successfully start the Unsafe Browser 0.000
And I kill the Unsafe Browser 0.000
When I enable the screen keyboard 0.000
Then the screen keyboard works in Tor Browser 0.000
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 6.235 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#3)' (at time 03:07:32)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/03:07:32_Tails_is_localized_for_every_tier-1_language,_Examples___3_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/03:07:32_Tails_is_localized_for_every_tier-1_language,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/03:07:32_Tails_is_localized_for_every_tier-1_language,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/03:07:32_Tails_is_localized_for_every_tier-1_language,_Examples___3_.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:29.985
Scenario Creating a Persistent Storage
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.072
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 1:29.985
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/persistence.feature:20:in `Given I have started Tails without network from a USB drive without a persistent partition and logged in'
Then Tails is running from USB drive "__internal" 0.000
When I create a file in the Persistent directory 0.000
And I create a persistent partition with the default settings 0.000
Then the file I created was copied to the Persistent Storage 0.000
When 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 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.244 
SCENARIO FAILED: 'Creating a Persistent Storage' (at time 03:58:19)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/03:58:19_Creating_a_Persistent_Storage.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/03:58:19_Creating_a_Persistent_Storage.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/03:58:19_Creating_a_Persistent_Storage.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/03:58:19_Creating_a_Persistent_Storage.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:29.334
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.010
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:29.334
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: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.992 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition' (at time 04:10:18)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/04:10:18_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/5746/artifact/build-artifacts/04:10:18_Writing_files_to_a_read_write-enabled_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/04:10:18_Writing_files_to_a_read_write-enabled_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/04:10:18_Writing_files_to_a_read_write-enabled_persistent_partition.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
3:52.358
Scenario Persistent Greeter options
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 1:3.079
When I enable persistence 1:30.265
Then no persistent Greeter options were restored 18.202
When I set all Greeter options to non-default values 1:0.811
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.822 
SCENARIO FAILED: 'Persistent Greeter options' (at time 04:22:59)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/04:22:59_Persistent_Greeter_options.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/04:22:59_Persistent_Greeter_options.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/04:22:59_Persistent_Greeter_options.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/04:22:59_Persistent_Greeter_options.journal
After features/support/hooks.rb:100 0.000
Feature: The Tor enforcement is effective
Tags: @product
2:4.673
Scenario Anti test: Detecting TCP leaks from the Unsafe Browser with the firewall leak detector
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails from DVD and logged in and the network is connected 21.937
And I capture all network traffic 0.104
When I successfully start the Unsafe Browser 28.727
And I open the Tails homepage in the Unsafe Browser 10.201
And the Tails homepage loads in the Unsafe Browser 1:3.702
cannot 
cannot find TailsHomepage.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/browser.rb:316:in `/^the Tails homepage loads in the Unsafe Browser$/'
features/tor_enforcement.feature:20:in `And the Tails homepage loads in the Unsafe Browser'
Then the firewall leak detector has detected leaks 0.000
After features/support/hooks.rb:330 6.572 
SCENARIO FAILED: 'Anti test: Detecting TCP leaks from the Unsafe Browser with the firewall leak detector' (at time 05:22:32)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/05:22:32_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/05:22:32_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/05:22:32_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/05:22:32_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.journal
After features/support/hooks.rb:100 0.031
Feature: Browsing the web using the Unsafe Browser
Tags: @product
2:7.540
Scenario The Unsafe Browser can load a web page from the Internet
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails from DVD and logged in and the network is connected 19.484
When I successfully start the Unsafe Browser 30.861
When I open the Tails homepage in the Unsafe Browser 16.733
Then the Tails homepage loads in the Unsafe Browser 1:0.460
cannot 
cannot find TailsHomepage.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/browser.rb:316:in `/^the Tails homepage loads in the Unsafe Browser$/'
features/unsafe_browser.feature:38:in `Then the Tails homepage loads in the Unsafe Browser'
And the Unsafe Browser has sent packets out to the Internet 0.000
After features/support/hooks.rb:330 6.065 
SCENARIO FAILED: 'The Unsafe Browser can load a web page from the Internet' (at time 06:07:34)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/06:07:34_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/06:07:34_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/06:07:34_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/06:07:34_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
44.261
Scenario Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile
Steps
When I plug and mount a USB drive containing a basic VeraCrypt file container with a keyfile 33.238
And I unlock and mount this VeraCrypt file container with GNOME Disks 11.022
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:68: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.711 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile' (at time 06:22:31)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/06:22:31_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/06:22:31_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/06:22:31_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/06:22:31_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.journal
After features/support/hooks.rb:100 0.014
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
37.094
Scenario Use GNOME Disks to unlock a basic VeraCrypt file container with a PIM
Steps
When I plug and mount a USB drive containing a basic VeraCrypt file container with a PIM 24.471
And I unlock and mount this VeraCrypt file container with GNOME Disks 12.622
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:84: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.203 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a PIM' (at time 06:24:52)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/06:24:52_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/06:24:52_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/06:24:52_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5746/artifact/build-artifacts/06:24:52_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.journal
After features/support/hooks.rb:100 0.000