Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 2 28 May 2026, 19:54

Failures Overview

The following summary displays scenarios that failed.

Feature: Hardware failures
Tags: @product
1:6.088
Scenario Outline Disk partitioning errors without a persistent partition
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Steps
Given a computer 0.063
And I set Tails to boot with options "test_partitioning_errors=fs_resize" 0.000
And I temporarily create a 7200 MiB disk named "temp" 0.013
And I plug USB drive "temp" 1.053
And I write the Tails USB image to disk "temp" 13.127
When I start Tails from USB drive "temp" with network unplugged 51.432
Then Tails is running from USB drive "temp" 0.398
<"usb"> 
<"usb"> expected but was
<"ata">. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:938:in `/^Tails is running from (.*) drive "([^"]+)"$/'
features/hardware_failure.feature:82:in `Then Tails is running from USB drive "temp"'
features/hardware_failure.feature:73:in `Then Tails is running from USB drive "temp"'
And the Greeter recommends reinstalling Tails due to partitioning errors 0.000
And the Greeter forbids starting Tails 0.000
And the Greeter forbids all settings but language 0.000
And Tails detected partitioning error fs-not-resized 0.000
After features/support/hooks.rb:335 4.731 
SCENARIO FAILED: 'Disk partitioning errors without a persistent partition, Examples (#3)' (at time 01:32:28)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/2/artifact/build-artifacts/01:32:28_Disk_partitioning_errors_without_a_persistent_partition,_Examples___3_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/2/artifact/build-artifacts/01:32:28_Disk_partitioning_errors_without_a_persistent_partition,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/2/artifact/build-artifacts/01:32:28_Disk_partitioning_errors_without_a_persistent_partition,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/2/artifact/build-artifacts/01:32:28_Disk_partitioning_errors_without_a_persistent_partition,_Examples___3_.journal
After features/support/hooks.rb:104 0.119
Feature: Shutdown buttons in the system menu
Tags: @product
36.662
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.519
When I request a shutdown using the system menu 26.143
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 4.979 
SCENARIO FAILED: 'I can shutdown Tails via the system menu' (at time 02:40:09)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/2/artifact/build-artifacts/02:40:09_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/2/artifact/build-artifacts/02:40:09_I_can_shutdown_Tails_via_the_system_menu.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/2/artifact/build-artifacts/02:40:09_I_can_shutdown_Tails_via_the_system_menu.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/2/artifact/build-artifacts/02:40:09_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.197
Scenario I can reboot Tails via the system menu
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Steps
Given I have started Tails from DVD and logged in and the network is connected 9.817
When I request a reboot using the system menu 26.380
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.464 
SCENARIO FAILED: 'I can reboot Tails via the system menu' (at time 02:40:51)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/2/artifact/build-artifacts/02:40:51_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/2/artifact/build-artifacts/02:40:51_I_can_reboot_Tails_via_the_system_menu.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/2/artifact/build-artifacts/02:40:51_I_can_reboot_Tails_via_the_system_menu.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/2/artifact/build-artifacts/02:40:51_I_can_reboot_Tails_via_the_system_menu.journal
After features/support/hooks.rb:104 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:22.027
Scenario The Tor Browser cannot access the LAN
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Steps
Given I have started Tails from DVD and logged in and the network is connected 9.658
And a web server is running on the LAN 1.024
And I capture all network traffic 0.003
When I start the Tor Browser 7.294
And I open a page on the LAN web server in the Tor Browser 4.040
Then the Tor Browser shows the "Unable to connect" error 1:0.005
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/browser.rb:383:in `/^the (Tor|Unsafe) Browser shows the "([^"]+)" error$/'
features/torified_browsing.feature:13:in `Then the Tor Browser shows the "Unable to connect" error'
And no traffic was sent to the web server on the LAN 0.000
After features/support/hooks.rb:335 5.151 
SCENARIO FAILED: 'The Tor Browser cannot access the LAN' (at time 02:52:45)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/2/artifact/build-artifacts/02:52:45_The_Tor_Browser_cannot_access_the_LAN.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/2/artifact/build-artifacts/02:52:45_The_Tor_Browser_cannot_access_the_LAN.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/2/artifact/build-artifacts/02:52:45_The_Tor_Browser_cannot_access_the_LAN.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/2/artifact/build-artifacts/02:52:45_The_Tor_Browser_cannot_access_the_LAN.journal
After features/support/hooks.rb:104 0.065