Project Number Date
test_Tails_ISO_feature-trixie 31 17 Jun 2025, 06:53

Failures Overview

The following summary displays scenarios that failed.

15.430
Scenario Erasure of memory freed by killed userspace processes
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails from DVD without network and logged in 8.404
And I prepare Tails for memory erasure tests 0.617
When I start a process allocating 128 MiB of memory with a known pattern 2.474
Then patterns cover at least 128 MiB in the guest's memory 3.932
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.493

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/00:39:46_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/31/artifact/build-artifacts/00:39:46_Erasure_of_memory_freed_by_killed_userspace_processes.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/00:39:46_Erasure_of_memory_freed_by_killed_userspace_processes.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/00:39:46_Erasure_of_memory_freed_by_killed_userspace_processes.journal

After features/support/hooks.rb:100 0.000
11:50.847
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.006
Before features/support/hooks.rb:507 0.006
Steps
Given I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login 1:25.084
And I update APT using apt 18.203
And I install "popularity-contest" using apt 26.532
Then I am proposed to add the "popularity-contest" package to my Additional Software 13.549
When I create a persistent storage and activate the Additional Software feature 25.140
Then Additional Software is correctly configured for package "popularity-contest" 3.092
When I shutdown Tails and wait for the computer to power off 12.489
And I start Tails from USB drive "__internal" with network unplugged 1:51.012
And I enable persistence 30.698
And I log in to a new session 34.735
And the Additional Software installation service has started 47.245
Then I am notified that the installation succeeded 5:3.062
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.030
After features/support/hooks.rb:330 6.651

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/01:32:05_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.file_content_var_log_boot.log

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

Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/01:32:05_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.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/31/artifact/build-artifacts/01:32:05_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_var_lib_apt

Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/01:32:05_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_mount

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

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

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

After features/support/hooks.rb:100 0.012
25:47.106
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.006
Steps
Given a computer 0.168
And I start Tails from USB drive "__internal" and I login with an administration password 3:29.022
And I update APT using apt 12.684
When I install "makepp" using apt 22:5.231
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.037
After features/support/hooks.rb:330 5.392

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

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/31/artifact/build-artifacts/01:57:58_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/31/artifact/build-artifacts/01:57:58_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/31/artifact/build-artifacts/01:57:58_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/31/artifact/build-artifacts/01:57:58_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/31/artifact/build-artifacts/01:57:58_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/31/artifact/build-artifacts/01:57:58_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/31/artifact/build-artifacts/01:57:58_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/31/artifact/build-artifacts/01:57:58_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal

After features/support/hooks.rb:100 0.012
10:14.318
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.006
Before features/support/hooks.rb:507 0.005
Steps
Given a computer 0.204
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 4:34.765
When I uninstall "popularity-contest" using apt 25.001
And I accept removing "popularity-contest" from Additional Software 2.680
Then "popularity-contest" is not in the list of Additional Software 0.759
When I start Synaptic 16.602
And I update APT using Synaptic 21.748
And I install "cowsay" using Synaptic 4:32.556
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.038
After features/support/hooks.rb:330 5.867

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:08:18)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/02:08:18_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/31/artifact/build-artifacts/02:08:18_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/31/artifact/build-artifacts/02:08:18_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/31/artifact/build-artifacts/02:08:18_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/31/artifact/build-artifacts/02:08:18_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/31/artifact/build-artifacts/02:08:18_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/31/artifact/build-artifacts/02:08:18_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/31/artifact/build-artifacts/02:08:18_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/31/artifact/build-artifacts/02:08:18_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.009
3:20.881
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.006
Steps
Given a computer 0.182
And I start Tails from USB drive "__internal" with network unplugged 1:47.616
And I enable persistence 14.057
And I remove the "cowsay" deb files from the APT cache 0.063
# 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.083
And I log in to a new session 51.364
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 16.274
And I can open the Additional Software log file from the notification 11.239
The
The Dogtail init script raised: SearchError: descendant of [notification | ]: child with name='Show Log' roleName='button'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/additional_software_packages.rb:39:in `click_gnome_shell_notification_button'
./features/step_definitions/additional_software_packages.rb:166:in `/^I can open the Additional Software log file from the notification$/'
features/additional_software_packages.feature:130:in `And I can open the Additional Software log file from the notification'
And the package "cowsay" is not installed 0.000
After features/support/hooks.rb:515 0.056
After features/support/hooks.rb:330 6.658

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/02:27:09_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/31/artifact/build-artifacts/02:27:09_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/31/artifact/build-artifacts/02:27:09_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/31/artifact/build-artifacts/02:27:09_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/31/artifact/build-artifacts/02:27:09_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/31/artifact/build-artifacts/02:27:09_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/31/artifact/build-artifacts/02:27:09_I_am_notified_when_Additional_Software_fails_to_install_a_package.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/02:27:09_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/31/artifact/build-artifacts/02:27:09_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal

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

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/03:06:36_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/31/artifact/build-artifacts/03:06:36_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/03:06:36_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/03:06:36_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal

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

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/03:29:28_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/31/artifact/build-artifacts/03:29:28_Upgrading_a_Tails_whose_signing_key_is_outdated.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/03:29:28_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/03:29:28_Upgrading_a_Tails_whose_signing_key_is_outdated.journal

After features/support/hooks.rb:100 0.000
33.720
Scenario Tails erases memory and shuts down on USB boot medium removal: persistent data
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.700
And I prepare Tails for memory erasure tests 0.748
And I fill a 128 MiB file with a known pattern on the persistent filesystem 18.526
And patterns cover at least 100 MiB in the guest's memory 3.745
90.348% of the expected size (100 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/emergency_shutdown.feature:51:in `And patterns cover at least 100 MiB in the guest's memory'
Output 1

