Project Number Date
test_Tails_ISO_stable 6552 02 Aug 2026, 11:43

Failures Overview

The following summary displays scenarios that failed.

Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
3:1.365
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.076
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 1:11.222
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.528
And I accept adding "cowsay" to Additional Software 4.172
And Additional Software is correctly configured for package "cowsay" 0.465
And I shutdown Tails and wait for the computer to power off 2.562
And I start Tails from USB drive "__internal" with network unplugged 32.311
And I enable persistence 10.444
# 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.036
And I log in to a new session 7.187
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been installed 10.152
And I revert the APT tweaks that made it prefer an old version of cowsay 0.033
# 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.052
And the network is plugged 0.035
And Tor is ready 10.821
And available upgrades have been checked 0.040
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 1.347
And I can open the Additional Software configuration window from the notification 24.861
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.048
After features/support/hooks.rb:339 5.444 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:01:32)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6552/artifact/build-artifacts/01:01:32_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.boum.org/job/test_Tails_ISO_stable/6552/artifact/build-artifacts/01:01:32_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.boum.org/job/test_Tails_ISO_stable/6552/artifact/build-artifacts/01:01:32_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.boum.org/job/test_Tails_ISO_stable/6552/artifact/build-artifacts/01:01:32_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.boum.org/job/test_Tails_ISO_stable/6552/artifact/build-artifacts/01:01:32_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.boum.org/job/test_Tails_ISO_stable/6552/artifact/build-artifacts/01:01:32_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.boum.org/job/test_Tails_ISO_stable/6552/artifact/build-artifacts/01:01:32_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6552/artifact/build-artifacts/01:01:32_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6552/artifact/build-artifacts/01:01:32_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: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
3:31.914
Scenario Chatting with some friend over XMPP
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Before features/support/hooks.rb:527 0.001
Steps
Given I have started Tails from DVD and logged in and the network is connected 10.430
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 10.125
Then I see Pidgin's account manager window 0.889
When I create my XMPP account 10.094
And I close Pidgin's account manager window 0.372
Then Pidgin automatically enables my XMPP account 3: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/pidgin.rb:144:in `/^Pidgin automatically enables my XMPP account$/'
features/pidgin.feature:22:in `Then Pidgin automatically enables my XMPP account'
Given my XMPP friend goes online 0.000
When I start a conversation with my friend 0.000
And I say something to my friend 0.000
Then I receive a response from my friend 0.000
After features/support/hooks.rb:535 0.031
After features/support/hooks.rb:339 4.891 
SCENARIO FAILED: 'Chatting with some friend over XMPP' (at time 02:44:22)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6552/artifact/build-artifacts/02:44:22_Chatting_with_some_friend_over_XMPP.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6552/artifact/build-artifacts/02:44:22_Chatting_with_some_friend_over_XMPP.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6552/artifact/build-artifacts/02:44:22_Chatting_with_some_friend_over_XMPP.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6552/artifact/build-artifacts/02:44:22_Chatting_with_some_friend_over_XMPP.journal
After features/support/hooks.rb:108 0.000
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
3:59.271
Scenario Using a persistent Pidgin configuration
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Before features/support/hooks.rb:527 0.001
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.275
And the network is plugged 0.040
And Tor is ready 22.291
And available upgrades have been checked 0.049
And all notifications have disappeared 7.429
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 9.910
Then I see Pidgin's account manager window 0.807
When I create my XMPP account 9.959
And I close Pidgin's account manager window 0.389
Then Pidgin automatically enables my XMPP account 3:0.116
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/pidgin.rb:144:in `/^Pidgin automatically enables my XMPP account$/'
features/pidgin.feature:39:in `Then Pidgin automatically enables my XMPP account'
When I close Pidgin 0.000
And I take note of the configured Pidgin accounts 0.000
And I shutdown Tails and wait for the computer to power off 0.000
Given a computer 0.000
And I start Tails from USB drive "__internal" and I login with persistence enabled 0.000
And Pidgin has the expected persistent accounts configured 0.000
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 0.000
Then Pidgin automatically enables my XMPP account 0.000
After features/support/hooks.rb:535 0.047
After features/support/hooks.rb:339 5.060 
SCENARIO FAILED: 'Using a persistent Pidgin configuration' (at time 02:48:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6552/artifact/build-artifacts/02:48:26_Using_a_persistent_Pidgin_configuration.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6552/artifact/build-artifacts/02:48:26_Using_a_persistent_Pidgin_configuration.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6552/artifact/build-artifacts/02:48:26_Using_a_persistent_Pidgin_configuration.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6552/artifact/build-artifacts/02:48:26_Using_a_persistent_Pidgin_configuration.journal
After features/support/hooks.rb:108 0.000