Project Number Date
test_Tails_ISO_test-suite-trixie-2 5 09 Jun 2025, 11:36

Failures Overview

The following summary displays scenarios that failed.

15.391
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 8.476
And I prepare Tails for memory erasure tests 0.803
When I start a process allocating 128 MiB of memory with a known pattern 2.513
Then patterns cover at least 128 MiB in the guest's memory 3.597
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 5.583

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/00:37:57_Erasure_of_memory_freed_by_killed_userspace_processes.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/00:37:57_Erasure_of_memory_freed_by_killed_userspace_processes.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/00:37:57_Erasure_of_memory_freed_by_killed_userspace_processes.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/00:37:57_Erasure_of_memory_freed_by_killed_userspace_processes.journal

After features/support/hooks.rb:100 0.000
12:9.083
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.002
Before features/support/hooks.rb:513 0.004
Steps
Given I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login 1:25.440
And I update APT using apt 11.862
And I install "popularity-contest" using apt 26.201
Then I am proposed to add the "popularity-contest" package to my Additional Software 12.218
When I create a persistent storage and activate the Additional Software feature 29.303
Then Additional Software is correctly configured for package "popularity-contest" 2.803
When I shutdown Tails and wait for the computer to power off 12.619
And I start Tails from USB drive "__internal" with network unplugged 1:48.126
And I enable persistence 32.805
And I log in to a new session 57.252
And the Additional Software installation service has started 45.599
Then I am notified that the installation succeeded 5:4.850
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:598: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:521 0.031
After features/support/hooks.rb:330 10.575

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:27:05)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/01:27:05_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_test-suite-trixie-2/5/artifact/build-artifacts/01:27:05_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_test-suite-trixie-2/5/artifact/build-artifacts/01:27:05_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.009
25:50.448
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.002
Before features/support/hooks.rb:513 0.003
Steps
Given a computer 0.170
And I start Tails from USB drive "__internal" and I login with an administration password 3:33.025
And I update APT using apt 12.043
When I install "makepp" using apt 22:5.208
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:521 0.048
After features/support/hooks.rb:330 5.187

SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 01:53:06)

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_test-suite-trixie-2/5/artifact/build-artifacts/01:53:06_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_test-suite-trixie-2/5/artifact/build-artifacts/01:53:06_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_test-suite-trixie-2/5/artifact/build-artifacts/01:53:06_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_test-suite-trixie-2/5/artifact/build-artifacts/01:53:06_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_test-suite-trixie-2/5/artifact/build-artifacts/01:53:06_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_test-suite-trixie-2/5/artifact/build-artifacts/01:53:06_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_test-suite-trixie-2/5/artifact/build-artifacts/01:53:06_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_test-suite-trixie-2/5/artifact/build-artifacts/01:53:06_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal

After features/support/hooks.rb:100 0.010
10:27.676
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.003
Before features/support/hooks.rb:513 0.003
Steps
Given a computer 0.184
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 4:49.897
When I uninstall "popularity-contest" using apt 25.064
And I accept removing "popularity-contest" from Additional Software 2.695
Then "popularity-contest" is not in the list of Additional Software 0.716
When I start Synaptic 14.516
And I update APT using Synaptic 22.207
And I install "cowsay" using Synaptic 4:32.394
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:521 0.044
After features/support/hooks.rb:330 5.680

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:03:39)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/02:03:39_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_test-suite-trixie-2/5/artifact/build-artifacts/02:03:39_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_test-suite-trixie-2/5/artifact/build-artifacts/02:03:39_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_test-suite-trixie-2/5/artifact/build-artifacts/02:03:39_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_test-suite-trixie-2/5/artifact/build-artifacts/02:03:39_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_test-suite-trixie-2/5/artifact/build-artifacts/02:03:39_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_test-suite-trixie-2/5/artifact/build-artifacts/02:03:39_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_test-suite-trixie-2/5/artifact/build-artifacts/02:03:39_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_test-suite-trixie-2/5/artifact/build-artifacts/02:03:39_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.006
Tags: @product
2:55.109
Scenario Installing an old version of Tails to a pristine USB drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 31.282
When I start Tails from USB drive "old" with network unplugged 2:22.529
The
The Dogtail init script raised: SearchError: descendent of [application | gnome-shell]: child with roleName='notification'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/common_steps.rb:456: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_upgrade.feature:25:in `When I start Tails from USB drive "old" with network unplugged'
Then the boot device has safe access rights 0.000
And Tails is running from USB drive "old" 0.000
And there is no persistence partition on USB drive "old" 0.000
And process "udev-watchdog" is running 0.000
And udev-watchdog is monitoring the correct device 0.000
And I unplug USB drive "old" 0.000
After features/support/hooks.rb:330 6.719

SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 02:25:03)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/02:25:03_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/02:25:03_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/02:25:03_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/02:25:03_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.journal

After features/support/hooks.rb:100 0.007
Tags: @product
1:56.330
Scenario Creating a persistent partition with the old Tails USB installation
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login 1:56.141
The
The Dogtail init script raised: SearchError: descendent of [application | gnome-shell]: child with roleName='notification'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/common_steps.rb:456: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_upgrade.feature:36:in `And I start Tails from USB drive "old" with network unplugged and I login'
Then Tails is running from USB drive "old" 0.000
And I create a persistent partition 0.000
And I take note of which tps features are available 0.000
Then a Tails persistence partition exists on USB drive "old" 0.000
And I shutdown Tails and wait for the computer to power off 0.000
After features/support/hooks.rb:330 5.913

SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 02:27:06)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/02:27:06_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/02:27:06_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/02:27:06_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/02:27:06_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal

After features/support/hooks.rb:100 0.008
Tags: @product
1:49.644
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given a computer 0.242
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:49.401
The
The Dogtail init script raised: SearchError: descendent of [application | gnome-shell]: child with roleName='notification'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/common_steps.rb:456: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_upgrade.feature:46:in `And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled'
Then Tails is running from USB drive "old" 0.000
And all tps features are active 0.000
When I write some files expected to persist 0.000
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.000
And all persistence configuration files have safe access rights 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
And I take note of which tps features are available 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 0.000
After features/support/hooks.rb:330 5.782

SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:29:01)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/02:29:01_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/02:29:01_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/02:29:01_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/02:29:01_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal

After features/support/hooks.rb:100 0.006
Tags: @product
2:12.457
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given a computer 0.697
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.759
The
The Dogtail init script raised: SearchError: descendant of [application | Welcome to Tails!]: child with roleName='password text'
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/usb.rb:671:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:703:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:283:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:73:in `And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled'
Then all tps features from the old Tails version are active 0.000
And Tails is running from USB drive "to_upgrade" 0.000
And the boot device has safe access rights 0.000
And the expected persistent files created with the old Tails version are present in the filesystem 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:330 5.819

SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:34:21)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/02:34:21_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/02:34:21_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/02:34:21_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/02:34:21_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal

After features/support/hooks.rb:100 0.006
22:58.503
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.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.386
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.422
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.686
When the network is plugged 0.067
And Tor is ready 30.866
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:11.589
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 5.769

SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:57:25)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/02:57:25_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_test-suite-trixie-2/5/artifact/build-artifacts/02:57:25_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/02:57:25_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/02:57:25_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal

After features/support/hooks.rb:100 0.000
22:53.312
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.510
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.089
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 26.500
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:13.026
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 5.862

SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 03:20:24)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/03:20:24_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/03:20:24_Upgrading_a_Tails_whose_signing_key_is_outdated.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/03:20:24_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/03:20:24_Upgrading_a_Tails_whose_signing_key_is_outdated.journal

After features/support/hooks.rb:100 0.000
Tags: @product
1:17.435
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.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.291
# 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 11.821
And I clone USB drive "__internal" to a temporary USB drive "backup" 2.242
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.718
And I write a file "/live/persistence/TailsData_unlocked/new" with contents "foo" 0.055
When I start Tails' custom backup tool 6.090
Then the backup tool displays "Plug in your backup Tails USB stick" 0.377
When I plug USB drive "backup" 2.855
And I give the Persistent Storage on drive "backup" its own UUID 0.353
And I click "Retry" in the backup tool 1.420
Then the backup tool displays "Do you want to back up your Persistent Storage now?" 0.909
When I click "Back Up" in the backup tool 1.216
And I enter my persistent storage passphrase into the polkit prompt 21.084
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:789: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 9.081

SCENARIO FAILED: 'Using Tails' custom backup tool to backup a newly added file' (at time 03:29:56)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/03:29:56_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/03:29:56_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/03:29:56_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/03:29:56_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal

After features/support/hooks.rb:100 0.156
Tags: @product
0.107
Scenario Getting a DHCP lease with the default NetworkManager connection
Steps
Then the hostname should not have been leaked on the network 0.107
Hostname leak detected (DhcpLeakError)
./features/step_definitions/dhcp.rb:15:in `/^the hostname should not have been leaked on the network$/'
features/dhcp.feature:17:in `Then the hostname should not have been leaked on the network'
After features/support/hooks.rb:330 5.588

SCENARIO FAILED: 'Getting a DHCP lease with the default NetworkManager connection' (at time 03:30:52)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/03:30:52_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.file_content_var_log_boot.log

Network capture: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/03:30:52_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.pcap

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/03:30:52_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/03:30:52_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/03:30:52_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.journal

