Project Number Date
test_Tails_ISO_feature-trixie 32 18 Jun 2025, 09:51

Failures Overview

The following summary displays scenarios that failed.

Tags: @product
1:17.514
Scenario TCA can scan QR code after a connection failure
Steps
Given the Tor network and default bridges are blocked 6.420
When I unsuccessfully configure a direct connection in the Tor Connection Assistant 31.771
Then the Tor Connection Assistant reports that it failed to connect 0.149
And tca.conf is empty 0.666
Given I scan a QR code from the error page in Tor Connection Assistant 38.506
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/tor.rb:739:in `/^I scan a QR code from the error page in Tor Connection Assistant$/'
features/tor_bridges.feature:39:in `Given I scan a QR code from the error page in Tor Connection Assistant'
And I retry connecting to Tor 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:330 9.037

SCENARIO FAILED: 'TCA can scan QR code after a connection failure' (at time 00:39:23)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/00:39:23_TCA_can_scan_QR_code_after_a_connection_failure.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/00:39:23_TCA_can_scan_QR_code_after_a_connection_failure.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/00:39:23_TCA_can_scan_QR_code_after_a_connection_failure.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/00:39:23_TCA_can_scan_QR_code_after_a_connection_failure.journal

After features/support/hooks.rb:100 0.050
20.792
Scenario Erasure of memory freed by killed userspace processes
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD without network and logged in 12.371
And I prepare Tails for memory erasure tests 1.525
When I start a process allocating 128 MiB of memory with a known pattern 2.696
Then patterns cover at least 128 MiB in the guest's memory 4.199
99.610% of the expected size (128 MiB) has the pattern, but more than 100.000% was expected.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/erase_memory.rb:186:in `/^patterns cover at least (\d+) MiB in the guest's memory$/'
features/erase_memory.feature:17:in `Then patterns cover at least 128 MiB in the guest's memory'
Output 1

Pattern coverage: 99.610% (127 MiB out of 128 MiB reference memory)

When I kill the allocating process 0.000
Then I find very few patterns in the guest's memory after 5 seconds 0.000
After features/support/hooks.rb:330 6.561

SCENARIO FAILED: 'Erasure of memory freed by killed userspace processes' (at time 00:47:16)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/00:47:16_Erasure_of_memory_freed_by_killed_userspace_processes.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/00:47:16_Erasure_of_memory_freed_by_killed_userspace_processes.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/00:47:16_Erasure_of_memory_freed_by_killed_userspace_processes.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/00:47:16_Erasure_of_memory_freed_by_killed_userspace_processes.journal

After features/support/hooks.rb:100 0.000
Tags: @product
1:14.331
Scenario Installing Tails with Tails Installer to a pristine USB drive, without cloning the Persistent Storage
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:14.331
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:98:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_install.feature:57:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I temporarily create a 7200 MiB disk named "install" 0.000
And I plug USB drive "install" 0.000
And I install Tails to USB drive "install" by cloning 0.000
Then the running Tails is installed on USB drive "install" 0.000
And there is a random seed on USB drive "install" 0.000
And there is no persistence partition on USB drive "install" 0.000
After features/support/hooks.rb:330 7.269

SCENARIO FAILED: 'Installing Tails with Tails Installer to a pristine USB drive, without cloning the Persistent Storage' (at time 01:23:30)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/01:23:30_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive,_without_cloning_the_Persistent_Storage.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/01:23:30_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive,_without_cloning_the_Persistent_Storage.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/01:23:30_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive,_without_cloning_the_Persistent_Storage.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/01:23:30_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive,_without_cloning_the_Persistent_Storage.journal

After features/support/hooks.rb:100 0.000
Tags: @product
1:17.381
Scenario Re-installing Tails over an existing USB installation with a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
# We reach this first checkpoint only to ensure that the ' __internal' disk has reached the state (Tails installed + persistent partition set up) we need before we clone it below.
# This first part is done without Tails Installer (install from Tails USB image)
# Note: the "__internal" disk will keep its state across scenarios
# and features until one of its snapshots is restored.
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:17.381
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:98:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_install.feature:70:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I have started Tails from DVD without network and logged in 0.000
And I clone USB drive "__internal" to a temporary USB drive "install" 0.000
And I plug USB drive "install" 0.000
# This second part is done with Tails Installer, that's what this scenario is about
When I reinstall Tails to USB drive "install" by cloning 0.000
Then the running Tails is installed on USB drive "install" 0.000
And there is a random seed on USB drive "install" 0.000
And there is no persistence partition on USB drive "install" 0.000
After features/support/hooks.rb:330 6.561

SCENARIO FAILED: 'Re-installing Tails over an existing USB installation with a persistent partition' (at time 01:24:55)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/01:24:55_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/01:24:55_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/01:24:55_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/01:24:55_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.journal