Pattern coverage: 90.348% (90 MiB out of 100 MiB reference memory)

When I eject the boot medium 0.000
And I wait for Tails to finish wiping the memory 0.000
Then I find very few patterns in the guest's memory 0.000
And Tails eventually shuts down 0.000
After features/support/hooks.rb:330 5.190

SCENARIO FAILED: 'Tails erases memory and shuts down on USB boot medium removal: persistent data' (at time 03:33:49)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/03:33:49_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/03:33:49_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/03:33:49_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/03:33:49_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.journal

After features/support/hooks.rb:100 0.000
Tags: @product
2:55.546
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 13.195
And I corrupt the boot device's GPT backup header 0.477
And I power off the computer 0.325
When I start the computer 1.068
Then the computer boots Tails 1:52.097
When I log in to a new session 32.706
And all notifications have disappeared 15.363
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.311
<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.659

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/03:56:26_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/31/artifact/build-artifacts/03:56:26_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/03:56:26_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/03:56:26_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.journal

After features/support/hooks.rb:100 0.008
Tags: @product
2:51.820
Scenario Outline GPT backup corruption with a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 11.202
And I corrupt the boot device's GPT backup partition table 0.473
And I power off the computer 0.382
When I start the computer 0.985
Then the computer boots Tails 1:50.721
When I log in to a new session 35.828
And all notifications have disappeared 11.992
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.234
<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 5.934

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/03:59:26_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/03:59:26_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/03:59:26_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/03:59:26_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.journal

After features/support/hooks.rb:100 0.008
Tags: @product
3:53.909
Scenario GPT backup corruption without a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given a computer 0.199
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.041
And I plug USB drive "temp" 1.052
And I write the Tails USB image to disk "temp" 33.873
When I start Tails from USB drive "temp" with network unplugged 2:38.225
Then Tails is running from USB drive "temp" 0.398
And the Greeter forbids creating a persistent partition 0.096
When I log in to a new session 27.208
And all notifications have disappeared 12.570
Then I am recommended to reinstall Tails due to partitioning errors 0.243
<"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.266

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/04:03:26_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/31/artifact/build-artifacts/04:03:26_GPT_backup_corruption_without_a_persistent_partition.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/04:03:26_GPT_backup_corruption_without_a_persistent_partition.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/04:03:26_GPT_backup_corruption_without_a_persistent_partition.journal

After features/support/hooks.rb:100 0.153
Tags: @product
8.780
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.006
Steps
Given I have started Tails from DVD without network and logged in 8.648
Then the keys trusted by APT are valid for the next 3 months 0.131
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.492

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/04:13:46_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/31/artifact/build-artifacts/04:13:46_The_included_APT_repository_keys_are_up-to-date.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/04:13:46_The_included_APT_repository_keys_are_up-to-date.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/04:13:46_The_included_APT_repository_keys_are_up-to-date.journal

After features/support/hooks.rb:100 0.000
Feature: Localization
2:7.620
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 7.868
When I log in to a new session in French (fr) 42.254
Then the keyboard layout is set to "fr" 0.462
When the network is plugged 0.097
And Tor is ready 22.630
Then I successfully start the Unsafe Browser 16.242
And I kill the Unsafe Browser 7.710
When I enable the screen keyboard 0.115
Then the screen keyboard works in Tor Browser 30.237
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 8.526

SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#4)' (at time 04:31:57)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/04:31:57_Tails_is_localized_for_every_tier-1_language,_Examples___4_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/04:31:57_Tails_is_localized_for_every_tier-1_language,_Examples___4_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/04:31:57_Tails_is_localized_for_every_tier-1_language,_Examples___4_.journal