After features/support/hooks.rb:100 0.052
Tags: @product
1.051
Scenario Getting a DHCP lease with a manually configured NetworkManager connection
Steps
When I add a wired DHCP NetworkManager connection called "manually-added-con" 0.384
And I switch to the "manually-added-con" NetworkManager connection 0.516
Then the hostname should not have been leaked on the network 0.151
Hostname leak detected (DhcpLeakError)
./features/step_definitions/dhcp.rb:15:in `/^the hostname should not have been leaked on the network$/'
features/dhcp.feature:22:in `Then the hostname should not have been leaked on the network'
After features/support/hooks.rb:330 5.329

SCENARIO FAILED: 'Getting a DHCP lease with a manually configured NetworkManager connection' (at time 03:31:35)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/03:31:35_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.file_content_var_log_boot.log

Network capture: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/03:31:35_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.pcap

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/03:31:35_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/03:31:35_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/03:31:35_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.journal

After features/support/hooks.rb:100 0.042
Tags: @product
2:56.111
Scenario Outline GPT backup corruption with a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 15.381
And I corrupt the boot device's GPT backup header 1.109
And I power off the computer 0.345
When I start the computer 1.116
Then the computer boots Tails 1:54.477
When I log in to a new session 28.119
And all notifications have disappeared 15.299
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.263
<nil> was expected to not be nil. (Test::Unit::AssertionFailedError)
./features/step_definitions/hardware.rb:84:in `/^I am recommended to migrate to a new USB stick due to partitioning errors$/'
features/hardware_failure.feature:45:in `Then I am recommended to migrate to a new USB stick due to partitioning errors'
features/hardware_failure.feature:41:in `Then I am recommended to migrate to a new USB stick due to partitioning errors'
And Tails detected partitioning error partitioning-corruption 0.000
After features/support/hooks.rb:330 6.702

SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#1)' (at time 03:49:16)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/03:49:16_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/03:49:16_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/03:49:16_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/03:49:16_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.journal

After features/support/hooks.rb:100 0.008
Tags: @product
3:3.205
Scenario Outline GPT backup corruption with a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 13.498
And I corrupt the boot device's GPT backup partition table 0.665
And I power off the computer 0.341
When I start the computer 1.044
Then the computer boots Tails 1:55.331
When I log in to a new session 35.822
And all notifications have disappeared 16.154
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.347
<nil> was expected to not be nil. (Test::Unit::AssertionFailedError)
./features/step_definitions/hardware.rb:84:in `/^I am recommended to migrate to a new USB stick due to partitioning errors$/'
features/hardware_failure.feature:46:in `Then I am recommended to migrate to a new USB stick due to partitioning errors'
features/hardware_failure.feature:41:in `Then I am recommended to migrate to a new USB stick due to partitioning errors'
And Tails detected partitioning error partitioning-corruption 0.000
After features/support/hooks.rb:330 6.231

SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#2)' (at time 03:52:26)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/03:52:26_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/03:52:26_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/03:52:26_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/03:52:26_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.journal

After features/support/hooks.rb:100 0.014
Tags: @product
4:8.252
Scenario GPT backup corruption without a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given a computer 0.207
And I set Tails to boot with options "test_gpt_corruption=gpt_backup,gpt_backup_table" 0.000
And I temporarily create a 7200 MiB disk named "temp" 0.049
And I plug USB drive "temp" 1.061
And I write the Tails USB image to disk "temp" 36.897
When I start Tails from USB drive "temp" with network unplugged 2:41.074
Then Tails is running from USB drive "temp" 0.492
And the Greeter forbids creating a persistent partition 0.169
When I log in to a new session 33.425
And all notifications have disappeared 14.618
Then I am recommended to reinstall Tails due to partitioning errors 0.255
<"OK"> was expected to include
<"Creation of Persistent Storage has been disabled">. (Test::Unit::AssertionFailedError)
./features/step_definitions/hardware.rb:94:in `/^I am recommended to reinstall Tails due to partitioning errors$/'
features/hardware_failure.feature:59:in `Then I am recommended to reinstall Tails due to partitioning errors'
# We are gonna verify the dialog again so we need to clean up the
# first instance.
And I close the "zenity" window 0.000
And I am told that Persistent Storage cannot be created 0.000
And Tails detected partitioning error partitioning-corruption 0.000
After features/support/hooks.rb:330 6.464

SCENARIO FAILED: 'GPT backup corruption without a persistent partition' (at time 03:56:40)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/03:56:40_GPT_backup_corruption_without_a_persistent_partition.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/03:56:40_GPT_backup_corruption_without_a_persistent_partition.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/03:56:40_GPT_backup_corruption_without_a_persistent_partition.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/03:56:40_GPT_backup_corruption_without_a_persistent_partition.journal

