Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 12 03 Jun 2026, 19:55

Failures Overview

The following summary displays scenarios that failed.

Feature: Localization
Tags: @product
1:53.701
Scenario Cleartext localization preferences have priority over Persistent Storage
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.014
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 8.455
# The first boot simulates a legacy Tails, where locale is only saved in Persistent Storage
Then Tails is running from USB drive "__internal" 0.319
And I create a persistent partition 29.520
And I manually store legacy localization settings in Persistent Storage 0.198
When I shutdown Tails and wait for the computer to power off 6.847
# The second boot verifies that the legacy setting still works
And I start Tails from USB drive "__internal" with network unplugged 38.591
Then the Welcome Screen's language is set to English 0.232
And the Welcome Screen's formats is set to United States 0.280
When I enable persistence 8.106
Then the Welcome Screen's language is set to German 0.492
And the Welcome Screen's formats is set to France 0.210
When I set the language to Italian (it) 4.592
Then the language and keyboard have not been saved in cleartext storage 2.106
When I save the language and keyboard options in cleartext storage 13.746
The 
The Dogtail init script raised: SearchError: descendant of [application | Welcome to Tails!]: child with name='Question' roleName='alert'
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/common_steps.rb:509:in `/^I save the language and keyboard options in cleartext storage$/'
features/localization.feature:98:in `When I save the language and keyboard options in cleartext storage'
Then the "it" language and keyboard have been saved in cleartext storage 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# The third boot verifies that cleartext has priority
And I start Tails from USB drive "__internal" with network unplugged 0.000
Then the Welcome Screen's language is set to Italian 0.000
And the Welcome Screen's formats is set to Italy 0.000
When I enable persistence 0.000
# Only formats are loaded from persistence
Then the Welcome Screen's formats is set to France 0.000
And the Welcome Screen's language is set to Italian 0.000
After features/support/hooks.rb:335 5.069 
SCENARIO FAILED: 'Cleartext localization preferences have priority over Persistent Storage' (at time 02:02:52)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/12/artifact/build-artifacts/02:02:52_Cleartext_localization_preferences_have_priority_over_Persistent_Storage.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/12/artifact/build-artifacts/02:02:52_Cleartext_localization_preferences_have_priority_over_Persistent_Storage.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/12/artifact/build-artifacts/02:02:52_Cleartext_localization_preferences_have_priority_over_Persistent_Storage.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/12/artifact/build-artifacts/02:02:52_Cleartext_localization_preferences_have_priority_over_Persistent_Storage.journal
After features/support/hooks.rb:104 0.008
Feature: Tails persistence
Tags: @product
2:8.708
Scenario LUKS backup header is restored if something goes wrong during upgrade
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Steps
Given I have started Tails without network from a USB drive with a LUKS 1 persistent partition and stopped at Tails Greeter's login screen 7.411
And I enable persistence but something goes wrong during the LUKS header upgrade 2:1.296
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:705:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:723:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:733:in `/^I enable persistence but something goes wrong during the LUKS header upgrade$/'
features/persistence.feature:169:in `And I enable persistence but something goes wrong during the LUKS header upgrade'
Then the Tails persistence partition on USB drive "__internal" still has LUKS version 1 0.000
After features/support/hooks.rb:335 4.709 
SCENARIO FAILED: 'LUKS backup header is restored if something goes wrong during upgrade' (at time 02:29:30)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/12/artifact/build-artifacts/02:29:30_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/12/artifact/build-artifacts/02:29:30_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/12/artifact/build-artifacts/02:29:30_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/12/artifact/build-artifacts/02:29:30_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.journal
After features/support/hooks.rb:104 0.000
Feature: Shutdown buttons in the system menu
Tags: @product
38.454
Scenario I can shutdown Tails via the system menu
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 10.922
When I request a shutdown using the system menu 27.532
The 
The Dogtail init script raised: SearchError: descendant of [application | gnome-shell]: child with name='Power Off' roleName='label'
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/common_steps.rb:930:in `/^I request a (shutdown|reboot) using the system menu$/'
features/shutdown_applet.feature:6:in `When I request a shutdown using the system menu'
Then Tails eventually shuts down 0.000
After features/support/hooks.rb:335 5.290 
SCENARIO FAILED: 'I can shutdown Tails via the system menu' (at time 02:40:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/12/artifact/build-artifacts/02:40:26_I_can_shutdown_Tails_via_the_system_menu.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/12/artifact/build-artifacts/02:40:26_I_can_shutdown_Tails_via_the_system_menu.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/12/artifact/build-artifacts/02:40:26_I_can_shutdown_Tails_via_the_system_menu.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/12/artifact/build-artifacts/02:40:26_I_can_shutdown_Tails_via_the_system_menu.journal
After features/support/hooks.rb:104 0.000
Feature: Shutdown buttons in the system menu
Tags: @product @not_release_blocker
37.187
Scenario I can reboot Tails via the system menu
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Steps
Given I have started Tails from DVD and logged in and the network is connected 10.268
When I request a reboot using the system menu 26.918
The 
The Dogtail init script raised: SearchError: descendant of [application | gnome-shell]: child with name='Restart' roleName='label'
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/common_steps.rb:930:in `/^I request a (shutdown|reboot) using the system menu$/'
features/shutdown_applet.feature:12:in `When I request a reboot using the system menu'
Then Tails eventually restarts 0.000
After features/support/hooks.rb:335 5.512 
SCENARIO FAILED: 'I can reboot Tails via the system menu' (at time 02:41:09)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/12/artifact/build-artifacts/02:41:09_I_can_reboot_Tails_via_the_system_menu.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/12/artifact/build-artifacts/02:41:09_I_can_reboot_Tails_via_the_system_menu.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/12/artifact/build-artifacts/02:41:09_I_can_reboot_Tails_via_the_system_menu.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/12/artifact/build-artifacts/02:41:09_I_can_reboot_Tails_via_the_system_menu.journal
After features/support/hooks.rb:104 0.000