After features/support/hooks.rb:100 0.000
Tags: @source
7.435
Scenario All packages are up-to-date
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:532 0.000
Steps
Given I have the build manifest for the image under test 0.000
Then all packages listed in the build manifest are up-to-date 7.435
Command failed (pid 119236 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-trixie/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_feature-trixie/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_feature-trixie/tmp/tails-amd64-feature_trixie@82c99162c4+devel@beb2116f2f-20250616T2242Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_feature-trixie/tmp/tails-amd64-feature_trixie@82c99162c4+devel@beb2116f2f-20250616T2242Z.build-manifest
ERROR: linux-headers-6.12.31-amd64: the package was not found in any of the Debian suites
ERROR: linux-headers-6.12.31-common: the package was not found in any of the Debian suites
ERROR: linux-image-6.12.31-amd64: the package was not found in any of the Debian suites
ERROR: linux-kbuild-6.12.31: the package was not found in any of the Debian suites
INFO: Need to upgrade to a new APT snapshot:
  - linux (6.12.31-1) to Debian sid (6.12.32-1)
  - linux-signed-amd64 (6.12.31-1) to Debian sid (6.12.32+1)
 (CommandFailed)
/var/lib/jenkins/workspace/test_Tails_ISO_feature-trixie/features/support/helpers/misc_helpers.rb:321:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_feature-trixie/features/support/helpers/misc_helpers.rb:314:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_feature-trixie/features/support/helpers/misc_helpers.rb:314:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_feature-trixie/features/step_definitions/needed_package_updates.rb:8:in `/^all packages listed in the build manifest are up-to-date$/'
features/needed_package_updates.feature:12:in `Then all packages listed in the build manifest are up-to-date'
After features/support/hooks.rb:539 0.001
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.068
Scenario Tails Persistent Storage behave tests
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails from DVD and logged in with an administration password and the network is connected 1:16.068
The
The Dogtail init script raised: DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
STDOUT:

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

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:85:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:715:in `new'
./features/step_definitions/common_steps.rb:715:in `/^all notifications have disappeared$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ with\ an\ administration\ password\ and\ the\ network\ is\ connected$/'
features/persistence.feature:7:in `Given I have started Tails from DVD and logged in with an administration password and the network is connected'
And I update APT using apt 0.000
And I install "python3-behave" using apt 0.000
Then the Tails Persistent Storage behave tests pass 0.000
After features/support/hooks.rb:330 7.093

SCENARIO FAILED: 'Tails Persistent Storage behave tests' (at time 05:14:11)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/05:14:11_Tails_Persistent_Storage_behave_tests.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/05:14:11_Tails_Persistent_Storage_behave_tests.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/05:14:11_Tails_Persistent_Storage_behave_tests.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/05:14:11_Tails_Persistent_Storage_behave_tests.journal

After features/support/hooks.rb:100 0.000
Tags: @product @doc
2:15.068
Scenario Filesystem and I/O errors
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 9.089
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 7.481
And Tails detects disk read failures on the boot device 1.665
When I try to enable persistence 0.709
Then the Welcome Screen tells me that my hardware is probably failing 23.132
When I log in to a new session 46.429
And all notifications have disappeared 26.355
Then the Tor Browser starts 20.205
cannot find TorBrowserNewTabButton.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:479:in `/^the Tor Browser (?:has started|starts)$/'
features/persistence.feature:213:in `Then the Tor Browser starts'
And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:330 8.114

SCENARIO FAILED: 'Filesystem and I/O errors' (at time 06:02:01)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/06:02:01_Filesystem_and_I_O_errors.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/06:02:01_Filesystem_and_I_O_errors.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/06:02:01_Filesystem_and_I_O_errors.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/06:02:01_Filesystem_and_I_O_errors.journal

After features/support/hooks.rb:100 0.000
50.968
Scenario Chatting with some friend over XMPP
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 15.726
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 10.910
Then I see Pidgin's account manager window 3.491
When I create my XMPP account 20.839
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.030
After features/support/hooks.rb:330 6.269

SCENARIO FAILED: 'Chatting with some friend over XMPP' (at time 06:13:16)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/06:13:16_Chatting_with_some_friend_over_XMPP.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/06:13:16_Chatting_with_some_friend_over_XMPP.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/06:13:16_Chatting_with_some_friend_over_XMPP.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/06:13:16_Chatting_with_some_friend_over_XMPP.journal

After features/support/hooks.rb:100 0.000
49.261
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.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 14.195
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.006
Then I see Pidgin's account manager window 3.261
When I create my XMPP account 20.797
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.048
After features/support/hooks.rb:330 6.183

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/06:14:12_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/31/artifact/build-artifacts/06:14:12_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/06:14:12_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/31/artifact/build-artifacts/06:14:12_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.journal

After features/support/hooks.rb:100 0.000
48.375
Scenario Connecting to the tails multi-user chat with my XMPP account
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Before features/support/hooks.rb:507 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 13.372
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 10.819
Then I see Pidgin's account manager window 3.346
And I create my XMPP account 20.837
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.036
After features/support/hooks.rb:330 5.992

SCENARIO FAILED: 'Connecting to the tails multi-user chat with my XMPP account' (at time 06:15:07)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/06:15:07_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/31/artifact/build-artifacts/06:15:07_Connecting_to_the_tails_multi-user_chat_with_my_XMPP_account.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/06:15:07_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/31/artifact/build-artifacts/06:15:07_Connecting_to_the_tails_multi-user_chat_with_my_XMPP_account.journal

After features/support/hooks.rb:100 0.000
1:19.143
Scenario Using a persistent Pidgin configuration
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 without network from a USB drive with a persistent partition enabled and logged in 13.548
And the network is plugged 0.115
And Tor is ready 23.327
And available upgrades have been checked 1.113
And all notifications have disappeared 5.485
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 10.991
Then I see Pidgin's account manager window 3.609
When I create my XMPP account 20.951
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.879

SCENARIO FAILED: 'Using a persistent Pidgin configuration' (at time 06:16:32)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/06:16:32_Using_a_persistent_Pidgin_configuration.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/06:16:32_Using_a_persistent_Pidgin_configuration.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/06:16:32_Using_a_persistent_Pidgin_configuration.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/06:16:32_Using_a_persistent_Pidgin_configuration.journal

After features/support/hooks.rb:100 0.000
Tags: @product
8.860
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.040
Steps
Given I have started Tails from DVD without network and logged in 8.758
Then there are no unexpected messages of priority "err" or higher in the journal 0.102
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": "579",
    "_BOOT_ID": "1e8ac1313d7a410ea421f2a0c1efe6c8",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "579",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750116430758258",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "2022a94b4c534414abaf90b60ec7bf70",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=1bd3e862bedd48a49fefe62e7a2937f2;i=35a;b=1e8ac1313d7a410ea421f2a0c1efe6c8;m=c9ba21;t=637b8bc2bc811;x=72253451e903b2d1",
    "__MONOTONIC_TIMESTAMP": "13220385",
    "__REALTIME_TIMESTAMP": "1750116430759953",
    "__SEQNUM": "858",
    "__SEQNUM_ID": "1bd3e862bedd48a49fefe62e7a2937f2"
  },
  {
    "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": "579",
    "_BOOT_ID": "1e8ac1313d7a410ea421f2a0c1efe6c8",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "579",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750116430758289",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "2022a94b4c534414abaf90b60ec7bf70",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=1bd3e862bedd48a49fefe62e7a2937f2;i=35c;b=1e8ac1313d7a410ea421f2a0c1efe6c8;m=c9bab3;t=637b8bc2bc8a3;x=8ce6ab198027372",
    "__MONOTONIC_TIMESTAMP": "13220531",
    "__REALTIME_TIMESTAMP": "1750116430760099",
    "__SEQNUM": "860",
    "__SEQNUM_ID": "1bd3e862bedd48a49fefe62e7a2937f2"
  },
  {
    "MESSAGE": "The group `powerdev' does not exist.",
    "SYSLOG_IDENTIFIER": "adduser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "2172",
    "SYSLOG_TIMESTAMP": "Jun 16 23:27:18 ",
    "_BOOT_ID": "1e8ac1313d7a410ea421f2a0c1efe6c8",
    "_CAP_EFFECTIVE": "1ffffffffff",
    "_CMDLINE": "adduser",
    "_COMM": "adduser",
    "_EXE": "/usr/bin/perl",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "2172",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750116438956614",
    "_SYSTEMD_CGROUP": "/system.slice/live-config.service",
    "_SYSTEMD_INVOCATION_ID": "acd4317216fd4716b1fe91159414f4b2",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "live-config.service",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=1bd3e862bedd48a49fefe62e7a2937f2;i=404;b=1e8ac1313d7a410ea421f2a0c1efe6c8;m=146cc68;t=637b8bca8da57;x=80966328854fd919",
    "__MONOTONIC_TIMESTAMP": "21417064",
    "__REALTIME_TIMESTAMP": "1750116438956631",
    "__SEQNUM": "1028",
    "__SEQNUM_ID": "1bd3e862bedd48a49fefe62e7a2937f2"
  },
  {
    "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": "579",
    "_BOOT_ID": "1e8ac1313d7a410ea421f2a0c1efe6c8",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "579",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750116618769154",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "2022a94b4c534414abaf90b60ec7bf70",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=1bd3e862bedd48a49fefe62e7a2937f2;i=8b4;b=1e8ac1313d7a410ea421f2a0c1efe6c8;m=6474f13;t=637b8c760931b;x=c4d31a5dd4964b29",
    "__MONOTONIC_TIMESTAMP": "105336595",
    "__REALTIME_TIMESTAMP": "1750116618769179",
    "__SEQNUM": "2228",
    "__SEQNUM_ID": "1bd3e862bedd48a49fefe62e7a2937f2"
  },
  {
    "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": "579",
    "_BOOT_ID": "1e8ac1313d7a410ea421f2a0c1efe6c8",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "579",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750116618769561",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "2022a94b4c534414abaf90b60ec7bf70",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=1bd3e862bedd48a49fefe62e7a2937f2;i=8b6;b=1e8ac1313d7a410ea421f2a0c1efe6c8;m=6475095;t=637b8c760949e;x=ae608349ea48e488",
    "__MONOTONIC_TIMESTAMP": "105336981",
    "__REALTIME_TIMESTAMP": "1750116618769566",
    "__SEQNUM": "2230",
    "__SEQNUM_ID": "1bd3e862bedd48a49fefe62e7a2937f2"
  },
  {
    "MESSAGE": "The user `amnesia' is not a member of group `sudo'.",
    "SYSLOG_IDENTIFIER": "deluser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "8118",
    "SYSLOG_TIMESTAMP": "Jun 16 23:30:24 ",
    "_AUDIT_LOGINUID": "1000",
    "_AUDIT_SESSION": "4",
    "_BOOT_ID": "1e8ac1313d7a410ea421f2a0c1efe6c8",
    "_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": "8118",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750116624770581",
    "_SYSTEMD_CGROUP": "/user.slice/user-1000.slice/session-4.scope",
    "_SYSTEMD_INVOCATION_ID": "995ddbc55c014855855b862304c677fa",
    "_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=1bd3e862bedd48a49fefe62e7a2937f2;i=1239;b=1e8ac1313d7a410ea421f2a0c1efe6c8;m=6a2e40c;t=637b8c7bc2815;x=1fc07caf6cea850f",
    "__MONOTONIC_TIMESTAMP": "111338508",
    "__REALTIME_TIMESTAMP": "1750116624771093",
    "__SEQNUM": "4665",
    "__SEQNUM_ID": "1bd3e862bedd48a49fefe62e7a2937f2"
  }
].
<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.548

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/06:21:49_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/31/artifact/build-artifacts/06:21:49_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/06:21:49_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/31/artifact/build-artifacts/06:21:49_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.journal