After features/support/hooks.rb:100 0.113
Tags: @product
9.206
Scenario The included APT repository keys are up-to-date
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 9.124
Then the keys trusted by APT are valid for the next 3 months 0.082
Command failed: apt-key adv --batch --with-colons --fingerprint --list-key
error code: 127
stdout: 
stderr: /bin/sh: 1: apt-key: not found
.
<false> is not true. (ExecutionFailedInVM)
./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/checks.rb:19:in `assert_all_keys_are_valid_for_n_months'
./features/step_definitions/checks.rb:8:in `/^the keys trusted by APT are valid for the next (\d+) months$/'
features/keys.feature:11:in `Then the keys trusted by APT are valid for the next 3 months'
After features/support/hooks.rb:330 5.439

SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 04:07:20)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/04:07:20_The_included_APT_repository_keys_are_up-to-date.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/04:07:20_The_included_APT_repository_keys_are_up-to-date.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/04:07:20_The_included_APT_repository_keys_are_up-to-date.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/04:07:20_The_included_APT_repository_keys_are_up-to-date.journal

After features/support/hooks.rb:100 0.000
Feature: Localization
2:17.330
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 8.546
When I log in to a new session in Italian (it) 50.515
Then the keyboard layout is set to "it" 0.357
When the network is plugged 0.133
And Tor is ready 21.212
Then I successfully start the Unsafe Browser 17.214
And I kill the Unsafe Browser 8.754
When I enable the screen keyboard 0.239
Then the screen keyboard works in Tor Browser 30.356
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:1043:in `launch_app'
./features/step_definitions/common_steps.rb:1098:in `launch_tor_browser'
./features/step_definitions/browser.rb:474:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:440:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:50: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 11.006

SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#8)' (at time 04:40:24)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/04:40:24_Tails_is_localized_for_every_tier-1_language,_Examples___8_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/04:40:24_Tails_is_localized_for_every_tier-1_language,_Examples___8_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/04:40:24_Tails_is_localized_for_every_tier-1_language,_Examples___8_.journal

After features/support/hooks.rb:100 0.000
Feature: Localization
2:43.603
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 8.097
When I log in to a new session in Persian (fa) 47.835
Then the keyboard layout is set to "ir" 0.512
When the network is plugged 0.128
And Tor is ready 52.883
Then I successfully start the Unsafe Browser 16.326
And I kill the Unsafe Browser 7.279
When I enable the screen keyboard 0.186
Then the screen keyboard works in Tor Browser 30.353
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:1043:in `launch_app'
./features/step_definitions/common_steps.rb:1098:in `launch_tor_browser'
./features/step_definitions/browser.rb:474:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:440:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:51: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 "ir" 0.000
After features/support/hooks.rb:330 10.576

SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#9)' (at time 04:43:19)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/04:43:19_Tails_is_localized_for_every_tier-1_language,_Examples___9_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/04:43:19_Tails_is_localized_for_every_tier-1_language,_Examples___9_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/04:43:19_Tails_is_localized_for_every_tier-1_language,_Examples___9_.journal

After features/support/hooks.rb:100 0.000
Feature: Localization
2:13.509
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.005
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.301
When I log in to a new session in Turkish (tr) 47.738
Then the keyboard layout is set to "tr" 0.454
When the network is plugged 0.092
And Tor is ready 19.554
Then I successfully start the Unsafe Browser 19.167
And I kill the Unsafe Browser 7.283
When I enable the screen keyboard 0.321
Then the screen keyboard works in Tor Browser 30.593
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:1043:in `launch_app'
./features/step_definitions/common_steps.rb:1098:in `launch_tor_browser'
./features/step_definitions/browser.rb:474:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:440:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:55: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 10.706

SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#13)' (at time 04:55:50)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/04:55:50_Tails_is_localized_for_every_tier-1_language,_Examples___13_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/04:55:50_Tails_is_localized_for_every_tier-1_language,_Examples___13_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/04:55:50_Tails_is_localized_for_every_tier-1_language,_Examples___13_.journal

After features/support/hooks.rb:100 0.000
48.589
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 10.451
And I create a persistent partition with the default settings 22.168
Then the "TorConfiguration" tps feature is not enabled 2.451
When the network is plugged 0.081
And the Tor Connection Assistant autostarts 7.890
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 5.544
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:826:in `click_connect_to_tor'
./features/step_definitions/tor.rb:635:in `block (2 levels) in <top (required)>'
./features/step_definitions/tor.rb:499:in `tca_configure'
./features/step_definitions/tor.rb:626:in `/^I configure (?:some|the) (persistent )?(\w+) bridges (from a QR code )?in the Tor Connection Assistant(?: in (easy|hide) mode)?( without connecting|)$/'
features/persistent_tor_bridges.feature:13:in `And I configure some persistent obfs4 bridges in the Tor Connection Assistant'
And I wait until Tor is ready 0.000
Then tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 0.000
When I cold reboot the computer 0.000
And the computer reboots Tails 0.000
And I enable persistence 0.000
And I capture all network traffic 0.000
And I log in to a new session 0.000
Then tca.conf includes the configured bridges 0.000
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
Tags: @product
0.000
Scenario Disabling persistence of Tor bridges
Steps
When I choose to connect to Tor automatically 0.000
And I accept Tor Connection's offer to use my persistent bridges 0.000
And I disable saving bridges to Persistent Storage 0.000
And I configure a direct connection in the Tor Connection Assistant 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes no bridge 0.000
And the "TorConfiguration" tps feature is not enabled and not active 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:330 5.554

SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 06:09:47)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/06:09:47_Disabling_persistence_of_Tor_bridges.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/06:09:47_Disabling_persistence_of_Tor_bridges.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/06:09:47_Disabling_persistence_of_Tor_bridges.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/06:09:47_Disabling_persistence_of_Tor_bridges.journal

After features/support/hooks.rb:100 0.000
Tags: @product
10.964
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.003
Steps
Given I have started Tails from DVD without network and logged in 10.781
Then there are no unexpected messages of priority "err" or higher in the journal 0.183
Unexpected error messages in the journal: [
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:18 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "574",
    "_BOOT_ID": "f219173c00044274a3b35b9130741071",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "574",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749443155479365",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "195635d7eaee4c0c8bf1e6e1dad2f50d",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=dfb818e1dc174a058f9a32e33b6b58aa;i=352;b=f219173c00044274a3b35b9130741071;m=b7a2b6;t=6371bf9d64b9d;x=b31744f3a2aaa32a",
    "__MONOTONIC_TIMESTAMP": "12034742",
    "__REALTIME_TIMESTAMP": "1749443155479453",
    "__SEQNUM": "850",
    "__SEQNUM_ID": "dfb818e1dc174a058f9a32e33b6b58aa"
  },
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:22 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "574",
    "_BOOT_ID": "f219173c00044274a3b35b9130741071",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "574",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749443155479390",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "195635d7eaee4c0c8bf1e6e1dad2f50d",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=dfb818e1dc174a058f9a32e33b6b58aa;i=354;b=f219173c00044274a3b35b9130741071;m=b7a352;t=6371bf9d64c38;x=8a69f67f7a919487",
    "__MONOTONIC_TIMESTAMP": "12034898",
    "__REALTIME_TIMESTAMP": "1749443155479608",
    "__SEQNUM": "852",
    "__SEQNUM_ID": "dfb818e1dc174a058f9a32e33b6b58aa"
  },
  {
    "MESSAGE": "The group `powerdev' does not exist.",
    "SYSLOG_IDENTIFIER": "adduser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "2299",
    "SYSLOG_TIMESTAMP": "Jun  9 04:26:04 ",
    "_BOOT_ID": "f219173c00044274a3b35b9130741071",
    "_CAP_EFFECTIVE": "1ffffffffff",
    "_CMDLINE": "adduser",
    "_COMM": "adduser",
    "_EXE": "/usr/bin/perl",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "2299",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749443164503175",
    "_SYSTEMD_CGROUP": "/system.slice/live-config.service",
    "_SYSTEMD_INVOCATION_ID": "908faca8921b403b9319cddd09574708",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "live-config.service",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=dfb818e1dc174a058f9a32e33b6b58aa;i=3f7;b=f219173c00044274a3b35b9130741071;m=14153d8;t=6371bfa5ffcbf;x=3b2284ede0c7f4ab",
    "__MONOTONIC_TIMESTAMP": "21058520",
    "__REALTIME_TIMESTAMP": "1749443164503231",
    "__SEQNUM": "1015",
    "__SEQNUM_ID": "dfb818e1dc174a058f9a32e33b6b58aa"
  },
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:18 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "574",
    "_BOOT_ID": "f219173c00044274a3b35b9130741071",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "574",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749443342657298",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "195635d7eaee4c0c8bf1e6e1dad2f50d",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=dfb818e1dc174a058f9a32e33b6b58aa;i=8ab;b=f219173c00044274a3b35b9130741071;m=6249020;t=6371c04fe6765;x=aee6fdcec55e6add",
    "__MONOTONIC_TIMESTAMP": "103059488",
    "__REALTIME_TIMESTAMP": "1749443342657381",
    "__SEQNUM": "2219",
    "__SEQNUM_ID": "dfb818e1dc174a058f9a32e33b6b58aa"
  },
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:22 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "574",
    "_BOOT_ID": "f219173c00044274a3b35b9130741071",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "574",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749443342657324",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "195635d7eaee4c0c8bf1e6e1dad2f50d",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=dfb818e1dc174a058f9a32e33b6b58aa;i=8ad;b=f219173c00044274a3b35b9130741071;m=62491e8;t=6371c04fe692d;x=b242f50d348b4811",
    "__MONOTONIC_TIMESTAMP": "103059944",
    "__REALTIME_TIMESTAMP": "1749443342657837",
    "__SEQNUM": "2221",
    "__SEQNUM_ID": "dfb818e1dc174a058f9a32e33b6b58aa"
  },
  {
    "MESSAGE": "The user `amnesia' is not a member of group `sudo'.",
    "SYSLOG_IDENTIFIER": "deluser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "7262",
    "SYSLOG_TIMESTAMP": "Jun  9 04:29:08 ",
    "_AUDIT_LOGINUID": "1000",
    "_AUDIT_SESSION": "4",
    "_BOOT_ID": "f219173c00044274a3b35b9130741071",
    "_CAP_EFFECTIVE": "1ffffffffff",
    "_COMM": "deluser",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "7262",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749443348163891",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=dfb818e1dc174a058f9a32e33b6b58aa;i=1223;b=f219173c00044274a3b35b9130741071;m=678a723;t=6371c05527e69;x=47e4c556211ef31d",
    "__MONOTONIC_TIMESTAMP": "108570403",
    "__REALTIME_TIMESTAMP": "1749443348168297",
    "__SEQNUM": "4643",
    "__SEQNUM_ID": "dfb818e1dc174a058f9a32e33b6b58aa"
  }
].
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/checks.rb:237:in `/^there are no unexpected messages of priority "err" or higher in the journal$/'
features/sane_defaults.feature:21:in `Then there are no unexpected messages of priority "err" or higher in the journal'
After features/support/hooks.rb:330 5.555