After features/support/hooks.rb:100 0.000
Tags: @product @uefi
6:43.716
Scenario Booting Tails from a USB drive in UEFI mode
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Steps
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 1:4.586
And I power off the computer 2.502
And the computer is set to boot in UEFI mode 0.215
When I start Tails from USB drive "__internal" with network unplugged and I login 5:36.411
Remote shell seems to be down (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/support/helpers/vm_helper.rb:548:in `wait_until_remote_shell_is_up'
./features/step_definitions/common_steps.rb:447:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:276: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_install.feature:85:in `When I start Tails from USB drive "__internal" with network unplugged and I login'
Then Tails is running from USB drive "__internal" 0.000
And the boot device has safe access rights 0.000
And Tails has started in UEFI mode 0.000
After features/support/hooks.rb:330 14.449

SCENARIO FAILED: 'Booting Tails from a USB drive in UEFI mode' (at time 01:31:48)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/01:31:48_Booting_Tails_from_a_USB_drive_in_UEFI_mode.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/01:31:48_Booting_Tails_from_a_USB_drive_in_UEFI_mode.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/01:31:48_Booting_Tails_from_a_USB_drive_in_UEFI_mode.journal

After features/support/hooks.rb:100 0.015
Tags: @product
1:9.217
Scenario Installing Tails with GNOME Disks from a USB image
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD without network and logged in 1:9.217
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:98:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ without\ network\ and\ logged\ in$/'
features/usb_install.feature:91:in `Given I have started Tails from DVD without network and logged in'
And I plug and mount a USB drive containing a Tails USB image 0.000
And I create a 7200 MiB disk named "usbimage" 0.000
And I plug USB drive "usbimage" 0.000
And I install a Tails USB image to the 7200 MiB disk with GNOME Disks 0.000
After features/support/hooks.rb:330 8.824

SCENARIO FAILED: 'Installing Tails with GNOME Disks from a USB image' (at time 01:33:10)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/01:33:10_Installing_Tails_with_GNOME_Disks_from_a_USB_image.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/01:33:10_Installing_Tails_with_GNOME_Disks_from_a_USB_image.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/01:33:10_Installing_Tails_with_GNOME_Disks_from_a_USB_image.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/01:33:10_Installing_Tails_with_GNOME_Disks_from_a_USB_image.journal

After features/support/hooks.rb:100 0.000
Tags: @product
0.244
Scenario The system partition is updated when booting from a USB drive where a Tails USB image was copied
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given a computer 0.214
And I start Tails from USB drive "usbimage" with network unplugged and I login 0.030
Call to virStorageVolLookupByName failed: Storage volume not found: no storage vol with matching name 'usbimage' (Libvirt::RetrieveError)
./features/support/helpers/storage_helper.rb:151:in `lookup_volume_by_name'
./features/support/helpers/storage_helper.rb:151:in `disk_path'
./features/support/helpers/vm_helper.rb:337:in `plug_drive'
./features/support/helpers/vm_helper.rb:416:in `set_disk_boot'
./features/step_definitions/common_steps.rb:153:in `/^the computer is set to boot from (.+?) drive "(.+?)"$/'
./features/step_definitions/common_steps.rb:274: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_install.feature:100:in `And I start Tails from USB drive "usbimage" with network unplugged and I login'
Then Tails is running from USB drive "usbimage" 0.000
And the label of the system partition on "usbimage" is "Tails" 0.000
And the system partition on "usbimage" is an EFI system partition 0.000
And the FAT filesystem on the system partition on "usbimage" is at least 4000M large 0.000
And the UUID of the FAT filesystem on the system partition on "usbimage" was randomized 0.000
And the label of the FAT filesystem on the system partition on "usbimage" is "TAILS" 0.000
And the system partition on "usbimage" has the expected flags 0.000
Hooks
After features/support/hooks.rb:330 4.442
<false> is not true. (Test::Unit::AssertionFailedError)
./features/support/hooks.rb:455:in `block (2 levels) in <top (required)>'
./features/support/hooks.rb:450:in `each'
./features/support/hooks.rb:450:in `After'
Output 1

SCENARIO FAILED: 'The system partition is updated when booting from a USB drive where a Tails USB image was copied' (at time 01:33:19)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/01:33:19_The_system_partition_is_updated_when_booting_from_a_USB_drive_where_a_Tails_USB_image_was_copied.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/01:33:19_The_system_partition_is_updated_when_booting_from_a_USB_drive_where_a_Tails_USB_image_was_copied.mkv

After features/support/hooks.rb:100 0.000
17:18.998
Scenario I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Before features/support/hooks.rb:507 0.007
Steps
Given I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login 2:38.695
And I update APT using apt 22.847
And I install "popularity-contest" using apt 37.990
Then I am proposed to add the "popularity-contest" package to my Additional Software 31.668
When I create a persistent storage and activate the Additional Software feature 1:8.338
Then Additional Software is correctly configured for package "popularity-contest" 10.680
When I shutdown Tails and wait for the computer to power off 25.465
And I start Tails from USB drive "__internal" with network unplugged 3:0.793
And I enable persistence 1:15.135
And I log in to a new session 1:22.592
And the Additional Software installation service has started 40.652
Then I am notified that the installation succeeded 5:4.138
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/common_steps.rb:634:in `/^I see the "(.+)" notification(?: after at most (\d+) seconds)?$/'
./features/step_definitions/additional_software_packages.rb:28:in `/^I am notified that the installation succeeded$/'
features/additional_software_packages.feature:39:in `Then I am notified that the installation succeeded'
And Additional Software is correctly configured for package "popularity-contest" 0.000
And the package "popularity-contest" is installed after Additional Software has been started 0.000
After features/support/hooks.rb:515 0.041
After features/support/hooks.rb:330 11.723

SCENARIO FAILED: 'I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails' (at time 01:58:20)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/01:58:20_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/01:58:20_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/01:58:20_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.journal

After features/support/hooks.rb:100 0.069
28:1.484
Scenario The Additional Software dpkg hook notices when persistence is locked down while installing a package
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.032
Before features/support/hooks.rb:507 0.039
Steps
Given a computer 1.147
And I start Tails from USB drive "__internal" and I login with an administration password 5:24.481
And I update APT using apt 19.357
When I install "makepp" using apt 22:16.498
Tor
Tor operation failed (despite retrying 10 times) with
Timeout::Error: try_for() timeout expired
Last ignored exception was: ExecutionFailedInVM: Command failed: dpkg -s 'makepp' 2>/dev/null | grep -qs '^Status:.*installed$'
error code: 1
stdout: 
stderr: .
<false> is not true.
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/apt.rb:69:in `block in wait_for_package_installation'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/apt.rb:68:in `wait_for_package_installation'
./features/step_definitions/apt.rb:86:in `block (3 levels) in <top (required)>'
./features/step_definitions/apt.rb:82:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:211:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/apt.rb:81:in `block in <top (required)>' (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/apt.rb:81:in `/^I install "(.+)" using apt$/'
features/additional_software_packages.feature:48:in `When I install "makepp" using apt'
Then the Additional Software dpkg hook has been run for package "makepp" and notices the persistence is locked 0.000
And the package "makepp" is installed 0.000
After features/support/hooks.rb:515 0.039
After features/support/hooks.rb:330 5.267

SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 02:26:33)

Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/02:26:33_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.file_content_var_log_boot.log

Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/02:26:33_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_persistent_volume

Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/02:26:33_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_var_cache_apt

Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/02:26:33_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_var_lib_apt

Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/02:26:33_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_mount

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/02:26:33_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/02:26:33_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/02:26:33_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal

After features/support/hooks.rb:100 0.020
15:49.162
Scenario My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Before features/support/hooks.rb:507 0.011
Steps
Given a computer 0.317
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 7:19.042
When I uninstall "popularity-contest" using apt 32.773
And I accept removing "popularity-contest" from Additional Software 6.325
Then "popularity-contest" is not in the list of Additional Software 0.906
When I start Synaptic 27.432
And I update APT using Synaptic 26.562
And I install "cowsay" using Synaptic 6:55.801
Tor
Tor operation failed (despite retrying 10 times) with
Dogtail::Failure: The Dogtail init script raised: SearchError: child of [application | synaptic]: 'Find' dialog
STDOUT:

STDERR:

 (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/apt.rb:180:in `/^I install "(.+)" using Synaptic$/'
features/additional_software_packages.feature:61:in `And I install "cowsay" using Synaptic'
And I accept adding "cowsay" to Additional Software 0.000
Then Additional Software is correctly configured for package "cowsay" 0.000
When I uninstall "cowsay" using apt 0.000
And I refuse removing "cowsay" from Additional Software 0.000
Then Additional Software is correctly configured for package "cowsay" 0.000
When I start "Additional Software" via GNOME Activities Overview 0.000
And I remove "cowsay" from the list of Additional Software using Additional Software GUI 0.000
Then "cowsay" is not in the list of Additional Software 0.000
When I install "cowsay" using apt 0.000
And I refuse adding "cowsay" to Additional Software 0.000
Then "cowsay" is not in the list of Additional Software 0.000
After features/support/hooks.rb:515 0.035
After features/support/hooks.rb:330 8.225

SCENARIO FAILED: 'My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic' (at time 02:42:31)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/02:42:31_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.file_content_var_log_boot.log

Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/02:42:31_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.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_feature-trixie/32/artifact/build-artifacts/02:42:31_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_persistent_volume

Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/02:42:31_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_var_cache_apt

Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/02:42:31_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_var_lib_apt

Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/02:42:31_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_mount

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/02:42:31_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/02:42:31_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/02:42:31_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.journal

After features/support/hooks.rb:100 0.031
21:4.702
Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Before features/support/hooks.rb:507 0.007
Steps
Given a computer 0.241
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 5:39.210
And I configure APT to prefer an old version of cowsay 0.028
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 41.994
And I accept adding "cowsay" to Additional Software 18.931
And Additional Software is correctly configured for package "cowsay" 3.999
And I shutdown Tails and wait for the computer to power off 19.146
And I start Tails from USB drive "__internal" with network unplugged 3:12.523
And I enable persistence 27.731
# 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.044
# 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.112
And I log in to a new session 1:54.479
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 52.063
And I revert the APT tweaks that made it prefer an old version of cowsay 0.646
# 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.221
And the network is plugged 0.463
And Tor is ready 45.418
And available upgrades have been checked 0.642
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 6.635
And I can open the Additional Software configuration window from the notification 17.248
And I shutdown Tails and wait for the computer to power off 17.476
And I start Tails from USB drive "__internal" with network unplugged 2:44.991
And I enable persistence 33.247
# 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.067
And I log in to a new session 1:26.006
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 54.050
And I revert the APT tweaks that made it prefer an old version of cowsay 0.090
And the network is plugged 0.129
And Tor is ready 26.860
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/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:688:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:642:in `/^Tor is ready$/'
features/additional_software_packages.feature:114:in `And Tor is ready'
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:515 0.041
After features/support/hooks.rb:330 14.878

SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 03:03:49)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/03:03:49_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_feature-trixie/32/artifact/build-artifacts/03:03:49_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_feature-trixie/32/artifact/build-artifacts/03:03:49_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_feature-trixie/32/artifact/build-artifacts/03:03:49_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_feature-trixie/32/artifact/build-artifacts/03:03:49_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_feature-trixie/32/artifact/build-artifacts/03:03:49_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_feature-trixie/32/artifact/build-artifacts/03:03:49_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_feature-trixie/32/artifact/build-artifacts/03:03:49_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_feature-trixie/32/artifact/build-artifacts/03:03:49_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal

After features/support/hooks.rb:100 0.034
5:5.889
Scenario I am notified when Additional Software fails to install a package
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Before features/support/hooks.rb:507 0.006
Steps
Given a computer 0.203
And I start Tails from USB drive "__internal" with network unplugged 3:2.101
And I enable persistence 36.051
And I remove the "cowsay" deb files from the APT cache 0.100
# 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.104
And I log in to a new session 1:6.056
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 7.889
And I can open the Additional Software log file from the notification 13.380
The
The Dogtail init script raised: SearchError: descendant of [notification | ]: child with name='Show Log' roleName='button'
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:39:in `click_gnome_shell_notification_button'
./features/step_definitions/additional_software_packages.rb:166:in `/^I can open the Additional Software log file from the notification$/'
features/additional_software_packages.feature:130:in `And I can open the Additional Software log file from the notification'
And the package "cowsay" is not installed 0.000
After features/support/hooks.rb:515 0.059
After features/support/hooks.rb:330 13.453

SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 03:09:08)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/03:09:08_I_am_notified_when_Additional_Software_fails_to_install_a_package.file_content_var_log_boot.log

Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/03:09:08_I_am_notified_when_Additional_Software_fails_to_install_a_package.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_feature-trixie/32/artifact/build-artifacts/03:09:08_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_persistent_volume

Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/03:09:08_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_var_cache_apt

Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/03:09:08_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_var_lib_apt

Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/03:09:08_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_mount

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/03:09:08_I_am_notified_when_Additional_Software_fails_to_install_a_package.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/03:09:08_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/03:09:08_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal

After features/support/hooks.rb:100 0.017
23:13.721
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.698
And no SquashFS delta is installed 0.113
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.426
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.362
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.478
When the network is plugged 0.068
And Tor is ready 28.495
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:24.005
Tor
Tor operation failed (despite retrying 10 times) with
FindFailed: can not find any of the patterns ["TailsUpgraderUpgradeTo6.2~testoverlayfs.png", "TailsUpgraderFailure.png"] on the screen (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/usb.rb:1301:in `/^I am proposed to install an incremental upgrade to version (.+)$/'
features/usb_upgrade.feature:90:in `Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs'
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.2~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.2~testoverlayfs are present 0.000
And only the 6.2~testoverlayfs SquashFS delta is installed 0.000
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.3~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.000
And only the 6.3~testoverlayfs SquashFS delta is installed 0.000
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.000
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the Upgrader considers the system as up-to-date 0.000
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:330 6.436

SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 03:55:29)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/03:55:29_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/03:55:29_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/03:55:29_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/03:55:29_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal

After features/support/hooks.rb:100 0.000
23:5.151
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.003
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.314
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.114
And the signing key used by the Upgrader is outdated 0.150
But a current signing key is available on our website 0.000
When the network is plugged 0.109
And Tor is ready 23.678
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:24.780
Tor
Tor operation failed (despite retrying 10 times) with
FindFailed: can not find any of the patterns ["TailsUpgraderUpgradeTo6.2~testoverlayfs.png", "TailsUpgraderFailure.png"] on the screen (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/usb.rb:1301:in `/^I am proposed to install an incremental upgrade to version (.+)$/'
features/usb_upgrade.feature:134:in `Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs'
After features/support/hooks.rb:330 8.519

SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 04:18:42)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/04:18:42_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/04:18:42_Upgrading_a_Tails_whose_signing_key_is_outdated.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/04:18:42_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/04:18:42_Upgrading_a_Tails_whose_signing_key_is_outdated.journal

