Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 1 28 May 2026, 16:34

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
25.942
Scenario Asking for bridge settings but receiving a mocked API error in Tor Connection
Steps
Given the Moat distributor responds with an API error 0.012
When I configure Tor Connection to ask for bridge settings based on my location 5.874
Then the Tor Connection Assistant reports that it failed to connect 9.415
And the Tor Connection Assistant reports the Moat API error 10.639
The 
The Dogtail init script raised: SearchError: descendant of [application | Tor Connection]: child with name='Error code: moat_api_error' 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/tor.rb:889:in `/^the Tor Connection Assistant reports the Moat API error$/'
features/tor_bridges.feature:113:in `And the Tor Connection Assistant reports the Moat API error'
After features/support/hooks.rb:335 5.417 
SCENARIO FAILED: 'Asking for bridge settings but receiving a mocked API error in Tor Connection' (at time 00:21:04)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/1/artifact/build-artifacts/00:21:04_Asking_for_bridge_settings_but_receiving_a_mocked_API_error_in_Tor_Connection.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/1/artifact/build-artifacts/00:21:04_Asking_for_bridge_settings_but_receiving_a_mocked_API_error_in_Tor_Connection.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/1/artifact/build-artifacts/00:21:04_Asking_for_bridge_settings_but_receiving_a_mocked_API_error_in_Tor_Connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/1/artifact/build-artifacts/00:21:04_Asking_for_bridge_settings_but_receiving_a_mocked_API_error_in_Tor_Connection.journal
After features/support/hooks.rb:104 0.056
Feature: Shutdown buttons in the system menu
Tags: @product
41.009
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 11.681
When I request a shutdown using the system menu 29.328
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.549 
SCENARIO FAILED: 'I can shutdown Tails via the system menu' (at time 02:49:55)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/1/artifact/build-artifacts/02:49:55_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/1/artifact/build-artifacts/02:49:55_I_can_shutdown_Tails_via_the_system_menu.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/1/artifact/build-artifacts/02:49:55_I_can_shutdown_Tails_via_the_system_menu.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/1/artifact/build-artifacts/02:49:55_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
38.957
Scenario I can reboot 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 9.994
When I request a reboot using the system menu 28.963
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.405 
SCENARIO FAILED: 'I can reboot Tails via the system menu' (at time 02:50:40)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/1/artifact/build-artifacts/02:50:40_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/1/artifact/build-artifacts/02:50:40_I_can_reboot_Tails_via_the_system_menu.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/1/artifact/build-artifacts/02:50:40_I_can_reboot_Tails_via_the_system_menu.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21373-poweroff-inhibit/1/artifact/build-artifacts/02:50:40_I_can_reboot_Tails_via_the_system_menu.journal
After features/support/hooks.rb:104 0.000