SCENARIO FAILED: 'No unexpected error messages in the journal after booting from DVD' (at time 06:15:11)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/06:15:11_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_test-suite-trixie-2/5/artifact/build-artifacts/06:15:11_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/06:15:11_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/06:15:11_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.journal

After features/support/hooks.rb:100 0.000
Tags: @product
13.395
Scenario No unexpected error messages in the journal after booting from USB drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.194
Then there are no unexpected messages of priority "err" or higher in the journal 0.201
Unexpected error messages in the journal: [
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:18 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "708",
    "_BOOT_ID": "73de203d02b84b318c1e80c9b48b0055",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "708",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749445298063269",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "136ca395b04c43ae831ce98a944c6ab4",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=7e0578076f00434f906fd27a0f555b50;i=387;b=73de203d02b84b318c1e80c9b48b0055;m=f0ac5f;t=6371c798bf2e8;x=748248ffecdcbb16",
    "__MONOTONIC_TIMESTAMP": "15772767",
    "__REALTIME_TIMESTAMP": "1749445298090728",
    "__SEQNUM": "903",
    "__SEQNUM_ID": "7e0578076f00434f906fd27a0f555b50"
  },
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:22 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "708",
    "_BOOT_ID": "73de203d02b84b318c1e80c9b48b0055",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "708",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749445298063295",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "136ca395b04c43ae831ce98a944c6ab4",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=7e0578076f00434f906fd27a0f555b50;i=389;b=73de203d02b84b318c1e80c9b48b0055;m=f0adbd;t=6371c798bf446;x=684007a7f9f820e7",
    "__MONOTONIC_TIMESTAMP": "15773117",
    "__REALTIME_TIMESTAMP": "1749445298091078",
    "__SEQNUM": "905",
    "__SEQNUM_ID": "7e0578076f00434f906fd27a0f555b50"
  },
  {
    "MESSAGE": "The group `powerdev' does not exist.",
    "SYSLOG_IDENTIFIER": "adduser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "2299",
    "SYSLOG_TIMESTAMP": "Jun  9 05:01:45 ",
    "_BOOT_ID": "73de203d02b84b318c1e80c9b48b0055",
    "_CAP_EFFECTIVE": "1ffffffffff",
    "_CMDLINE": "adduser",
    "_COMM": "adduser",
    "_EXE": "/usr/bin/perl",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "2299",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749445305355036",
    "_SYSTEMD_CGROUP": "/system.slice/live-config.service",
    "_SYSTEMD_INVOCATION_ID": "6b48ede165164606a5faab4982e7768c",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "live-config.service",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=7e0578076f00434f906fd27a0f555b50;i=41a;b=73de203d02b84b318c1e80c9b48b0055;m=15f84a3;t=6371c79facb2b;x=bf3f692a499e2ddf",
    "__MONOTONIC_TIMESTAMP": "23037091",
    "__REALTIME_TIMESTAMP": "1749445305355051",
    "__SEQNUM": "1050",
    "__SEQNUM_ID": "7e0578076f00434f906fd27a0f555b50"
  },
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:18 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "708",
    "_BOOT_ID": "73de203d02b84b318c1e80c9b48b0055",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "708",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749445437945895",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "136ca395b04c43ae831ce98a944c6ab4",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=7e0578076f00434f906fd27a0f555b50;i=e6c;b=73de203d02b84b318c1e80c9b48b0055;m=903ab53;t=6371c81e1f879;x=d4da7e573b24c56b",
    "__MONOTONIC_TIMESTAMP": "151235411",
    "__REALTIME_TIMESTAMP": "1749445437945977",
    "__SEQNUM": "3692",
    "__SEQNUM_ID": "7e0578076f00434f906fd27a0f555b50"
  },
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:22 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "708",
    "_BOOT_ID": "73de203d02b84b318c1e80c9b48b0055",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "708",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749445437945923",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "136ca395b04c43ae831ce98a944c6ab4",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=7e0578076f00434f906fd27a0f555b50;i=e6e;b=73de203d02b84b318c1e80c9b48b0055;m=903acf5;t=6371c81e1fa1c;x=bcea2c548d4d6293",
    "__MONOTONIC_TIMESTAMP": "151235829",
    "__REALTIME_TIMESTAMP": "1749445437946396",
    "__SEQNUM": "3694",
    "__SEQNUM_ID": "7e0578076f00434f906fd27a0f555b50"
  },
  {
    "MESSAGE": "The user `amnesia' is not a member of group `sudo'.",
    "SYSLOG_IDENTIFIER": "deluser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "12691",
    "SYSLOG_TIMESTAMP": "Jun  9 05:04:05 ",
    "_AUDIT_LOGINUID": "1000",
    "_AUDIT_SESSION": "4",
    "_BOOT_ID": "73de203d02b84b318c1e80c9b48b0055",
    "_CAP_EFFECTIVE": "1ffffffffff",
    "_CMDLINE": "/usr/bin/perl -T /usr/sbin/deluser amnesia sudo",
    "_COMM": "deluser",
    "_EXE": "/usr/bin/perl",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "12691",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749445445433057",
    "_SYSTEMD_CGROUP": "/user.slice/user-1000.slice/session-4.scope",
    "_SYSTEMD_INVOCATION_ID": "91aa7d26089b4ad19ebd70c46a953872",
    "_SYSTEMD_OWNER_UID": "1000",
    "_SYSTEMD_SESSION": "4",
    "_SYSTEMD_SLICE": "user-1000.slice",
    "_SYSTEMD_UNIT": "session-4.scope",
    "_SYSTEMD_USER_SLICE": "-.slice",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=7e0578076f00434f906fd27a0f555b50;i=1875;b=73de203d02b84b318c1e80c9b48b0055;m=975e9c8;t=6371c825436ee;x=1194879e8737bd2c",
    "__MONOTONIC_TIMESTAMP": "158722504",
    "__REALTIME_TIMESTAMP": "1749445445433070",
    "__SEQNUM": "6261",
    "__SEQNUM_ID": "7e0578076f00434f906fd27a0f555b50"
  }
].
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/checks.rb:237:in `/^there are no unexpected messages of priority "err" or higher in the journal$/'
features/sane_defaults.feature:25:in `Then there are no unexpected messages of priority "err" or higher in the journal'
After features/support/hooks.rb:330 5.476