After features/support/hooks.rb:100 0.000
Tags: @product
1:34.714
Scenario Using Tails' custom backup tool to backup a newly added file
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.958
# The volume cannot be in use when GuestFs clones it, which we do below
And I shutdown Tails and wait for the computer to power off 14.832
And I clone USB drive "__internal" to a temporary USB drive "backup" 2.353
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.852
And I write a file "/live/persistence/TailsData_unlocked/new" with contents "foo" 0.048
When I start Tails' custom backup tool 5.136
Then the backup tool displays "Plug in your backup Tails USB stick" 0.447
When I plug USB drive "backup" 3.159
And I give the Persistent Storage on drive "backup" its own UUID 0.341
And I click "Retry" in the backup tool 1.478
Then the backup tool displays "Do you want to back up your Persistent Storage now?" 7.054
When I click "Back Up" in the backup tool 1.588
And I enter my persistent storage passphrase into the polkit prompt 21.461
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/common_steps.rb:825:in `deal_with_polkit_prompt'
./features/step_definitions/backup.rb:18:in `/^I enter my persistent storage passphrase into the polkit prompt$/'
features/backup.feature:21:in `And I enter my persistent storage passphrase into the polkit prompt'
Then the backup tool displays "Your Persistent Storage was backed up successfully to your backup Tails USB stick!" 0.000
# The backup tool ejects the drive, so we have to replug it
When I unplug USB drive "backup" 0.000
And I plug USB drive "backup" 0.000
Then the USB drive "backup" contains the same files as my persistent storage 0.000
After features/support/hooks.rb:330 13.648

SCENARIO FAILED: 'Using Tails' custom backup tool to backup a newly added file' (at time 04:30:33)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/04:30:33_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/04:30:33_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/04:30:33_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal

After features/support/hooks.rb:100 0.896
1:12.860
Scenario The Tails documentation launcher works when offline
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.022
Steps
Given I have started Tails from DVD without network and logged in 24.654
When I start "Tails Documentation" via GNOME Activities Overview 16.941
Then the Tor Browser has started 31.264
cannot find TorBrowserNewTabButton.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:495:in `/^the Tor Browser (?:has started|starts)$/'
features/documentation.feature:7:in `Then the Tor Browser has started'
Then "Tails - Documentation" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:330 10.913

SCENARIO FAILED: 'The Tails documentation launcher works when offline' (at time 04:34:11)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/04:34:11_The_Tails_documentation_launcher_works_when_offline.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/04:34:11_The_Tails_documentation_launcher_works_when_offline.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/04:34:11_The_Tails_documentation_launcher_works_when_offline.journal

After features/support/hooks.rb:100 0.000
1:12.723
Scenario The Tails documentation launcher works when online
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails from DVD and logged in and the network is connected 20.761
When I start "Tails Documentation" via GNOME Activities Overview 16.434
Then the Tor Browser has started 35.527
cannot find TorBrowserNewTabButton.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:495:in `/^the Tor Browser (?:has started|starts)$/'
features/documentation.feature:13:in `Then the Tor Browser has started'
Then "Tails - Documentation" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:330 12.491

SCENARIO FAILED: 'The Tails documentation launcher works when online' (at time 04:35:35)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/04:35:35_The_Tails_documentation_launcher_works_when_online.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/04:35:35_The_Tails_documentation_launcher_works_when_online.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/04:35:35_The_Tails_documentation_launcher_works_when_online.journal

After features/support/hooks.rb:100 0.000
Feature: Localization
3:27.165
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.034
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 15.483
When I log in to a new session in English (en) 1:0.479
Then the keyboard layout is set to "us" 0.127
When the network is plugged 0.068
And Tor is ready 35.600
Then I successfully start the Unsafe Browser 36.978
And I kill the Unsafe Browser 7.579
When I enable the screen keyboard 0.192
Then the screen keyboard works in Tor Browser 50.658
cannot find TorBrowserNewTabButton.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:495:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:482:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:438:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:45:in `Then the screen keyboard works in Tor Browser'
features/localization.feature:30: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 "us" 0.000
After features/support/hooks.rb:330 6.108

SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#3)' (at time 05:43:53)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/05:43:53_Tails_is_localized_for_every_tier-1_language,_Examples___3_.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/05:43:53_Tails_is_localized_for_every_tier-1_language,_Examples___3_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/05:43:53_Tails_is_localized_for_every_tier-1_language,_Examples___3_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/05:43:53_Tails_is_localized_for_every_tier-1_language,_Examples___3_.journal

After features/support/hooks.rb:100 0.000
Feature: Localization
4:16.048
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.030
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 24.372
When I log in to a new session in French (fr) 1:31.379
Then the keyboard layout is set to "fr" 0.216
When the network is plugged 0.134
And Tor is ready 40.172
Then I successfully start the Unsafe Browser 42.720
And I kill the Unsafe Browser 9.414
When I enable the screen keyboard 1.619
Then the screen keyboard works in Tor Browser 46.018
cannot find TorBrowserNewTabButton.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:495:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:482:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:438:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:46:in `Then the screen keyboard works in Tor Browser'
features/localization.feature:30: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 "fr" 0.000
After features/support/hooks.rb:330 12.667

SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#4)' (at time 05:48:16)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/05:48:16_Tails_is_localized_for_every_tier-1_language,_Examples___4_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/05:48:16_Tails_is_localized_for_every_tier-1_language,_Examples___4_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/05:48:16_Tails_is_localized_for_every_tier-1_language,_Examples___4_.journal

After features/support/hooks.rb:100 0.000
Feature: Localization
1:57.754
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.028
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 13.550
When I log in to a new session in German (de) 1:25.134
Then the keyboard layout is set to "de" 2.742
When the network is plugged 0.474
And Tor is ready 15.852
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/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:688:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:642:in `/^Tor is ready$/'
features/localization.feature:47:in `And Tor is ready'
features/localization.feature:26:in `And Tor is ready'
Then I successfully start the Unsafe Browser 0.000
And I kill the Unsafe Browser 0.000
When I enable the screen keyboard 0.000
Then the screen keyboard works in Tor Browser 0.000
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 "de" 0.000
After features/support/hooks.rb:330 6.833

SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#5)' (at time 05:50:30)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/05:50:30_Tails_is_localized_for_every_tier-1_language,_Examples___5_.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/05:50:30_Tails_is_localized_for_every_tier-1_language,_Examples___5_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/05:50:30_Tails_is_localized_for_every_tier-1_language,_Examples___5_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/05:50:30_Tails_is_localized_for_every_tier-1_language,_Examples___5_.journal

