Project Number Date
test_Tails_ISO_feature-trixie 29 15 Jun 2025, 07:21

Failures Overview

The following summary displays scenarios that failed.

Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
18.362
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.957
And I prepare Tails for memory erasure tests 0.620
When I start a process allocating 128 MiB of memory with a known pattern 2.794
Then patterns cover at least 128 MiB in the guest's memory 5.989
99.610% 
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.610 
SCENARIO FAILED: 'Erasure of memory freed by killed userspace processes' (at time 00:40:17)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/00:40:17_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/29/artifact/build-artifacts/00:40:17_Erasure_of_memory_freed_by_killed_userspace_processes.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/00:40:17_Erasure_of_memory_freed_by_killed_userspace_processes.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/00:40:17_Erasure_of_memory_freed_by_killed_userspace_processes.journal
After features/support/hooks.rb:100 0.000
Feature: Additional software
Tags: @product @check_tor_leaks @slow
13:2.020
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.023
Before features/support/hooks.rb:507 0.157
Steps
Given I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login 1:39.218
And I update APT using apt 14.181
And I install "popularity-contest" using apt 31.423
Then I am proposed to add the "popularity-contest" package to my Additional Software 13.237
When I create a persistent storage and activate the Additional Software feature 38.768
Then Additional Software is correctly configured for package "popularity-contest" 4.341
When I shutdown Tails and wait for the computer to power off 15.993
And I start Tails from USB drive "__internal" with network unplugged 2:2.207
And I enable persistence 36.255
And I log in to a new session 36.450
And the Additional Software installation service has started 1:5.949
Then I am notified that the installation succeeded 5:3.991
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:595: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.038
After features/support/hooks.rb:330 9.641 
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:43:35)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/01:43:35_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/29/artifact/build-artifacts/01:43:35_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/29/artifact/build-artifacts/01:43:35_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.010
Feature: Additional software
Tags: @product @check_tor_leaks @slow
25:32.805
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.005
Before features/support/hooks.rb:507 0.005
Steps
Given a computer 0.312
And I start Tails from USB drive "__internal" and I login with an administration password 3:14.389
And I update APT using apt 9.389
When I install "makepp" using apt 22:8.714
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.028
After features/support/hooks.rb:330 5.215 
SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 02:09:17)
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/29/artifact/build-artifacts/02:09:17_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/29/artifact/build-artifacts/02:09:17_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/29/artifact/build-artifacts/02:09:17_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/29/artifact/build-artifacts/02:09:17_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/29/artifact/build-artifacts/02:09:17_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/29/artifact/build-artifacts/02:09:17_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/29/artifact/build-artifacts/02:09:17_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/29/artifact/build-artifacts/02:09:17_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal
After features/support/hooks.rb:100 0.013
Feature: Additional software
Tags: @product @check_tor_leaks @slow
10:58.405
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.005
Before features/support/hooks.rb:507 0.005
Steps
Given a computer 0.192
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 5:1.471
When I uninstall "popularity-contest" using apt 25.537
And I accept removing "popularity-contest" from Additional Software 3.309
Then "popularity-contest" is not in the list of Additional Software 1.164
When I start Synaptic 16.955
And I update APT using Synaptic 24.850
And I install "cowsay" using Synaptic 4:44.923
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.055
After features/support/hooks.rb:330 5.909 
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:20:21)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/02:20:21_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/29/artifact/build-artifacts/02:20:21_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/29/artifact/build-artifacts/02:20:21_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/29/artifact/build-artifacts/02:20:21_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/29/artifact/build-artifacts/02:20:21_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/29/artifact/build-artifacts/02:20:21_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/29/artifact/build-artifacts/02:20:21_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/29/artifact/build-artifacts/02:20:21_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/29/artifact/build-artifacts/02:20:21_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.008
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
7:59.290
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.005
Before features/support/hooks.rb:507 0.005
Steps
Given a computer 0.265
And I start Tails from USB drive "__internal" with network unplugged 1:53.934
And I enable persistence 14.728
And I remove the "cowsay" deb files from the APT cache 0.126
# 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.183
And I log in to a new session 41.908
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 5:8.144
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:595:in `/^I see the "(.+)" notification(?: after at most (\d+) seconds)?$/'
features/additional_software_packages.feature:129:in `Then I see the "The installation of your additional software failed" notification after at most 300 seconds'
And I can open the Additional Software log file from the notification 0.000
And the package "cowsay" is not installed 0.000
After features/support/hooks.rb:515 0.059
After features/support/hooks.rb:330 7.130 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 02:43:13)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/02:43:13_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/29/artifact/build-artifacts/02:43:13_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/29/artifact/build-artifacts/02:43:13_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/29/artifact/build-artifacts/02:43:13_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/29/artifact/build-artifacts/02:43:13_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/29/artifact/build-artifacts/02:43:13_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/29/artifact/build-artifacts/02:43:13_I_am_notified_when_Additional_Software_fails_to_install_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/02:43:13_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/29/artifact/build-artifacts/02:43:13_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal
After features/support/hooks.rb:100 0.012
Feature: Upgrading an old Tails USB installation
Tags: @product
2:42.754
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.005
Steps
Given a computer 0.183
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 35.388
When I start Tails from USB drive "old" with network unplugged 2:6.089
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:453: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 8.587 
SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 02:46:03)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/02:46:03_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/02:46:03_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/02:46:03_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.journal
After features/support/hooks.rb:100 0.042
Feature: Upgrading an old Tails USB installation
Tags: @product
1:33.322
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.008
Steps
Given a computer 0.514
And I start Tails from USB drive "old" with network unplugged and I login 1:32.808
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:453: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.836 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 02:47:45)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/02:47:45_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_feature-trixie/29/artifact/build-artifacts/02:47:45_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/02:47:45_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/02:47:45_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.008
Feature: Upgrading an old Tails USB installation
Tags: @product
1:24.075
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.005
Steps
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:23.898
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:453: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.886 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:49:15)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/02:49:15_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_feature-trixie/29/artifact/build-artifacts/02:49:15_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_feature-trixie/29/artifact/build-artifacts/02:49:15_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_feature-trixie/29/artifact/build-artifacts/02:49:15_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.008
Feature: Upgrading an old Tails USB installation
Tags: @product
2:12.313
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.005
Steps
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.122
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.587 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:54:29)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/02:54:29_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_feature-trixie/29/artifact/build-artifacts/02:54:29_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/02:54:29_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/02:54:29_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.023
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
22:52.477
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 14.220
And no SquashFS delta is installed 0.293
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.363
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.343
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.964
When the network is plugged 0.096
And Tor is ready 22.389
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:13.745
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.397 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 03:17:27)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/03:17:27_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/29/artifact/build-artifacts/03:17:27_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/03:17:27_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/03:17:27_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
22:42.927
Scenario Upgrading a Tails whose signing key is outdated
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 10.869
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.344
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.075
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 18.706
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:12.805
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.639 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 03:40:16)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/03:40:16_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/29/artifact/build-artifacts/03:40:16_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/03:40:16_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/03:40:16_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000
Feature: Emergency shutdown
Tags: @product @not_release_blocker
2:25.853
Scenario Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4
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 logged in 8.780
And I prepare Tails for memory erasure tests 1.005
And I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 40.241
And I fill the USB drive with a known pattern 1.582
And I read the content of the test FS 0.124
And patterns cover at least 99% of the test FS size in the guest's memory 3.633 
Pattern coverage: 106.113% (97 MiB out of 91 MiB reference memory)
When I eject the boot medium 0.380
And I wait for Tails to finish wiping the memory 1:30.105
cannot 
cannot find MemoryWipeCompleted.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/erase_memory.rb:232:in `/^I wait for Tails to finish wiping the memory$/'
features/emergency_shutdown.feature:44:in `And I wait for Tails to finish wiping the memory'
Then I find very few patterns in the guest's memory 0.000
After features/support/hooks.rb:330 10.938 
SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4' (at time 03:45:28)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/03:45:28_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/03:45:28_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/03:45:28_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.journal
After features/support/hooks.rb:100 0.001
Feature: Hardware failures
Tags: @product
3:7.773
Scenario Outline GPT backup corruption with a persistent partition
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 and stopped at Tails Greeter's login screen 18.114
And I corrupt the boot device's GPT backup header 0.546
And I power off the computer 0.533
When I start the computer 1.270
Then the computer boots Tails 1:59.770
When I log in to a new session 31.256
And all notifications have disappeared 16.059
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.222
<nil> 
<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 7.257 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#1)' (at time 04:09:56)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/04:09:56_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_feature-trixie/29/artifact/build-artifacts/04:09:56_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/04:09:56_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/04:09:56_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.journal
After features/support/hooks.rb:100 0.008
Feature: Hardware failures
Tags: @product
2:48.985
Scenario Outline GPT backup corruption with a persistent partition
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 and stopped at Tails Greeter's login screen 10.134
And I corrupt the boot device's GPT backup partition table 0.464
And I power off the computer 0.378
When I start the computer 1.134
Then the computer boots Tails 1:51.979
When I log in to a new session 31.794
And all notifications have disappeared 12.806
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.292
<nil> 
<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.198 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#2)' (at time 04:12:52)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/04:12:52_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_feature-trixie/29/artifact/build-artifacts/04:12:52_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/04:12:52_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/04:12:52_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.journal
After features/support/hooks.rb:100 0.008
Feature: Hardware failures
Tags: @product
4:3.759
Scenario GPT backup corruption without a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given a computer 0.179
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.079
And I plug USB drive "temp" 1.070
And I write the Tails USB image to disk "temp" 35.260
When I start Tails from USB drive "temp" with network unplugged 2:38.894
Then Tails is running from USB drive "temp" 0.402
And the Greeter forbids creating a persistent partition 0.109
When I log in to a new session 32.802
And all notifications have disappeared 14.730
Then I am recommended to reinstall Tails due to partitioning errors 0.229
<"OK"> 
<"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.174 
SCENARIO FAILED: 'GPT backup corruption without a persistent partition' (at time 04:17:02)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/04:17:02_GPT_backup_corruption_without_a_persistent_partition.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/04:17:02_GPT_backup_corruption_without_a_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/04:17:02_GPT_backup_corruption_without_a_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/04:17:02_GPT_backup_corruption_without_a_persistent_partition.journal
After features/support/hooks.rb:100 0.141
Feature: Tails-related cryptographic keys are up-to-date
Tags: @product
22.700
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 22.217
Then the keys trusted by APT are valid for the next 3 months 0.483
Command 
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.817 
SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 04:28:30)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/04:28:30_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_feature-trixie/29/artifact/build-artifacts/04:28:30_The_included_APT_repository_keys_are_up-to-date.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/04:28:30_The_included_APT_repository_keys_are_up-to-date.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/04:28:30_The_included_APT_repository_keys_are_up-to-date.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
2:17.580
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.529
When I log in to a new session in French (fr) 46.302
Then the keyboard layout is set to "fr" 0.329
When the network is plugged 0.125
And Tor is ready 22.176
Then I successfully start the Unsafe Browser 22.268
And I kill the Unsafe Browser 7.415
When I enable the screen keyboard 0.195
Then the screen keyboard works in Tor Browser 30.237
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:1040:in `launch_app'
./features/step_definitions/common_steps.rb:1095:in `launch_tor_browser'
./features/step_definitions/browser.rb:456:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:422: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 11.282 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#4)' (at time 04:47:52)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/04:47:52_Tails_is_localized_for_every_tier-1_language,_Examples___4_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/04:47:52_Tails_is_localized_for_every_tier-1_language,_Examples___4_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/04:47:52_Tails_is_localized_for_every_tier-1_language,_Examples___4_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
2:21.876
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 9.333
When I log in to a new session in Italian (it) 50.902
Then the keyboard layout is set to "it" 1.116
When the network is plugged 0.200
And Tor is ready 25.347
Then I successfully start the Unsafe Browser 16.894
And I kill the Unsafe Browser 7.317
When I enable the screen keyboard 0.205
Then the screen keyboard works in Tor Browser 30.558
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:1040:in `launch_app'
./features/step_definitions/common_steps.rb:1095:in `launch_tor_browser'
./features/step_definitions/browser.rb:456:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:422: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 10.940 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#8)' (at time 05:01:26)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/05:01:26_Tails_is_localized_for_every_tier-1_language,_Examples___8_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/05:01:26_Tails_is_localized_for_every_tier-1_language,_Examples___8_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/05:01:26_Tails_is_localized_for_every_tier-1_language,_Examples___8_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
2:19.697
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.463
When I log in to a new session in Russian (ru) 51.961
Then the keyboard layout is set to "ru" 0.483
When the network is plugged 0.430
And Tor is ready 22.670
Then I successfully start the Unsafe Browser 17.788
And I kill the Unsafe Browser 7.434
When I enable the screen keyboard 0.161
Then the screen keyboard works in Tor Browser 30.303
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:1040:in `launch_app'
./features/step_definitions/common_steps.rb:1095:in `launch_tor_browser'
./features/step_definitions/browser.rb:456:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:422:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:53: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 "ru" 0.000
After features/support/hooks.rb:330 8.717 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#11)' (at time 05:10:59)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/05:10:59_Tails_is_localized_for_every_tier-1_language,_Examples___11_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/05:10:59_Tails_is_localized_for_every_tier-1_language,_Examples___11_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/05:10:59_Tails_is_localized_for_every_tier-1_language,_Examples___11_.journal
After features/support/hooks.rb:100 0.000
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
52.234
Scenario Chatting with some friend over XMPP
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Before features/support/hooks.rb:507 0.005
Steps
Given I have started Tails from DVD and logged in and the network is connected 16.585
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.667
Then I see Pidgin's account manager window 3.264
When I create my XMPP account 20.716
cannot 
cannot find PidginAddAccountWindow.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/pidgin.rb:123:in `/^I create my XMPP account$/'
features/pidgin.feature:21: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
Given my XMPP friend goes online 0.000
When I start a conversation with my friend 0.000
And I say something to my friend 0.000
Then I receive a response from my friend 0.000
After features/support/hooks.rb:515 0.048
After features/support/hooks.rb:330 6.306 
SCENARIO FAILED: 'Chatting with some friend over XMPP' (at time 06:41:24)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/06:41:24_Chatting_with_some_friend_over_XMPP.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/06:41:24_Chatting_with_some_friend_over_XMPP.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/06:41:24_Chatting_with_some_friend_over_XMPP.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/06:41:24_Chatting_with_some_friend_over_XMPP.journal
After features/support/hooks.rb:100 0.000
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
48.860
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.005
Before features/support/hooks.rb:507 0.005
Steps
Given I have started Tails from DVD and logged in and the network is connected 13.976
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.038
Then I see Pidgin's account manager window 3.025
When I create my XMPP account 20.820
cannot 
cannot find PidginAddAccountWindow.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/pidgin.rb:123: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.041
After features/support/hooks.rb:330 5.870 
SCENARIO FAILED: 'Chatting with some friend over XMPP in a multi-user chat' (at time 06:42:20)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/06:42:20_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/29/artifact/build-artifacts/06:42:20_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/06:42:20_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/29/artifact/build-artifacts/06:42:20_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.journal
After features/support/hooks.rb:100 0.000
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
47.632
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.004
Before features/support/hooks.rb:507 0.004
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.317
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 10.878
Then I see Pidgin's account manager window 3.495
And I create my XMPP account 20.940
cannot 
cannot find PidginAddAccountWindow.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/pidgin.rb:123: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.037
After features/support/hooks.rb:330 6.396 
SCENARIO FAILED: 'Connecting to the tails multi-user chat with my XMPP account' (at time 06:43:13)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/06:43:13_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/29/artifact/build-artifacts/06:43:13_Connecting_to_the_tails_multi-user_chat_with_my_XMPP_account.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/06:43:13_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/29/artifact/build-artifacts/06:43:13_Connecting_to_the_tails_multi-user_chat_with_my_XMPP_account.journal
After features/support/hooks.rb:100 0.000
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
1:15.490
Scenario Using a persistent Pidgin configuration
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Before features/support/hooks.rb:507 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.295
And the network is plugged 0.151
And Tor is ready 20.098
And available upgrades have been checked 1.203
And all notifications have disappeared 5.637
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 10.795
Then I see Pidgin's account manager window 3.539
When I create my XMPP account 20.769
cannot 
cannot find PidginAddAccountWindow.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/pidgin.rb:123:in `/^I create my XMPP account$/'
features/pidgin.feature:68: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 close Pidgin 0.000
And I take note of the configured Pidgin accounts 0.000
And I shutdown Tails and wait for the computer to power off 0.000
Given a computer 0.000
And I start Tails from USB drive "__internal" and I login with persistence enabled 0.000
And Pidgin has the expected persistent accounts configured 0.000
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 0.000
Then Pidgin automatically enables my XMPP account 0.000
And I join some empty multi-user chat 0.000
# Exercise Pidgin AppArmor profile with persistence enabled.
# This should really be in dedicated scenarios, but it would be
# too costly to set up the virtual USB drive with persistence more
# than once in this feature.
Given I start monitoring the AppArmor log of "/usr/bin/pidgin" 0.000
Then I cannot add a certificate from the "/home/amnesia/.gnupg" directory to Pidgin 0.000
And AppArmor has denied "/usr/bin/pidgin" from opening "/home/amnesia/.gnupg/test.crt" 0.000
When I close Pidgin's certificate import failure dialog 0.000
And I close Pidgin's certificate manager 0.000
Given I restart monitoring the AppArmor log of "/usr/bin/pidgin" 0.000
Then I cannot add a certificate from the "/live/persistence/TailsData_unlocked/gnupg" directory to Pidgin 0.000
And AppArmor has denied "/usr/bin/pidgin" from opening "/live/persistence/TailsData_unlocked/gnupg/test.crt" 0.000
When I close Pidgin's certificate import failure dialog 0.000
And I close Pidgin's certificate manager 0.000
Then I can add a certificate from the "/home/amnesia" directory to Pidgin 0.000
After features/support/hooks.rb:515 0.041
After features/support/hooks.rb:330 5.871 
SCENARIO FAILED: 'Using a persistent Pidgin configuration' (at time 06:44:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/06:44:35_Using_a_persistent_Pidgin_configuration.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/06:44:35_Using_a_persistent_Pidgin_configuration.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/06:44:35_Using_a_persistent_Pidgin_configuration.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/06:44:35_Using_a_persistent_Pidgin_configuration.journal
After features/support/hooks.rb:100 0.000
Feature: Tails has a sane default configuration
Tags: @product
10.756
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.007
Steps
Given I have started Tails from DVD without network and logged in 10.542
Then there are no unexpected messages of priority "err" or higher in the journal 0.214
Unexpected 
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": "dd7ba977f69648fabc246f0df6d046a9",
    "_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": "1749943516900124",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "79007df32e2644c68fa61ee69dfb8923",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=839d11f0e28a4bcebed7b620a38c1616;i=37c;b=dd7ba977f69648fabc246f0df6d046a9;m=e2a7ff;t=6379079b3de1d;x=6829d564a4d42eba",
    "__MONOTONIC_TIMESTAMP": "14854143",
    "__REALTIME_TIMESTAMP": "1749943516913181",
    "__SEQNUM": "892",
    "__SEQNUM_ID": "839d11f0e28a4bcebed7b620a38c1616"
  },
  {
    "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": "dd7ba977f69648fabc246f0df6d046a9",
    "_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": "1749943516900153",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "79007df32e2644c68fa61ee69dfb8923",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=839d11f0e28a4bcebed7b620a38c1616;i=37e;b=dd7ba977f69648fabc246f0df6d046a9;m=e2a96e;t=6379079b3df8c;x=e02badffbb1db4bb",
    "__MONOTONIC_TIMESTAMP": "14854510",
    "__REALTIME_TIMESTAMP": "1749943516913548",
    "__SEQNUM": "894",
    "__SEQNUM_ID": "839d11f0e28a4bcebed7b620a38c1616"
  },
  {
    "MESSAGE": "The group `powerdev' does not exist.",
    "SYSLOG_IDENTIFIER": "adduser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "1891",
    "SYSLOG_TIMESTAMP": "Jun 14 23:25:24 ",
    "_BOOT_ID": "dd7ba977f69648fabc246f0df6d046a9",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "1891",
    "_RUNTIME_SCOPE": "system",
    "_SOURCE_REALTIME_TIMESTAMP": "1749943524422053",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=839d11f0e28a4bcebed7b620a38c1616;i=3ff;b=dd7ba977f69648fabc246f0df6d046a9;m=1557e2c;t=637907a26b449;x=4378bee99352f349",
    "__MONOTONIC_TIMESTAMP": "22380076",
    "__REALTIME_TIMESTAMP": "1749943524439113",
    "__SEQNUM": "1023",
    "__SEQNUM_ID": "839d11f0e28a4bcebed7b620a38c1616"
  },
  {
    "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": "dd7ba977f69648fabc246f0df6d046a9",
    "_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": "1749943710437712",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "79007df32e2644c68fa61ee69dfb8923",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=839d11f0e28a4bcebed7b620a38c1616;i=8c9;b=dd7ba977f69648fabc246f0df6d046a9;m=66d4461;t=63790853cd183;x=14892e83db9faa6b",
    "__MONOTONIC_TIMESTAMP": "107824225",
    "__REALTIME_TIMESTAMP": "1749943710437763",
    "__SEQNUM": "2249",
    "__SEQNUM_ID": "839d11f0e28a4bcebed7b620a38c1616"
  },
  {
    "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": "dd7ba977f69648fabc246f0df6d046a9",
    "_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": "1749943710437736",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "79007df32e2644c68fa61ee69dfb8923",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=839d11f0e28a4bcebed7b620a38c1616;i=8cb;b=dd7ba977f69648fabc246f0df6d046a9;m=66d45dd;t=63790853cd2ff;x=3ca375278524d223",
    "__MONOTONIC_TIMESTAMP": "107824605",
    "__REALTIME_TIMESTAMP": "1749943710438143",
    "__SEQNUM": "2251",
    "__SEQNUM_ID": "839d11f0e28a4bcebed7b620a38c1616"
  },
  {
    "MESSAGE": "The user `amnesia' is not a member of group `sudo'.",
    "SYSLOG_IDENTIFIER": "deluser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "6806",
    "SYSLOG_TIMESTAMP": "Jun 14 23:28:35 ",
    "_AUDIT_LOGINUID": "1000",
    "_AUDIT_SESSION": "4",
    "_BOOT_ID": "dd7ba977f69648fabc246f0df6d046a9",
    "_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": "6806",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749943715376607",
    "_SYSTEMD_CGROUP": "/user.slice/user-1000.slice/session-4.scope",
    "_SYSTEMD_INVOCATION_ID": "3119944e97bc463ea75b90f5415629bb",
    "_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=839d11f0e28a4bcebed7b620a38c1616;i=121f;b=dd7ba977f69648fabc246f0df6d046a9;m=6b8a110;t=6379085882e32;x=6136d663f9ddca4a",
    "__MONOTONIC_TIMESTAMP": "112763152",
    "__REALTIME_TIMESTAMP": "1749943715376690",
    "__SEQNUM": "4639",
    "__SEQNUM_ID": "839d11f0e28a4bcebed7b620a38c1616"
  }
].
<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.787 
SCENARIO FAILED: 'No unexpected error messages in the journal after booting from DVD' (at time 06:50:34)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/06:50:34_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/29/artifact/build-artifacts/06:50:34_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/06:50:34_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/29/artifact/build-artifacts/06:50:34_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.journal
After features/support/hooks.rb:100 0.000
Feature: Tails has a sane default configuration
Tags: @product
14.899
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.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.699
Then there are no unexpected messages of priority "err" or higher in the journal 0.200
Unexpected 
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": "707",
    "_BOOT_ID": "ced0d59f65c440fba5ebfbe9ce11c06a",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "707",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749945884638045",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "0a19ec47c16d432db7cba862622a356b",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=ba1cbad325954105942fe9f5d95d1df3;i=366;b=ced0d59f65c440fba5ebfbe9ce11c06a;m=13d6523;t=6379106d47ba0;x=adb4588c4a5a8c8f",
    "__MONOTONIC_TIMESTAMP": "20800803",
    "__REALTIME_TIMESTAMP": "1749945884638112",
    "__SEQNUM": "870",
    "__SEQNUM_ID": "ba1cbad325954105942fe9f5d95d1df3"
  },
  {
    "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": "707",
    "_BOOT_ID": "ced0d59f65c440fba5ebfbe9ce11c06a",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "707",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749945884638440",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "0a19ec47c16d432db7cba862622a356b",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=ba1cbad325954105942fe9f5d95d1df3;i=368;b=ced0d59f65c440fba5ebfbe9ce11c06a;m=13d666f;t=6379106d47ced;x=7935c951bcc71916",
    "__MONOTONIC_TIMESTAMP": "20801135",
    "__REALTIME_TIMESTAMP": "1749945884638445",
    "__SEQNUM": "872",
    "__SEQNUM_ID": "ba1cbad325954105942fe9f5d95d1df3"
  },
  {
    "MESSAGE": "The group `powerdev' does not exist.",
    "SYSLOG_IDENTIFIER": "adduser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "2803",
    "SYSLOG_TIMESTAMP": "Jun 15 00:04:56 ",
    "_BOOT_ID": "ced0d59f65c440fba5ebfbe9ce11c06a",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "2803",
    "_RUNTIME_SCOPE": "system",
    "_SOURCE_REALTIME_TIMESTAMP": "1749945896411142",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=ba1cbad325954105942fe9f5d95d1df3;i=416;b=ced0d59f65c440fba5ebfbe9ce11c06a;m=1f123b3;t=6379107883a30;x=38a1df8cf996c214",
    "__MONOTONIC_TIMESTAMP": "32580531",
    "__REALTIME_TIMESTAMP": "1749945896417840",
    "__SEQNUM": "1046",
    "__SEQNUM_ID": "ba1cbad325954105942fe9f5d95d1df3"
  },
  {
    "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": "707",
    "_BOOT_ID": "ced0d59f65c440fba5ebfbe9ce11c06a",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "707",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749946073766636",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "0a19ec47c16d432db7cba862622a356b",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=ba1cbad325954105942fe9f5d95d1df3;i=e9b;b=ced0d59f65c440fba5ebfbe9ce11c06a;m=c45f33c;t=63791121a8c45;x=39e9d6311f404ac7",
    "__MONOTONIC_TIMESTAMP": "205910844",
    "__REALTIME_TIMESTAMP": "1749946073779269",
    "__SEQNUM": "3739",
    "__SEQNUM_ID": "ba1cbad325954105942fe9f5d95d1df3"
  },
  {
    "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": "707",
    "_BOOT_ID": "ced0d59f65c440fba5ebfbe9ce11c06a",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "707",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749946073778028",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "0a19ec47c16d432db7cba862622a356b",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=ba1cbad325954105942fe9f5d95d1df3;i=e9d;b=ced0d59f65c440fba5ebfbe9ce11c06a;m=c45f4cc;t=63791121a8dd5;x=8bfa0ba14637d8c8",
    "__MONOTONIC_TIMESTAMP": "205911244",
    "__REALTIME_TIMESTAMP": "1749946073779669",
    "__SEQNUM": "3741",
    "__SEQNUM_ID": "ba1cbad325954105942fe9f5d95d1df3"
  },
  {
    "MESSAGE": "The user `amnesia' is not a member of group `sudo'.",
    "SYSLOG_IDENTIFIER": "deluser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "12279",
    "SYSLOG_TIMESTAMP": "Jun 15 00:08:03 ",
    "_AUDIT_LOGINUID": "1000",
    "_AUDIT_SESSION": "4",
    "_BOOT_ID": "ced0d59f65c440fba5ebfbe9ce11c06a",
    "_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": "12279",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749946083588897",
    "_SYSTEMD_CGROUP": "/user.slice/user-1000.slice/session-4.scope",
    "_SYSTEMD_INVOCATION_ID": "8bbe1f5bf05e46028ab14a08f9e5a9cb",
    "_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=ba1cbad325954105942fe9f5d95d1df3;i=1893;b=ced0d59f65c440fba5ebfbe9ce11c06a;m=cdba225;t=6379112b03b2e;x=a0c19e5e859c1b2b",
    "__MONOTONIC_TIMESTAMP": "215720485",
    "__REALTIME_TIMESTAMP": "1749946083588910",
    "__SEQNUM": "6291",
    "__SEQNUM_ID": "ba1cbad325954105942fe9f5d95d1df3"
  }
].
<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.161 
SCENARIO FAILED: 'No unexpected error messages in the journal after booting from USB drive' (at time 06:50:55)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/06:50:55_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_feature-trixie/29/artifact/build-artifacts/06:50:55_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/06:50:55_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/06:50:55_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.journal
After features/support/hooks.rb:100 0.000
Feature: Shutdown buttons in the system menu
Tags: @product
29.625
Scenario I can shutdown Tails via the system menu
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.048
Steps
Given I have started Tails from DVD and logged in and the network is connected 15.005
When I request a shutdown using the system menu 14.620
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/support/helpers/dogtail.rb:371:in `grabFocus'
./features/step_definitions/common_steps.rb:887: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 6.134 
SCENARIO FAILED: 'I can shutdown Tails via the system menu' (at time 06:51:29)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/06:51:29_I_can_shutdown_Tails_via_the_system_menu.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/06:51:29_I_can_shutdown_Tails_via_the_system_menu.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/06:51:29_I_can_shutdown_Tails_via_the_system_menu.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/06:51:29_I_can_shutdown_Tails_via_the_system_menu.journal
After features/support/hooks.rb:100 0.000
Feature: Shutdown buttons in the system menu
Tags: @product @not_release_blocker
28.729
Scenario I can reboot Tails via the system menu
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 13.767
When I request a reboot using the system menu 14.962
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/support/helpers/dogtail.rb:371:in `grabFocus'
./features/step_definitions/common_steps.rb:887: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 6.212 
SCENARIO FAILED: 'I can reboot Tails via the system menu' (at time 06:52:04)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/06:52:04_I_can_reboot_Tails_via_the_system_menu.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/06:52:04_I_can_reboot_Tails_via_the_system_menu.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/06:52:04_I_can_reboot_Tails_via_the_system_menu.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/06:52:04_I_can_reboot_Tails_via_the_system_menu.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product @check_tor_leaks
1:22.145
Scenario The Downloads directory is usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Before features/support/hooks.rb:507 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.615
Then the live user's Downloads directory exists 0.050
And there is a GNOME bookmark for the Downloads directory 19.127
When I start the Tor Browser 23.446
And the Tor Browser loads the startup page 2.250
Then I can save the current page as "index.html" to the Downloads directory 24.655
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'org.gnome.Nautilus' application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/browser.rb:6:in `new'
./features/step_definitions/browser.rb:6:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:38:in `browser_save_page_as'
./features/step_definitions/browser.rb:543:in `/^I (can|cannot) save the current page as "([^"]+[.]html)" to the (.*) (directory|GNOME bookmark)$/'
features/torified_browsing.feature:24:in `Then I can save the current page as "index.html" to the Downloads directory'
And I can print the current page as "output.pdf" to the Downloads directory 0.000
After features/support/hooks.rb:515 0.045
After features/support/hooks.rb:330 8.340 
SCENARIO FAILED: 'The Downloads directory is usable in Tor Browser' (at time 07:19:48)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:19:48_The_Downloads_directory_is_usable_in_Tor_Browser.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:19:48_The_Downloads_directory_is_usable_in_Tor_Browser.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:19:48_The_Downloads_directory_is_usable_in_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:19:48_The_Downloads_directory_is_usable_in_Tor_Browser.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
46.672
Scenario The Tor Browser uses TBB's shared libraries
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.892
When I start the Tor Browser 29.672
Then the Tor Browser uses all expected TBB shared libraries 4.107
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:259:in `xul_app_shared_lib_check'
./features/step_definitions/browser.rb:273:in `/^the (.*) uses all expected TBB shared libraries$/'
features/torified_browsing.feature:76:in `Then the Tor Browser uses all expected TBB shared libraries'
After features/support/hooks.rb:330 5.460 
SCENARIO FAILED: 'The Tor Browser uses TBB's shared libraries' (at time 07:26:58)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:26:58_The_Tor_Browser_uses_TBB_s_shared_libraries.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:26:58_The_Tor_Browser_uses_TBB_s_shared_libraries.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:26:58_The_Tor_Browser_uses_TBB_s_shared_libraries.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:26:58_The_Tor_Browser_uses_TBB_s_shared_libraries.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
2:1.007
Scenario The Persistent directory is usable in Tor Browser
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 12.253
And the network is plugged 0.163
And I successfully configure Tor 20.650
And available upgrades have been checked 1.138
And all notifications have disappeared 5.293
And there is a GNOME bookmark for the Persistent directory 18.999
When I start the Tor Browser 35.020
And I download some file in the Tor Browser to the Persistent directory 27.488
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'org.gnome.Nautilus' application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/browser.rb:6:in `new'
./features/step_definitions/browser.rb:6:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:310:in `/^I download some file in the Tor Browser to the (.*) directory$/'
features/torified_browsing.feature:113:in `And I download some file in the Tor Browser to the Persistent directory'
Then the file is saved to the Persistent directory 0.000
When I open the address "https://tails.net/about" in the Tor Browser 0.000
Then "Tails - How Tails works" has loaded in the Tor Browser 0.000
And I can print the current page as "output.pdf" to the Persistent directory 0.000
After features/support/hooks.rb:330 8.197 
SCENARIO FAILED: 'The Persistent directory is usable in Tor Browser' (at time 07:32:29)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:32:29_The_Persistent_directory_is_usable_in_Tor_Browser.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:32:29_The_Persistent_directory_is_usable_in_Tor_Browser.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:32:29_The_Persistent_directory_is_usable_in_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:32:29_The_Persistent_directory_is_usable_in_Tor_Browser.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:36.361
Scenario Outline The default XDG directories are usable in Tor Browser
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 logged in 8.876
Then the live user's Documents directory exists 0.376
And there is a GNOME bookmark for the Documents directory 21.247
Then I start the Tor Browser in offline mode 28.792
And I can save the current page as "index.html" to the Documents GNOME bookmark 37.067
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/browser.rb:19:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:38:in `browser_save_page_as'
./features/step_definitions/browser.rb:543:in `/^I (can|cannot) save the current page as "([^"]+[.]html)" to the (.*) (directory|GNOME bookmark)$/'
features/torified_browsing.feature:127:in `And I can save the current page as "index.html" to the Documents GNOME bookmark'
features/torified_browsing.feature:124:in `And I can save the current page as "index.html" to the <dir> GNOME bookmark'
After features/support/hooks.rb:330 8.401 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#1)' (at time 07:34:14)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:34:14_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:34:14_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:34:14_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:34:14_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:10.569
Scenario Outline The default XDG directories are usable in Tor Browser
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 logged in 8.573
Then the live user's Downloads directory exists 0.262
And there is a GNOME bookmark for the Downloads directory 18.272
Then I start the Tor Browser in offline mode 24.827
And I can save the current page as "index.html" to the Downloads GNOME bookmark 18.633
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'org.gnome.Nautilus' application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/browser.rb:6:in `new'
./features/step_definitions/browser.rb:6:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:38:in `browser_save_page_as'
./features/step_definitions/browser.rb:543:in `/^I (can|cannot) save the current page as "([^"]+[.]html)" to the (.*) (directory|GNOME bookmark)$/'
features/torified_browsing.feature:128:in `And I can save the current page as "index.html" to the Downloads GNOME bookmark'
features/torified_browsing.feature:124:in `And I can save the current page as "index.html" to the <dir> GNOME bookmark'
After features/support/hooks.rb:330 10.032 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#2)' (at time 07:35:33)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:35:33_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:35:33_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:35:33_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:12.327
Scenario Outline The default XDG directories are usable in Tor Browser
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 logged in 9.475
Then the live user's Pictures directory exists 0.178
And there is a GNOME bookmark for the Pictures directory 18.785
Then I start the Tor Browser in offline mode 25.170
And I can save the current page as "index.html" to the Pictures GNOME bookmark 18.717
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'org.gnome.Nautilus' application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/browser.rb:6:in `new'
./features/step_definitions/browser.rb:6:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:38:in `browser_save_page_as'
./features/step_definitions/browser.rb:543:in `/^I (can|cannot) save the current page as "([^"]+[.]html)" to the (.*) (directory|GNOME bookmark)$/'
features/torified_browsing.feature:130:in `And I can save the current page as "index.html" to the Pictures GNOME bookmark'
features/torified_browsing.feature:124:in `And I can save the current page as "index.html" to the <dir> GNOME bookmark'
After features/support/hooks.rb:330 8.486 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#4)' (at time 07:38:15)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:38:15_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___4_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:38:15_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___4_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:38:15_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___4_.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Unsafe Browser
Tags: @product @not_release_blocker
52.910
Scenario Starting a second instance of the Unsafe Browser results in an error message being shown
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 12.839
When I successfully start the Unsafe Browser 18.921
# Wait for whatever facility the GNOME Activities Overview uses to
# learn about which applications are running to "settle". Without
# this sleep, it is confused and it's impossible to start a new
# instance (it will just switch to the one we already started).
And I wait 10 seconds 10.008 
Slept for 10 seconds
And I try to start the Unsafe Browser 0.521
Then I see a warning about another instance already running 10.618
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'zenity' application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/unsafe_browser.rb:76:in `new'
./features/step_definitions/unsafe_browser.rb:76:in `/^I see a warning about another instance already running$/'
features/unsafe_browser.feature:59:in `Then I see a warning about another instance already running'
After features/support/hooks.rb:330 9.840 
SCENARIO FAILED: 'Starting a second instance of the Unsafe Browser results in an error message being shown' (at time 07:54:37)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:54:37_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:54:37_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:54:37_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:54:37_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
21.499
Scenario Use Unlock VeraCrypt Volumes to unlock a USB drive that has a basic VeraCrypt volume
Steps
When I plug a USB drive containing a basic VeraCrypt volume 8.376
And I cancel the GNOME authentication prompt 2.304
And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 6.693
And I open this VeraCrypt volume in GNOME Files 3.526
Then I see the expected contents in this VeraCrypt volume 0.496
When I lock the currently opened VeraCrypt volume 0.101
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<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/veracrypt.rb:330:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:18:in `When I lock the currently opened VeraCrypt volume'
Then the VeraCrypt volume has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.703 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a USB drive that has a basic VeraCrypt volume' (at time 07:59:17)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:59:17_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:59:17_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:59:17_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:59:17_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
25.857
Scenario Use Unlock VeraCrypt Volumes to unlock a USB drive that has a hidden VeraCrypt volume
Steps
When I plug a USB drive containing a hidden VeraCrypt volume 11.641
And I cancel the GNOME authentication prompt 2.246
And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 7.781
And I open this VeraCrypt volume in GNOME Files 3.644
Then I see the expected contents in this VeraCrypt volume 0.466
When I lock the currently opened VeraCrypt volume 0.076
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<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/veracrypt.rb:330:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:27:in `When I lock the currently opened VeraCrypt volume'
Then the VeraCrypt volume has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.595 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a USB drive that has a hidden VeraCrypt volume' (at time 07:59:57)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:59:57_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:59:57_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:59:57_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/07:59:57_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
29.831
Scenario Use Unlock VeraCrypt Volumes to unlock a basic VeraCrypt file container with a PIM
Steps
When I plug and mount a USB drive containing a basic VeraCrypt file container with a PIM 16.973
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 9.175
And I open this VeraCrypt volume in GNOME Files 3.179
Then I see the expected contents in this VeraCrypt volume 0.420
When I lock the currently opened VeraCrypt file container 0.083
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<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/veracrypt.rb:330:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:35:in `When I lock the currently opened VeraCrypt file container'
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 9.490 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a basic VeraCrypt file container with a PIM' (at time 08:00:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/08:00:42_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/08:00:42_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/08:00:42_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/08:00:42_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
45.830
Scenario Use Unlock VeraCrypt Volumes to unlock a hidden VeraCrypt file container
Steps
When I plug and mount a USB drive containing a hidden VeraCrypt file container 29.204
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 12.883
And I open this VeraCrypt volume in GNOME Files 3.205
Then I see the expected contents in this VeraCrypt volume 0.464
When I lock the currently opened VeraCrypt file container 0.072
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<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/veracrypt.rb:330:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:43:in `When I lock the currently opened VeraCrypt file container'
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 6.247 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a hidden VeraCrypt file container' (at time 08:01:47)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/08:01:47_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/08:01:47_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/08:01:47_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/08:01:47_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:100 0.020
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
30.785
Scenario Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile
Steps
When I plug a USB drive containing a basic VeraCrypt volume with a keyfile 8.629
And I cancel the GNOME authentication prompt 2.485
And I unlock and mount this VeraCrypt volume with GNOME Disks 12.533
And I open this VeraCrypt volume in GNOME Files 5.736
Then I see the expected contents in this VeraCrypt volume 1.324
When I lock the currently opened VeraCrypt volume 0.074
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<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/veracrypt.rb:330:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:54:in `When I lock the currently opened VeraCrypt volume'
Then the VeraCrypt volume has been unmounted and locked 0.000
After features/support/hooks.rb:330 6.676 
SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile' (at time 08:02:33)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/08:02:33_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/08:02:33_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/08:02:33_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/08:02:33_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
28.208
Scenario Use GNOME Disks to unlock a USB drive that has a hidden VeraCrypt volume
Steps
When I plug a USB drive containing a hidden VeraCrypt volume 11.755
And I cancel the GNOME authentication prompt 2.772
And I unlock and mount this VeraCrypt volume with GNOME Disks 9.161
And I open this VeraCrypt volume in GNOME Files 3.896
Then I see the expected contents in this VeraCrypt volume 0.483
When I lock the currently opened VeraCrypt volume 0.138
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<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/veracrypt.rb:330:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:63:in `When I lock the currently opened VeraCrypt volume'
Then the VeraCrypt volume has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.727 
SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a hidden VeraCrypt volume' (at time 08:03:17)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/08:03:17_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/08:03:17_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/08:03:17_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/08:03:17_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
52.243
Scenario Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile
Steps
When I plug and mount a USB drive containing a basic VeraCrypt file container with a keyfile 24.521
And I unlock and mount this VeraCrypt file container with GNOME Disks 23.899
And I open this VeraCrypt volume in GNOME Files 3.235
Then I see the expected contents in this VeraCrypt volume 0.483
When I lock the currently opened VeraCrypt file container 0.103
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<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/veracrypt.rb:330:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:71:in `When I lock the currently opened VeraCrypt file container'
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 6.470 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile' (at time 08:04:25)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/08:04:25_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/08:04:25_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/08:04:25_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/08:04:25_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.journal
After features/support/hooks.rb:100 0.026
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
56.058
Scenario Use GNOME Disks to unlock a hidden VeraCrypt file container
Steps
When I plug and mount a USB drive containing a hidden VeraCrypt file container 29.722
And I unlock and mount this VeraCrypt file container with GNOME Disks 21.688
And I open this VeraCrypt volume in GNOME Files 3.993
Then I see the expected contents in this VeraCrypt volume 0.564
When I lock the currently opened VeraCrypt file container 0.088
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<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/veracrypt.rb:330:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:79:in `When I lock the currently opened VeraCrypt file container'
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.702 
SCENARIO FAILED: 'Use GNOME Disks to unlock a hidden VeraCrypt file container' (at time 08:05:38)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/08:05:38_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/08:05:38_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/08:05:38_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/08:05:38_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:100 0.017
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
43.313
Scenario Use GNOME Disks to unlock a basic VeraCrypt file container with a PIM
Steps
When I plug and mount a USB drive containing a basic VeraCrypt file container with a PIM 18.790
And I unlock and mount this VeraCrypt file container with GNOME Disks 20.269
And I open this VeraCrypt volume in GNOME Files 3.919
Then I see the expected contents in this VeraCrypt volume 0.251
When I lock the currently opened VeraCrypt file container 0.082
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<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/veracrypt.rb:330:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:87:in `When I lock the currently opened VeraCrypt file container'
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.676 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a PIM' (at time 08:06:36)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/08:06:36_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/08:06:36_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/08:06:36_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/29/artifact/build-artifacts/08:06:36_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.journal
After features/support/hooks.rb:100 0.000