SCENARIO FAILED: 'No unexpected error messages in the journal after booting from USB drive' (at time 06:15:29)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/06:15:29_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/06:15:29_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/06:15:29_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/06:15:29_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.journal

After features/support/hooks.rb:100 0.000
Tags: @product
27.382
Scenario I can shutdown Tails via the system menu
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 13.096
When I request a shutdown using the system menu 14.285
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/support/helpers/dogtail.rb:371:in `grabFocus'
./features/step_definitions/common_steps.rb:890:in `/^I request a (shutdown|reboot) using the system menu$/'
features/shutdown_applet.feature:6:in `When I request a shutdown using the system menu'
Then Tails eventually shuts down 0.000
After features/support/hooks.rb:330 5.849

SCENARIO FAILED: 'I can shutdown Tails via the system menu' (at time 06:16:02)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/06:16:02_I_can_shutdown_Tails_via_the_system_menu.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/06:16:02_I_can_shutdown_Tails_via_the_system_menu.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/06:16:02_I_can_shutdown_Tails_via_the_system_menu.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/06:16:02_I_can_shutdown_Tails_via_the_system_menu.journal

After features/support/hooks.rb:100 0.000
26.564
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 12.487
When I request a reboot using the system menu 14.077
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/support/helpers/dogtail.rb:371:in `grabFocus'
./features/step_definitions/common_steps.rb:890:in `/^I request a (shutdown|reboot) using the system menu$/'
features/shutdown_applet.feature:12:in `When I request a reboot using the system menu'
Then Tails eventually restarts 0.000
After features/support/hooks.rb:330 5.601

SCENARIO FAILED: 'I can reboot Tails via the system menu' (at time 06:16:35)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/06:16:35_I_can_reboot_Tails_via_the_system_menu.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/06:16:35_I_can_reboot_Tails_via_the_system_menu.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/06:16:35_I_can_reboot_Tails_via_the_system_menu.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/06:16:35_I_can_reboot_Tails_via_the_system_menu.journal