After features/support/hooks.rb:100 0.000
Feature: Localization
3:39.657
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 13.349
When I log in to a new session in Hindi (hi) 1:29.182
Then the keyboard layout is set to "in" 0.198
When the network is plugged 0.090
And Tor is ready 37.294
Then I successfully start the Unsafe Browser 25.428
And I kill the Unsafe Browser 8.246
When I enable the screen keyboard 2.024
Then the screen keyboard works in Tor Browser 43.840
cannot find TorBrowserNewTabButton.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:495:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:482:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:438:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:48:in `Then the screen keyboard works in Tor Browser'
features/localization.feature:30: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 "us" 0.000
After features/support/hooks.rb:330 7.169

SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#6)' (at time 05:54:16)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/05:54:16_Tails_is_localized_for_every_tier-1_language,_Examples___6_.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/05:54:16_Tails_is_localized_for_every_tier-1_language,_Examples___6_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/05:54:16_Tails_is_localized_for_every_tier-1_language,_Examples___6_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/05:54:16_Tails_is_localized_for_every_tier-1_language,_Examples___6_.journal

After features/support/hooks.rb:100 0.000
Feature: Localization
3:53.993
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 19.416
When I log in to a new session in Portuguese (pt) 1:20.826
Then the keyboard layout is set to "pt" 0.132
When the network is plugged 0.097
And Tor is ready 35.587
Then I successfully start the Unsafe Browser 36.215
And I kill the Unsafe Browser 7.807
When I enable the screen keyboard 1.223
Then the screen keyboard works in Tor Browser 52.687
cannot find TorBrowserNewTabButton.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:495:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:482:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:438:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:52:in `Then the screen keyboard works in Tor Browser'
features/localization.feature:30: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 "us" 0.000
After features/support/hooks.rb:330 12.667

SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#10)' (at time 06:16:37)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/06:16:37_Tails_is_localized_for_every_tier-1_language,_Examples___10_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/06:16:37_Tails_is_localized_for_every_tier-1_language,_Examples___10_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/06:16:37_Tails_is_localized_for_every_tier-1_language,_Examples___10_.journal

