Project Number Date
test_Tails_ISO_devel 4629 19 Sep 2026, 11:10

Failures Overview

The following summary displays scenarios that failed.

Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
3:4.603
Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Before features/support/hooks.rb:527 0.001
Steps
Given a computer 0.075
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 1:10.613
And I configure APT to prefer an old version of cowsay 0.005
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 5.694
And I accept adding "cowsay" to Additional Software 4.079
And Additional Software is correctly configured for package "cowsay" 0.451
And I shutdown Tails and wait for the computer to power off 2.599
And I start Tails from USB drive "__internal" with network unplugged 31.902
And I enable persistence 10.521
# We need to add back this custom APT source for the Additional Software
# install step, as it was not saved in persistence
And I configure APT to prefer an old version of cowsay 0.005
# Prevent the "Warning: virtual machine detected!" notification from racing
# with the one we'll be interacting with below.
And I disable the tails-virt-notify-user.service user unit 0.044
And I log in to a new session 7.115
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been installed 10.147
And I revert the APT tweaks that made it prefer an old version of cowsay 0.038
# We remove the newest package after it has been downloaded and before
# it is installed, so that the upgrade process fails
And I prepare the Additional Software upgrade process to fail 0.034
And the network is plugged 0.025
And Tor is ready 12.509
And available upgrades have been checked 1.070
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 0.508
And I can open the Additional Software configuration window from the notification 27.160
The 
The Dogtail init script raised: SearchError: descendant of [application | gnome-shell]: child with roleName='notification'
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/additional_software_packages.rb:33:in `click_gnome_shell_notification_button'
./features/step_definitions/additional_software_packages.rb:160:in `/^I can open the Additional Software configuration window from the notification$/'
features/additional_software_packages.feature:103:in `And I can open the Additional Software configuration window from the notification'
And I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged 0.000
And I enable persistence 0.000
# We need to add back this custom APT source for the Additional Software
# install step, as it was not saved in persistence
And I configure APT to prefer an old version of cowsay 0.000
And I log in to a new session 0.000
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been installed 0.000
And I revert the APT tweaks that made it prefer an old version of cowsay 0.000
And the network is plugged 0.000
And Tor is ready 0.000
Then the Additional Software upgrade service has started 0.000
And the installed version of package "cowsay" is newer than "3.03+dfsg2-1" 0.000
After features/support/hooks.rb:535 0.031
After features/support/hooks.rb:339 5.274 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:03:33)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4629/artifact/build-artifacts/01:03:33_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_var_log_boot.log
Content of /run/live-additional-software/log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4629/artifact/build-artifacts/01:03:33_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_run_live-additional-software_log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.net/job/test_Tails_ISO_devel/4629/artifact/build-artifacts/01:03:33_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.net/job/test_Tails_ISO_devel/4629/artifact/build-artifacts/01:03:33_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.net/job/test_Tails_ISO_devel/4629/artifact/build-artifacts/01:03:33_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.net/job/test_Tails_ISO_devel/4629/artifact/build-artifacts/01:03:33_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_mount
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4629/artifact/build-artifacts/01:03:33_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4629/artifact/build-artifacts/01:03:33_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4629/artifact/build-artifacts/01:03:33_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal
After features/support/hooks.rb:108 0.010
Feature: Upgrading an old Tails USB installation
Tags: @product
1:23.436
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Steps
Given a computer 0.078
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:23.358
can 
can not find any of the patterns ["TailsGreeter.png", "PlymouthGraphicsCardFailureMessage.png"] on the screen (FindFailed)
./features/support/helpers/screen.rb:248:in `rescue in wait_any'
./features/support/helpers/screen.rb:232:in `wait_any'
./features/step_definitions/common_steps.rb:446:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:238:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:73:in `And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled'
Then all tps features from the old Tails version are active 0.000
And Tails is running from USB drive "to_upgrade" 0.000
And the boot device has safe access rights 0.000
And the expected persistent files created with the old Tails version are present in the filesystem 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:339 4.985 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:12:22)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4629/artifact/build-artifacts/01:12:22_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4629/artifact/build-artifacts/01:12:22_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4629/artifact/build-artifacts/01:12:22_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4629/artifact/build-artifacts/01:12:22_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:108 0.007
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
1:51.096
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 6.477
And I set an administration password 6.614
When I log in to a new session in Russian (ru) 25.896
Then the keyboard layout is set to "ru" 0.074
And tpsd is localized to the selected locale 0.075
Given the network is plugged 0.037
And Tor is ready 11.407
Then I successfully start the Unsafe Browser 4.556
And I kill the Unsafe Browser 5.156
Given Thunderbird is installed 20.738
When I enable the screen keyboard 0.090
Then the screen keyboard works in Tor Browser 29.970
cannot 
cannot find BrowserAddressBarComma.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:477:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:56:in `Then the screen keyboard works in Tor Browser'
features/localization.feature:33:in `Then the screen keyboard works in Tor Browser'
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 "ru" 0.000
After features/support/hooks.rb:339 5.124 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#11)' (at time 02:03:03)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4629/artifact/build-artifacts/02:03:03_Tails_is_localized_for_every_tier-1_language,_Examples___11_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4629/artifact/build-artifacts/02:03:03_Tails_is_localized_for_every_tier-1_language,_Examples___11_.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4629/artifact/build-artifacts/02:03:03_Tails_is_localized_for_every_tier-1_language,_Examples___11_.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4629/artifact/build-artifacts/02:03:03_Tails_is_localized_for_every_tier-1_language,_Examples___11_.journal
After features/support/hooks.rb:108 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:20.969
Scenario The Tor Browser cannot access the LAN
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Steps
Given I have started Tails from DVD and logged in and the network is connected 9.443
And a web server is running on the LAN 1.019
And I capture all network traffic 0.002
When I start the Tor Browser 6.966
And I open a page on the LAN web server in the Tor Browser 3.536
Then the Tor Browser shows the "Unable to connect" error 1:0.000
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:393: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:339 5.086 
SCENARIO FAILED: 'The Tor Browser cannot access the LAN' (at time 03:16:47)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4629/artifact/build-artifacts/03:16:47_The_Tor_Browser_cannot_access_the_LAN.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4629/artifact/build-artifacts/03:16:47_The_Tor_Browser_cannot_access_the_LAN.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4629/artifact/build-artifacts/03:16:47_The_Tor_Browser_cannot_access_the_LAN.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4629/artifact/build-artifacts/03:16:47_The_Tor_Browser_cannot_access_the_LAN.journal
After features/support/hooks.rb:108 0.067