Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 5 01 Jun 2026, 19:53

Failures Overview

The following summary displays scenarios that failed.

Feature: Tails persistence
Tags: @product
2:8.338
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.053
And I enable persistence but something goes wrong during the LUKS header upgrade 2:1.285
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 5.088 
SCENARIO FAILED: 'LUKS backup header is restored if something goes wrong during upgrade' (at time 02:29:44)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/5/artifact/build-artifacts/02:29:44_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/5/artifact/build-artifacts/02:29:44_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/5/artifact/build-artifacts/02:29:44_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/5/artifact/build-artifacts/02:29:44_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
37.246
Scenario I can shutdown 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.786
When I request a shutdown using the system menu 26.459
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.415 
SCENARIO FAILED: 'I can shutdown Tails via the system menu' (at time 02:40:08)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/5/artifact/build-artifacts/02:40:08_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/5/artifact/build-artifacts/02:40:08_I_can_shutdown_Tails_via_the_system_menu.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/5/artifact/build-artifacts/02:40:08_I_can_shutdown_Tails_via_the_system_menu.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/5/artifact/build-artifacts/02:40:08_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
36.259
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 9.882
When I request a reboot using the system menu 26.377
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.351 
SCENARIO FAILED: 'I can reboot Tails via the system menu' (at time 02:40:50)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/5/artifact/build-artifacts/02:40:50_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/5/artifact/build-artifacts/02:40:50_I_can_reboot_Tails_via_the_system_menu.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/5/artifact/build-artifacts/02:40:50_I_can_reboot_Tails_via_the_system_menu.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/5/artifact/build-artifacts/02:40:50_I_can_reboot_Tails_via_the_system_menu.journal
After features/support/hooks.rb:104 0.000