After features/support/hooks.rb:100 0.000
Tags: @source
3.181
Scenario All packages are up-to-date
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:532 0.000
Steps
Given I have the build manifest for the image under test 0.000
Then all packages listed in the build manifest are up-to-date 3.181
Command failed (pid 78440 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-trixie/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_feature-trixie/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_feature-trixie/tmp/tails-amd64-feature_trixie@5c002c0779+devel@f19c798ee6-20250617T2257Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_feature-trixie/tmp/tails-amd64-feature_trixie@5c002c0779+devel@f19c798ee6-20250617T2257Z.build-manifest
ERROR: linux-headers-6.12.31-amd64: the package was not found in any of the Debian suites
ERROR: linux-headers-6.12.31-common: the package was not found in any of the Debian suites
ERROR: linux-image-6.12.31-amd64: the package was not found in any of the Debian suites
ERROR: linux-kbuild-6.12.31: the package was not found in any of the Debian suites
INFO: Need to upgrade to a new APT snapshot:
  - grub-efi-amd64-signed (1+2.12+7) to Debian trixie (1+2.12+8)
  - grub2[grub-common, grub-efi-amd64-bin] (2.12-7) to Debian trixie (2.12-8)
  - grub2[grub-efi-amd64-unsigned, grub2-common, grub-efi-ia32-bin, grub-efi-ia32-unsigned, grub-efi-ia32] (2.12-7) to Debian trixie (2.12-8)
  - linux (6.12.31-1) to Debian sid (6.12.32-1)
  - linux-signed-amd64 (6.12.31-1) to Debian sid (6.12.32+1)
 (CommandFailed)
/var/lib/jenkins/workspace/test_Tails_ISO_feature-trixie/features/support/helpers/misc_helpers.rb:321:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_feature-trixie/features/support/helpers/misc_helpers.rb:314:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_feature-trixie/features/support/helpers/misc_helpers.rb:314:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_feature-trixie/features/step_definitions/needed_package_updates.rb:8:in `/^all packages listed in the build manifest are up-to-date$/'
features/needed_package_updates.feature:12:in `Then all packages listed in the build manifest are up-to-date'
After features/support/hooks.rb:539 0.000
After features/support/hooks.rb:100 0.000
Tags: @product
7:11.334
Scenario Persistent Greeter options
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 18.499
When I enable persistence 1:12.236
Then no persistent Greeter options were restored 18.590
When I set all Greeter options to non-default values 51.906
And I log in to a new session in German (de) after having activated the Persistent Storage 1:12.645
Then all Greeter options are set to non-default values 0.282
When I cold reboot the computer 17.091
And the computer reboots Tails 2:16.863
Given I enable persistence 24.691
Then persistent Greeter options were restored 0.666
When I log in to a new session after having activated the Persistent Storage 17.858
The
The Dogtail init script raised: SearchError: descendant of [application | Welcome to Tails!]: child with name='Start Tails' roleName='button'
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:516:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
features/persistence.feature:113:in `When I log in to a new session after having activated the Persistent Storage'
Then all Greeter options are set to non-default values 0.000
After features/support/hooks.rb:330 6.455

SCENARIO FAILED: 'Persistent Greeter options' (at time 07:22:34)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/07:22:34_Persistent_Greeter_options.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/07:22:34_Persistent_Greeter_options.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/07:22:34_Persistent_Greeter_options.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/07:22:34_Persistent_Greeter_options.journal

After features/support/hooks.rb:100 0.008
39.574
Scenario Chatting with some friend over XMPP in a multi-user chat
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.034
Before features/support/hooks.rb:507 0.009
Steps
Given I have started Tails from DVD and logged in and the network is connected 18.129
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.506
Then I see Pidgin's account manager window 4.281
When I create my XMPP account 5.657
cannot find PidginAddAccountProtocolXMPP.png on the screen (FindFailed)
./features/support/helpers/screen.rb:157:in `find'
./features/support/helpers/screen.rb:367:in `hover'
./features/support/helpers/screen.rb:394:in `click'
./features/step_definitions/pidgin.rb:126:in `/^I create my XMPP account$/'
features/pidgin.feature:34:in `When I create my XMPP account'
And I close Pidgin's account manager window 0.000
Then Pidgin automatically enables my XMPP account 0.000
When I join some empty multi-user chat 0.000
And I clear the multi-user chat's scrollback 0.000
And my XMPP friend goes online and joins the multi-user chat 0.000
Then I can see that my friend joined the multi-user chat 0.000
And I say something to my friend in the multi-user chat 0.000
Then I receive a response from my friend in the multi-user chat 0.000
When I say https://gitlab.tails.boum.org/tails to my friend in the multi-user chat 0.000
Then I see the Tails GitLab URL 0.000
When I wait 10 seconds 0.000
And I click on the Tails GitLab URL 0.000
Then the Tor Browser loads the Tails GitLab 0.000
After features/support/hooks.rb:515 0.036
After features/support/hooks.rb:330 6.021

SCENARIO FAILED: 'Chatting with some friend over XMPP in a multi-user chat' (at time 08:14:07)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/08:14:07_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/08:14:07_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/08:14:07_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/08:14:07_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.journal

After features/support/hooks.rb:100 0.000
34.301
Scenario Connecting to the tails multi-user chat with my XMPP account
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Before features/support/hooks.rb:507 0.007
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.373
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.026
Then I see Pidgin's account manager window 4.496
And I create my XMPP account 6.403
cannot find PidginAddAccountProtocolXMPP.png on the screen (FindFailed)
./features/support/helpers/screen.rb:157:in `find'
./features/support/helpers/screen.rb:367:in `hover'
./features/support/helpers/screen.rb:394:in `click'
./features/step_definitions/pidgin.rb:126:in `/^I create my XMPP account$/'
features/pidgin.feature:54:in `And I create my XMPP account'
And I close Pidgin's account manager window 0.000
Then Pidgin automatically enables my XMPP account 0.000
And I can join the "tails" channel on "chat.disroot.org" 0.000
After features/support/hooks.rb:515 0.042
After features/support/hooks.rb:330 5.955

SCENARIO FAILED: 'Connecting to the tails multi-user chat with my XMPP account' (at time 08:14:48)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/08:14:48_Connecting_to_the_tails_multi-user_chat_with_my_XMPP_account.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/08:14:48_Connecting_to_the_tails_multi-user_chat_with_my_XMPP_account.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/08:14:48_Connecting_to_the_tails_multi-user_chat_with_my_XMPP_account.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/08:14:48_Connecting_to_the_tails_multi-user_chat_with_my_XMPP_account.journal

After features/support/hooks.rb:100 0.000
Tags: @product
1:35.711
Scenario The live user is setup correctly
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Steps
Given I have started Tails from DVD without network and logged in 1:35.711
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:98:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ without\ network\ and\ logged\ in$/'
features/sane_defaults.feature:5:in `Given I have started Tails from DVD without network and logged in'
Then the live user has been setup by live-boot 0.000
And the live user is a member of only its own group and "cdrom dialout floppy video plugdev netdev scanner lp lpadmin users" 0.000
And the live user owns its home directory which has strict permissions 0.000
After features/support/hooks.rb:330 7.222

SCENARIO FAILED: 'The live user is setup correctly' (at time 08:35:56)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/08:35:56_The_live_user_is_setup_correctly.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/08:35:56_The_live_user_is_setup_correctly.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/08:35:56_The_live_user_is_setup_correctly.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/08:35:56_The_live_user_is_setup_correctly.journal

After features/support/hooks.rb:100 0.000
Tags: @product
1:28.199
Scenario No unexpected error messages in the journal after booting from DVD
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.054
Steps
Given I have started Tails from DVD without network and logged in 1:28.199
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:98:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ without\ network\ and\ logged\ in$/'
features/sane_defaults.feature:20:in `Given I have started Tails from DVD without network and logged in'
Then there are no unexpected messages of priority "err" or higher in the journal 0.000
After features/support/hooks.rb:330 9.670

SCENARIO FAILED: 'No unexpected error messages in the journal after booting from DVD' (at time 08:39:16)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/08:39:16_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/08:39:16_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/08:39:16_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/08:39:16_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.journal

After features/support/hooks.rb:100 0.000
3:37.329
Scenario I can reboot Tails via the system menu
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails from DVD and logged in and the network is connected 27.624
When I request a reboot using the system menu 8.782
Then Tails eventually restarts 3:0.922
try_for() timeout expired
Last ignored exception was: FindFailed: cannot find TailsGreeter.png on the screen
./features/support/helpers/screen.rb:157:in `find'
./features/step_definitions/common_steps.rb:880:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/common_steps.rb:878:in `block in <top (required)>' (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/common_steps.rb:878:in `/^Tails eventually (shuts down|restarts)$/'
features/shutdown_applet.feature:13:in `Then Tails eventually restarts'
After features/support/hooks.rb:330 16.303

SCENARIO FAILED: 'I can reboot Tails via the system menu' (at time 08:45:04)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/08:45:04_I_can_reboot_Tails_via_the_system_menu.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/08:45:04_I_can_reboot_Tails_via_the_system_menu.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/08:45:04_I_can_reboot_Tails_via_the_system_menu.journal

After features/support/hooks.rb:100 0.000
1:19.030
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Before features/support/hooks.rb:507 0.014
Steps
Given I have started Tails from DVD and logged in and the network is connected 1:19.030
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:98:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/ssh.feature:8:in `Given I have started Tails from DVD and logged in and the network is connected'
0.000
Scenario Connecting to an SSH server on the Internet works and uses the default SocksPort
Steps
Given I monitor the network connections of SSH 0.000
And I have the SSH key pair for an SSH server 0.000
When I connect to an SSH server on the Internet 0.000
Then I have sucessfully logged into the SSH server 0.000
And I see that SSH is properly stream isolated 0.000
After features/support/hooks.rb:515 0.036
After features/support/hooks.rb:330 6.585

SCENARIO FAILED: 'Connecting to an SSH server on the Internet works and uses the default SocksPort' (at time 08:46:36)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/08:46:36_Connecting_to_an_SSH_server_on_the_Internet_works_and_uses_the_default_SocksPort.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/08:46:36_Connecting_to_an_SSH_server_on_the_Internet_works_and_uses_the_default_SocksPort.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/08:46:36_Connecting_to_an_SSH_server_on_the_Internet_works_and_uses_the_default_SocksPort.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/08:46:36_Connecting_to_an_SSH_server_on_the_Internet_works_and_uses_the_default_SocksPort.journal

After features/support/hooks.rb:100 0.000
1:16.906
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Steps
Given I have started Tails from DVD without network and logged in 1:16.906
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:98:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ without\ network\ and\ logged\ in$/'
features/tor_connection.feature:7:in `Given I have started Tails from DVD without network and logged in'
0.000
Scenario Time syncing works even if the user waits a lot before connecting
Steps
When the network is plugged 0.000
And I wait 720 seconds 0.000
Then I successfully configure Tor 0.000
And the time has synced 0.000
After features/support/hooks.rb:330 6.986

SCENARIO FAILED: 'Time syncing works even if the user waits a lot before connecting' (at time 08:56:15)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/08:56:15_Time_syncing_works_even_if_the_user_waits_a_lot_before_connecting.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/08:56:15_Time_syncing_works_even_if_the_user_waits_a_lot_before_connecting.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/08:56:15_Time_syncing_works_even_if_the_user_waits_a_lot_before_connecting.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/08:56:15_Time_syncing_works_even_if_the_user_waits_a_lot_before_connecting.journal

After features/support/hooks.rb:100 0.000
1:17.434
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Steps
Given I have started Tails from DVD without network and logged in 1:17.434
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:98:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ without\ network\ and\ logged\ in$/'
features/tor_connection.feature:7:in `Given I have started Tails from DVD without network and logged in'
Tags: @product
0.000
Scenario I can use a network with captive portal
Steps
Given the Tor network and default bridges are blocked 0.000
And the network is plugged 0.000
And I make sure time sync before Tor connects indicates a captive portal 0.000
And the Tor Connection Assistant autostarts 0.000
When I choose to connect to Tor automatically 0.000
And I click "Connect to Tor" 0.000
Then the Tor Connection Assistant fails to connect to Tor 0.000
And the Tor Connection Assistant knows that it's not the time sync that failed 0.000
And the Tor Connection Assistant knows that there might be a captive portal 0.000
When I open the Unsafe Browser from Tor Connection 0.000
And I log-in to the Captive Portal 0.000
And I close the Unsafe Browser 0.000
And the Tor network and default bridges are unblocked 0.000
And I allow time sync before Tor connects to work again 0.000
And I click "Connect to Tor" 0.000
Then I wait until Tor is ready 0.000
After features/support/hooks.rb:330 7.796

SCENARIO FAILED: 'I can use a network with captive portal' (at time 08:58:36)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/08:58:36_I_can_use_a_network_with_captive_portal.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/08:58:36_I_can_use_a_network_with_captive_portal.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/08:58:36_I_can_use_a_network_with_captive_portal.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/08:58:36_I_can_use_a_network_with_captive_portal.journal

After features/support/hooks.rb:100 0.000
Tags: @product
1:17.420
Scenario Anti test: Detecting UDP leaks of DNS lookups with the firewall leak detector
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 1:17.420
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:98:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/tor_enforcement.feature:31:in `Given I have started Tails from DVD and logged in and the network is connected'
And I capture all network traffic 0.000
And I disable Tails' firewall 0.000
When I do a UDP DNS lookup of "torproject.org" 0.000
Then the firewall leak detector has detected leaks 0.000
After features/support/hooks.rb:330 6.447

SCENARIO FAILED: 'Anti test: Detecting UDP leaks of DNS lookups with the firewall leak detector' (at time 09:03:55)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/09:03:55_Anti_test:_Detecting_UDP_leaks_of_DNS_lookups_with_the_firewall_leak_detector.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/09:03:55_Anti_test:_Detecting_UDP_leaks_of_DNS_lookups_with_the_firewall_leak_detector.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/09:03:55_Anti_test:_Detecting_UDP_leaks_of_DNS_lookups_with_the_firewall_leak_detector.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/09:03:55_Anti_test:_Detecting_UDP_leaks_of_DNS_lookups_with_the_firewall_leak_detector.journal

After features/support/hooks.rb:100 0.000