After features/support/hooks.rb:100 0.000
Tags: @product
14.444
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.360
Then there are no unexpected messages of priority "err" or higher in the journal 0.084
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": "713",
    "_BOOT_ID": "a5fab3e959cb4ba28320193f5358a502",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "713",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750118639297202",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "632127375f1d485ea56096d3e192f37f",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=c49c08b46c6349c79241b994aa499034;i=388;b=a5fab3e959cb4ba28320193f5358a502;m=e3e42f;t=637b93fcf6421;x=318f3665b8f466fc",
    "__MONOTONIC_TIMESTAMP": "14935087",
    "__REALTIME_TIMESTAMP": "1750118639297569",
    "__SEQNUM": "904",
    "__SEQNUM_ID": "c49c08b46c6349c79241b994aa499034"
  },
  {
    "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": "713",
    "_BOOT_ID": "a5fab3e959cb4ba28320193f5358a502",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "713",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750118639297229",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "632127375f1d485ea56096d3e192f37f",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=c49c08b46c6349c79241b994aa499034;i=38a;b=a5fab3e959cb4ba28320193f5358a502;m=e3e592;t=637b93fcf6585;x=3e9e6f1ff3bc88b7",
    "__MONOTONIC_TIMESTAMP": "14935442",
    "__REALTIME_TIMESTAMP": "1750118639297925",
    "__SEQNUM": "906",
    "__SEQNUM_ID": "c49c08b46c6349c79241b994aa499034"
  },
  {
    "MESSAGE": "The group `powerdev' does not exist.",
    "SYSLOG_IDENTIFIER": "adduser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "2369",
    "SYSLOG_TIMESTAMP": "Jun 17 00:04:07 ",
    "_BOOT_ID": "a5fab3e959cb4ba28320193f5358a502",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "2369",
    "_RUNTIME_SCOPE": "system",
    "_SOURCE_REALTIME_TIMESTAMP": "1750118647097173",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=c49c08b46c6349c79241b994aa499034;i=416;b=a5fab3e959cb4ba28320193f5358a502;m=15b36d3;t=637b94046b6c5;x=5fe88e666c12aecd",
    "__MONOTONIC_TIMESTAMP": "22755027",
    "__REALTIME_TIMESTAMP": "1750118647117509",
    "__SEQNUM": "1046",
    "__SEQNUM_ID": "c49c08b46c6349c79241b994aa499034"
  },
  {
    "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": "713",
    "_BOOT_ID": "a5fab3e959cb4ba28320193f5358a502",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "713",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750118787378986",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "632127375f1d485ea56096d3e192f37f",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=c49c08b46c6349c79241b994aa499034;i=e74;b=a5fab3e959cb4ba28320193f5358a502;m=9858140;t=637b948a2f296;x=b79089b392875adf",
    "__MONOTONIC_TIMESTAMP": "159744320",
    "__REALTIME_TIMESTAMP": "1750118787379862",
    "__SEQNUM": "3700",
    "__SEQNUM_ID": "c49c08b46c6349c79241b994aa499034"
  },
  {
    "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": "713",
    "_BOOT_ID": "a5fab3e959cb4ba28320193f5358a502",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "713",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750118787380665",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "632127375f1d485ea56096d3e192f37f",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=c49c08b46c6349c79241b994aa499034;i=e76;b=a5fab3e959cb4ba28320193f5358a502;m=9858b47;t=637b948a2fc9e;x=2f1b2dd315fa3aa7",
    "__MONOTONIC_TIMESTAMP": "159746887",
    "__REALTIME_TIMESTAMP": "1750118787382430",
    "__SEQNUM": "3702",
    "__SEQNUM_ID": "c49c08b46c6349c79241b994aa499034"
  },
  {
    "MESSAGE": "The user `amnesia' is not a member of group `sudo'.",
    "SYSLOG_IDENTIFIER": "deluser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "12669",
    "SYSLOG_TIMESTAMP": "Jun 17 00:06:34 ",
    "_AUDIT_LOGINUID": "1000",
    "_AUDIT_SESSION": "4",
    "_BOOT_ID": "a5fab3e959cb4ba28320193f5358a502",
    "_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": "12669",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750118794417336",
    "_SYSTEMD_CGROUP": "/user.slice/user-1000.slice/session-4.scope",
    "_SYSTEMD_INVOCATION_ID": "c65cdd5fa82c4827a7006c43881787d5",
    "_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=c49c08b46c6349c79241b994aa499034;i=1870;b=a5fab3e959cb4ba28320193f5358a502;m=9f0e443;t=637b9490e559a;x=56126fae69572749",
    "__MONOTONIC_TIMESTAMP": "166782019",
    "__REALTIME_TIMESTAMP": "1750118794417562",
    "__SEQNUM": "6256",
    "__SEQNUM_ID": "c49c08b46c6349c79241b994aa499034"
  }
].
<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.156

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/06:22:09_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/31/artifact/build-artifacts/06:22:09_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/31/artifact/build-artifacts/06:22:09_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/31/artifact/build-artifacts/06:22:09_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.journal