After features/support/hooks.rb:100 0.000
2:8.190
Scenario I can send emails, and receive emails over IMAP
Steps
When I enter my email credentials into the autoconfiguration wizard 2:8.190
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/thunderbird.rb:106:in `/^I enter my email credentials into the autoconfiguration wizard$/'
features/thunderbird.feature:19:in `When I enter my email credentials into the autoconfiguration wizard'
Then the autoconfiguration wizard's choice for the incoming server is secure IMAP 0.000
And the autoconfiguration wizard's choice for the outgoing server is secure SMTP 0.000
When I accept the autoconfiguration wizard's configuration 0.000
And I send an email to myself 0.000
And I fetch my email 0.000
Then I can find the email I sent to myself in my inbox 0.000
After features/support/hooks.rb:521 0.034
After features/support/hooks.rb:330 7.073

SCENARIO FAILED: 'I can send emails, and receive emails over IMAP' (at time 06:21:18)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/06:21:18_I_can_send_emails,_and_receive_emails_over_IMAP.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/06:21:18_I_can_send_emails,_and_receive_emails_over_IMAP.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/06:21:18_I_can_send_emails,_and_receive_emails_over_IMAP.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/06:21:18_I_can_send_emails,_and_receive_emails_over_IMAP.journal

After features/support/hooks.rb:100 0.000
Tags: @product
4:49.202
Scenario Persistent browser bookmarks
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.977
And all tps features are active 2.437
And all persistent filesystems have safe access rights 0.672
And all persistence configuration files have safe access rights 0.859
And all persistent directories have safe access rights 3.053
When I start the Tor Browser in offline mode 40.015
And I add a bookmark to eff.org in the Tor Browser 12.547
And I cold reboot the computer 16.562
And the computer reboots Tails 2:1.310
And I enable persistence 18.796
And I log in to a new session 35.699
And all notifications have disappeared 26.270
The
The Dogtail init script raised: DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
STDOUT:

STDERR:
Exception ignored in: <function Ponytail.__del__ at 0x7dccf2709260>
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/ponytail/ponytail.py", line 51, in __del__
    if (self.connected):
AttributeError: 'Ponytail' object has no attribute 'connected'

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:85:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:718:in `new'
./features/step_definitions/common_steps.rb:718:in `/^all notifications have disappeared$/'
features/torified_browsing.feature:145:in `And all notifications have disappeared'
And I start the Tor Browser in offline mode 0.000
Then the Tor Browser has a bookmark to eff.org 0.000
After features/support/hooks.rb:330 5.633

SCENARIO FAILED: 'Persistent browser bookmarks' (at time 06:59:21)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/06:59:21_Persistent_browser_bookmarks.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/06:59:21_Persistent_browser_bookmarks.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/06:59:21_Persistent_browser_bookmarks.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/06:59:21_Persistent_browser_bookmarks.journal

After features/support/hooks.rb:100 0.009
Tags: @product @doc
1:3.077
Scenario Starting the Unsafe Browser works as it should
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 12.272
When I successfully start the Unsafe Browser 21.296
Then the Unsafe Browser runs as the expected user 2.457
And the Unsafe Browser has a red theme 0.572
And the Unsafe Browser shows a warning as its start page 0.593
And the Unsafe Browser has no add-ons installed 8.897
And the Unsafe Browser has no bookmarks 15.446
And the Unsafe Browser uses all expected TBB shared libraries 1.540
The
The loaded shared libraries for the firefox process are not the way we expect them.
Expected TBB libs that are absent: ["libfreeblpriv3.so", "libgkcodecs.so", "liblgpllibs.so", "libmozgtk.so", "libmozsandbox.so", "libmozsqlite3.so", "libmozwayland.so", "libnspr4.so", "libnss3.so", "libnssckbi.so", "libnssutil3.so", "libplc4.so", "libplds4.so", "libsmime3.so", "libsoftokn3.so", "libssl3.so", "libxul.so"]
Native libs that we don't want: [].
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/browser.rb:277:in `xul_app_shared_lib_check'
./features/step_definitions/browser.rb:291:in `/^the (.*) uses all expected TBB shared libraries$/'
features/unsafe_browser.feature:32:in `And the Unsafe Browser uses all expected TBB shared libraries'
After features/support/hooks.rb:330 6.260

SCENARIO FAILED: 'Starting the Unsafe Browser works as it should' (at time 07:06:11)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/07:06:11_Starting_the_Unsafe_Browser_works_as_it_should.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/07:06:11_Starting_the_Unsafe_Browser_works_as_it_should.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/07:06:11_Starting_the_Unsafe_Browser_works_as_it_should.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/5/artifact/build-artifacts/07:06:11_Starting_the_Unsafe_Browser_works_as_it_should.journal

After features/support/hooks.rb:100 0.000