After features/support/hooks.rb:100 0.000
Tags: @product
27.462
Scenario I can shutdown Tails via the system menu
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails from DVD and logged in and the network is connected 13.509
When I request a shutdown using the system menu 13.953
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.005

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/06:22:42_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/31/artifact/build-artifacts/06:22:42_I_can_shutdown_Tails_via_the_system_menu.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/06:22:42_I_can_shutdown_Tails_via_the_system_menu.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/06:22:42_I_can_shutdown_Tails_via_the_system_menu.journal

After features/support/hooks.rb:100 0.000
26.749
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 12.774
When I request a reboot using the system menu 13.975
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.328

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/06:23:14_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/31/artifact/build-artifacts/06:23:14_I_can_reboot_Tails_via_the_system_menu.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/06:23:14_I_can_reboot_Tails_via_the_system_menu.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/06:23:14_I_can_reboot_Tails_via_the_system_menu.journal

After features/support/hooks.rb:100 0.000
1:41.120
Scenario The Downloads directory is usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Before features/support/hooks.rb:507 0.007
Steps
Given I have started Tails from DVD and logged in and the network is connected 13.053
Then the live user's Downloads directory exists 0.081
And there is a GNOME bookmark for the Downloads directory 22.314
When I start the Tor Browser 26.820
And the Tor Browser loads the startup page 2.079
Then I can save the current page as "index.html" to the Downloads directory 36.771
The
The page was not saved to /home/amnesia/Downloads/index.html (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:546: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.036
After features/support/hooks.rb:330 5.586

SCENARIO FAILED: 'The Downloads directory is usable in Tor Browser' (at time 06:50:35)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/06:50:35_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/31/artifact/build-artifacts/06:50:35_The_Downloads_directory_is_usable_in_Tor_Browser.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/06:50:35_The_Downloads_directory_is_usable_in_Tor_Browser.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/06:50:35_The_Downloads_directory_is_usable_in_Tor_Browser.journal

After features/support/hooks.rb:100 0.000
Tags: @product
52.739
Scenario The Tor Browser uses TBB's shared libraries
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails from DVD and logged in and the network is connected 13.293
When I start the Tor Browser 30.919
Then the Tor Browser uses all expected TBB shared libraries 8.526
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.234

SCENARIO FAILED: 'The Tor Browser uses TBB's shared libraries' (at time 06:57:44)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/06:57:44_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/31/artifact/build-artifacts/06:57:44_The_Tor_Browser_uses_TBB_s_shared_libraries.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/06:57:44_The_Tor_Browser_uses_TBB_s_shared_libraries.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/06:57:44_The_Tor_Browser_uses_TBB_s_shared_libraries.journal

After features/support/hooks.rb:100 0.000
Tags: @product
2:7.400
Scenario The Persistent directory is usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.925
And the network is plugged 0.116
And I successfully configure Tor 24.882
And available upgrades have been checked 1.185
And all notifications have disappeared 5.502
And there is a GNOME bookmark for the Persistent directory 29.286
When I start the Tor Browser 23.862
And I download some file in the Tor Browser to the Persistent directory 29.639
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 9.727

SCENARIO FAILED: 'The Persistent directory is usable in Tor Browser' (at time 07:03:19)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/07:03:19_The_Persistent_directory_is_usable_in_Tor_Browser.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/07:03:19_The_Persistent_directory_is_usable_in_Tor_Browser.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/07:03:19_The_Persistent_directory_is_usable_in_Tor_Browser.journal

After features/support/hooks.rb:100 0.000
Tags: @product
1:10.383
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.007
Steps
Given I have started Tails from DVD without network and logged in 9.109
Then the live user's Documents directory exists 0.114
And there is a GNOME bookmark for the Documents directory 17.917
Then I start the Tor Browser in offline mode 20.639
And I can save the current page as "index.html" to the Documents GNOME bookmark 22.601
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: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 9.309

SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#1)' (at time 07:04:39)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/07:04:39_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/07:04:39_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/31/artifact/build-artifacts/07:04:39_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.journal

After features/support/hooks.rb:100 0.000
Tags: @product
1:17.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.007
Steps
Given I have started Tails from DVD without network and logged in 8.529
Then the live user's Downloads directory exists 0.161
And there is a GNOME bookmark for the Downloads directory 18.309
Then I start the Tor Browser in offline mode 22.908
And I can save the current page as "index.html" to the Downloads GNOME bookmark 27.660
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 8.859

SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#2)' (at time 07:06:06)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/07:06:06_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___2_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/07:06:06_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/31/artifact/build-artifacts/07:06:06_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___2_.journal

After features/support/hooks.rb:100 0.000
Tags: @product
1:12.984
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.007
Steps
Given I have started Tails from DVD without network and logged in 8.782
Then the live user's Music directory exists 0.171
And there is a GNOME bookmark for the Music directory 18.131
Then I start the Tor Browser in offline mode 22.531
And I can save the current page as "index.html" to the Music GNOME bookmark 23.366
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:129:in `And I can save the current page as "index.html" to the Music 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 9.242

SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#3)' (at time 07:07:28)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/07:07:28_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___3_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/07:07:28_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___3_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/07:07:28_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___3_.journal

After features/support/hooks.rb:100 0.000
Tags: @product
1:12.862
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.020
Steps
Given I have started Tails from DVD without network and logged in 8.991
Then the live user's Pictures directory exists 0.127
And there is a GNOME bookmark for the Pictures directory 18.426
Then I start the Tor Browser in offline mode 21.483
And I can save the current page as "index.html" to the Pictures GNOME bookmark 23.833
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 9.201

SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#4)' (at time 07:08:50)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/07:08:50_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___4_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/07:08:50_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/31/artifact/build-artifacts/07:08:50_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___4_.journal

After features/support/hooks.rb:100 0.000
Tags: @product
1:11.777
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.007
Steps
Given I have started Tails from DVD without network and logged in 8.857
Then the live user's Videos directory exists 0.106
And there is a GNOME bookmark for the Videos directory 18.024
Then I start the Tor Browser in offline mode 21.968
And I can save the current page as "index.html" to the Videos GNOME bookmark 22.820
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:131:in `And I can save the current page as "index.html" to the Videos 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 9.233

SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#5)' (at time 07:10:11)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/07:10:11_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___5_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/07:10:11_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___5_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/07:10:11_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___5_.journal

After features/support/hooks.rb:100 0.000
52.217
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.010
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.937
When I successfully start the Unsafe Browser 18.228
# 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.006

Slept for 10 seconds

And I try to start the Unsafe Browser 0.261
Then I see a warning about another instance already running 10.783
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 10.033

SCENARIO FAILED: 'Starting a second instance of the Unsafe Browser results in an error message being shown' (at time 07:24:52)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/07:24:52_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/31/artifact/build-artifacts/07:24:52_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/31/artifact/build-artifacts/07:24:52_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/31/artifact/build-artifacts/07:24:52_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.journal

After features/support/hooks.rb:100 0.000
20.924
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.123
And I cancel the GNOME authentication prompt 2.654
And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 6.569
And I open this VeraCrypt volume in GNOME Files 2.956
Then I see the expected contents in this VeraCrypt volume 0.443
When I lock the currently opened VeraCrypt volume 0.176
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.454

SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a USB drive that has a basic VeraCrypt volume' (at time 07:29:46)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/07:29:46_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/31/artifact/build-artifacts/07:29:46_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/31/artifact/build-artifacts/07:29:46_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/31/artifact/build-artifacts/07:29:46_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.journal

After features/support/hooks.rb:100 0.000
26.785
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.424
And I cancel the GNOME authentication prompt 2.318
And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 8.928
And I open this VeraCrypt volume in GNOME Files 3.582
Then I see the expected contents in this VeraCrypt volume 0.461
When I lock the currently opened VeraCrypt volume 0.069
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.621

SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a USB drive that has a hidden VeraCrypt volume' (at time 07:30:26)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/07:30:26_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/31/artifact/build-artifacts/07:30:26_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/31/artifact/build-artifacts/07:30:26_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/31/artifact/build-artifacts/07:30:26_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.journal

After features/support/hooks.rb:100 0.000
29.879
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.786
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 8.944
And I open this VeraCrypt volume in GNOME Files 3.630
Then I see the expected contents in this VeraCrypt volume 0.423
When I lock the currently opened VeraCrypt file container 0.094
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 5.538

SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a basic VeraCrypt file container with a PIM' (at time 07:31:11)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/07:31:11_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/31/artifact/build-artifacts/07:31:11_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/31/artifact/build-artifacts/07:31:11_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/31/artifact/build-artifacts/07:31:11_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.journal

After features/support/hooks.rb:100 0.000
40.875
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 26.856
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 10.148
And I open this VeraCrypt volume in GNOME Files 3.327
Then I see the expected contents in this VeraCrypt volume 0.447
When I lock the currently opened VeraCrypt file container 0.095
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 5.504

SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a hidden VeraCrypt file container' (at time 07:32:06)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/07:32:06_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/31/artifact/build-artifacts/07:32:06_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/07:32:06_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/31/artifact/build-artifacts/07:32:06_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.journal

After features/support/hooks.rb:100 0.017
25.848
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.163
And I cancel the GNOME authentication prompt 2.267
And I unlock and mount this VeraCrypt volume with GNOME Disks 11.905
And I open this VeraCrypt volume in GNOME Files 2.981
Then I see the expected contents in this VeraCrypt volume 0.417
When I lock the currently opened VeraCrypt volume 0.112
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 5.491

SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile' (at time 07:32:46)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/07:32:46_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/31/artifact/build-artifacts/07:32:46_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/31/artifact/build-artifacts/07:32:46_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/31/artifact/build-artifacts/07:32:46_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
27.546
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.419
And I cancel the GNOME authentication prompt 2.431
And I unlock and mount this VeraCrypt volume with GNOME Disks 9.886
And I open this VeraCrypt volume in GNOME Files 3.302
Then I see the expected contents in this VeraCrypt volume 0.418
When I lock the currently opened VeraCrypt volume 0.088
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.528

SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a hidden VeraCrypt volume' (at time 07:33:28)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/07:33:28_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/31/artifact/build-artifacts/07:33:28_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/31/artifact/build-artifacts/07:33:28_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/31/artifact/build-artifacts/07:33:28_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.journal

After features/support/hooks.rb:100 0.000
50.413
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 23.681
And I unlock and mount this VeraCrypt file container with GNOME Disks 23.281
And I open this VeraCrypt volume in GNOME Files 2.922
Then I see the expected contents in this VeraCrypt volume 0.438
When I lock the currently opened VeraCrypt file container 0.089
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 5.522

SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile' (at time 07:34:33)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/07:34:33_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/31/artifact/build-artifacts/07:34:33_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/31/artifact/build-artifacts/07:34:33_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/31/artifact/build-artifacts/07:34:33_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.journal

After features/support/hooks.rb:100 0.014
50.603
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 26.441
And I unlock and mount this VeraCrypt file container with GNOME Disks 20.378
And I open this VeraCrypt volume in GNOME Files 3.284
Then I see the expected contents in this VeraCrypt volume 0.423
When I lock the currently opened VeraCrypt file container 0.075
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.612

SCENARIO FAILED: 'Use GNOME Disks to unlock a hidden VeraCrypt file container' (at time 07:35:38)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/07:35: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/31/artifact/build-artifacts/07:35:38_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/07:35: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/31/artifact/build-artifacts/07:35:38_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.journal

After features/support/hooks.rb:100 0.019
40.123
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 16.518
And I unlock and mount this VeraCrypt file container with GNOME Disks 19.814
And I open this VeraCrypt volume in GNOME Files 3.249
Then I see the expected contents in this VeraCrypt volume 0.449
When I lock the currently opened VeraCrypt file container 0.091
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.475

SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a PIM' (at time 07:36:32)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/31/artifact/build-artifacts/07:36:32_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/31/artifact/build-artifacts/07:36:32_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/31/artifact/build-artifacts/07:36:32_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/31/artifact/build-artifacts/07:36:32_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.journal

After features/support/hooks.rb:100 0.000