Project Number Date
test_Tails_ISO_21019-fix-custom-package-versioning-scheme 1 17 Jun 2025, 20:56

Failures Overview

The following summary displays scenarios that failed.

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

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

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

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/00:44:23_Erasure_of_memory_freed_by_killed_userspace_processes.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/00:44:23_Erasure_of_memory_freed_by_killed_userspace_processes.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/00:44:23_Erasure_of_memory_freed_by_killed_userspace_processes.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/00:44:23_Erasure_of_memory_freed_by_killed_userspace_processes.journal

After features/support/hooks.rb:100 0.000
13:21.103
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.004
Before features/support/hooks.rb:507 0.005
Steps
Given I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login 1:37.125
And I update APT using apt 26.886
And I install "popularity-contest" using apt 26.853
Then I am proposed to add the "popularity-contest" package to my Additional Software 15.560
When I create a persistent storage and activate the Additional Software feature 30.065
Then Additional Software is correctly configured for package "popularity-contest" 4.780
When I shutdown Tails and wait for the computer to power off 16.620
And I start Tails from USB drive "__internal" with network unplugged 2:5.783
And I enable persistence 41.784
And I log in to a new session 1:0.658
And the Additional Software installation service has started 47.213
Then I am notified that the installation succeeded 5:7.770
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.046
After features/support/hooks.rb:330 8.362

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/01:40:39_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/01:40:39_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/01:40:39_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/01:40:39_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/01:40:39_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/01:40:39_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/01:40:39_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/01:40:39_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/01:40:39_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.journal

After features/support/hooks.rb:100 0.010
25:41.802
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.004
Before features/support/hooks.rb:507 0.003
Steps
Given a computer 0.248
And I start Tails from USB drive "__internal" and I login with an administration password 3:24.003
And I update APT using apt 11.826
When I install "makepp" using apt 22:5.723
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.049
After features/support/hooks.rb:330 7.392

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

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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/02:06:30_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/02:06:30_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/02:06:30_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/02:06:30_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/02:06:30_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/02:06:30_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/02:06:30_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/02:06:30_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal

After features/support/hooks.rb:100 0.039
11:33.784
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.016
Before features/support/hooks.rb:507 0.005
Steps
Given a computer 0.279
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 5:26.919
When I uninstall "popularity-contest" using apt 25.346
And I accept removing "popularity-contest" from Additional Software 3.050
Then "popularity-contest" is not in the list of Additional Software 2.924
When I start Synaptic 19.929
And I update APT using Synaptic 23.115
And I install "cowsay" using Synaptic 4:52.218
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.047
After features/support/hooks.rb:330 6.823

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/02:18:11_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/02:18:11_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/02:18:11_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/02:18:11_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/02:18:11_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/02:18:11_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/02:18:11_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/02:18:11_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/02:18:11_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.016
23:3.790
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.761
And no SquashFS delta is installed 0.113
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.689
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.136
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.328
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.616
When the network is plugged 0.079
And Tor is ready 30.228
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:14.834
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.683

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/03:20:25_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/03:20:25_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/03:20:25_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/03:20:25_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal

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

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/03:43:30_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/03:43:30_Upgrading_a_Tails_whose_signing_key_is_outdated.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/03:43:30_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/03:43:30_Upgrading_a_Tails_whose_signing_key_is_outdated.journal

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

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

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/03:53:31_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/03:53:31_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/03:53:31_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal

After features/support/hooks.rb:100 0.164
51.019
Scenario The Tails documentation launcher works when offline
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Steps
Given I have started Tails from DVD without network and logged in 9.635
When I start "Tails Documentation" via GNOME Activities Overview 10.226
Then the Tor Browser has started 31.157
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/documentation.feature:7:in `Then the Tor Browser has started'
Then "Tails - Documentation" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:330 12.890

SCENARIO FAILED: 'The Tails documentation launcher works when offline' (at time 03:56:12)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/03:56:12_The_Tails_documentation_launcher_works_when_offline.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/03:56:12_The_Tails_documentation_launcher_works_when_offline.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/03:56:12_The_Tails_documentation_launcher_works_when_offline.journal

After features/support/hooks.rb:100 0.000
Tags: @product
3:20.584
Scenario Outline GPT backup corruption with a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 17.055
And I corrupt the boot device's GPT backup header 0.462
And I power off the computer 0.601
When I start the computer 1.114
Then the computer boots Tails 2:3.698
When I log in to a new session 38.851
And all notifications have disappeared 18.557
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.243
<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.789

SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#1)' (at time 04:14:45)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/04:14:45_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/04:14:45_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/04:14:45_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/04:14:45_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.journal

After features/support/hooks.rb:100 0.138
Tags: @product
3:19.909
Scenario Outline GPT backup corruption with a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.051
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.379
And I corrupt the boot device's GPT backup partition table 0.444
And I power off the computer 0.341
When I start the computer 1.284
Then the computer boots Tails 2:12.938
When I log in to a new session 35.988
And all notifications have disappeared 13.811
Then I am recommended to migrate to a new USB stick due to partitioning errors 1.720
<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 7.421

SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#2)' (at time 04:18:13)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/04:18:13_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/04:18:13_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/04:18:13_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/04:18:13_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.journal

After features/support/hooks.rb:100 0.008
Tags: @product
4:43.752
Scenario GPT backup corruption without a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given a computer 0.201
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.043
And I write the Tails USB image to disk "temp" 43.281
When I start Tails from USB drive "temp" with network unplugged 3:5.161
Then Tails is running from USB drive "temp" 0.384
And the Greeter forbids creating a persistent partition 0.089
When I log in to a new session 35.679
And all notifications have disappeared 17.649
Then I am recommended to reinstall Tails due to partitioning errors 0.220
<"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.584

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/04:23:04_GPT_backup_corruption_without_a_persistent_partition.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/04:23:04_GPT_backup_corruption_without_a_persistent_partition.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/04:23:04_GPT_backup_corruption_without_a_persistent_partition.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/04:23:04_GPT_backup_corruption_without_a_persistent_partition.journal

After features/support/hooks.rb:100 0.122
Tags: @product
9.815
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.004
Steps
Given I have started Tails from DVD without network and logged in 9.664
Then the keys trusted by APT are valid for the next 3 months 0.151
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 7.940

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/04:35:47_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/04:35:47_The_included_APT_repository_keys_are_up-to-date.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/04:35:47_The_included_APT_repository_keys_are_up-to-date.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/04:35:47_The_included_APT_repository_keys_are_up-to-date.journal

After features/support/hooks.rb:100 0.000
Feature: Localization
2:29.463
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.526
When I log in to a new session in Arabic (ar) 55.843
Then the keyboard layout is set to "eg" 0.286
When the network is plugged 0.137
And Tor is ready 26.038
Then I successfully start the Unsafe Browser 20.217
And I kill the Unsafe Browser 7.879
When I enable the screen keyboard 0.217
Then the screen keyboard works in Tor Browser 30.316
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:43:in `Then the screen keyboard works in Tor Browser'
features/localization.feature:30:in `Then the screen keyboard works in Tor Browser'
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 9.102

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

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/04:45:54_Tails_is_localized_for_every_tier-1_language,_Examples___1_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/04:45:54_Tails_is_localized_for_every_tier-1_language,_Examples___1_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/04:45:54_Tails_is_localized_for_every_tier-1_language,_Examples___1_.journal

After features/support/hooks.rb:100 0.000
Feature: Localization
2:22.883
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.009
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 9.021
When I log in to a new session in French (fr) 50.676
Then the keyboard layout is set to "fr" 1.554
When the network is plugged 0.130
And Tor is ready 25.692
Then I successfully start the Unsafe Browser 17.637
And I kill the Unsafe Browser 7.489
When I enable the screen keyboard 0.179
Then the screen keyboard works in Tor Browser 30.501
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 10.847

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

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/04:55:15_Tails_is_localized_for_every_tier-1_language,_Examples___4_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/04:55:15_Tails_is_localized_for_every_tier-1_language,_Examples___4_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/04:55:15_Tails_is_localized_for_every_tier-1_language,_Examples___4_.journal

After features/support/hooks.rb:100 0.000
Feature: Localization
2:41.028
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.065
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 10.593
When I log in to a new session in Turkish (tr) 55.716
Then the keyboard layout is set to "tr" 0.447
When the network is plugged 0.173
And Tor is ready 25.729
Then I successfully start the Unsafe Browser 17.917
And I kill the Unsafe Browser 7.581
When I enable the screen keyboard 0.213
Then the screen keyboard works in Tor Browser 42.657
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/step_definitions/browser.rb:466: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:55:in `Then the screen keyboard works in Tor Browser'
features/localization.feature:30:in `Then the screen keyboard works in Tor Browser'
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 9.572

SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#13)' (at time 05:27:12)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/05:27:12_Tails_is_localized_for_every_tier-1_language,_Examples___13_.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/05:27:12_Tails_is_localized_for_every_tier-1_language,_Examples___13_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/05:27:12_Tails_is_localized_for_every_tier-1_language,_Examples___13_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/05:27:12_Tails_is_localized_for_every_tier-1_language,_Examples___13_.journal

After features/support/hooks.rb:100 0.000
Tags: @source
11.029
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 11.029
Command failed (pid 105078 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/tmp/tails-amd64-21019-fix-custom-package-versioning-scheme@bc9dc9cdb6+devel@beb2116f2f-20250617T1146Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/tmp/tails-amd64-21019-fix-custom-package-versioning-scheme@bc9dc9cdb6+devel@beb2116f2f-20250617T1146Z.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_21019-fix-custom-package-versioning-scheme/features/support/helpers/misc_helpers.rb:321:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/features/support/helpers/misc_helpers.rb:314:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/features/support/helpers/misc_helpers.rb:314:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/features/step_definitions/needed_package_updates.rb:8:in `/^all packages listed in the build manifest are up-to-date$/'
features/needed_package_updates.feature:12:in `Then all packages listed in the build manifest are up-to-date'
After features/support/hooks.rb:539 0.000
After features/support/hooks.rb:100 0.000
Tags: @product
15.562
Scenario Deleting a Tails persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 10.381
And I log in to a new session without activating the Persistent Storage 5.181
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/common_steps.rb:513:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
features/persistence.feature:128:in `And I log in to a new session without activating the Persistent Storage'
Then persistence is disabled 0.000
But a Tails persistence partition exists on USB drive "__internal" 0.000
And all notifications have disappeared 0.000
When I delete the persistent partition 0.000
Then there is no persistence partition on USB drive "__internal" 0.000
After features/support/hooks.rb:330 5.405

SCENARIO FAILED: 'Deleting a Tails persistent partition' (at time 06:19:16)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/06:19:16_Deleting_a_Tails_persistent_partition.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/06:19:16_Deleting_a_Tails_persistent_partition.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/06:19:16_Deleting_a_Tails_persistent_partition.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/06:19:16_Deleting_a_Tails_persistent_partition.journal

After features/support/hooks.rb:100 0.000
Tags: @product
16.167
Scenario No unexpected error messages in the journal after booting from DVD
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD without network and logged in 16.051
Then there are no unexpected messages of priority "err" or higher in the journal 0.116
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": "573",
    "_BOOT_ID": "135348e9651140829631d9164801f726",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "573",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750165190310646",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "a9a329098e0743fabe72c638aa861495",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=2670a6887692425bb2ee9b027261a83e;i=356;b=135348e9651140829631d9164801f726;m=e5a5b9;t=637c416777b06;x=60f543a18773993a",
    "__MONOTONIC_TIMESTAMP": "15050169",
    "__REALTIME_TIMESTAMP": "1750165190310662",
    "__SEQNUM": "854",
    "__SEQNUM_ID": "2670a6887692425bb2ee9b027261a83e"
  },
  {
    "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": "573",
    "_BOOT_ID": "135348e9651140829631d9164801f726",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "573",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750165190310828",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "a9a329098e0743fabe72c638aa861495",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=2670a6887692425bb2ee9b027261a83e;i=358;b=135348e9651140829631d9164801f726;m=e5a662;t=637c416777bb0;x=3fe32bff7869edfe",
    "__MONOTONIC_TIMESTAMP": "15050338",
    "__REALTIME_TIMESTAMP": "1750165190310832",
    "__SEQNUM": "856",
    "__SEQNUM_ID": "2670a6887692425bb2ee9b027261a83e"
  },
  {
    "MESSAGE": "The group `powerdev' does not exist.",
    "SYSLOG_IDENTIFIER": "adduser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "1985",
    "SYSLOG_TIMESTAMP": "Jun 17 12:59:59 ",
    "_BOOT_ID": "135348e9651140829631d9164801f726",
    "_CAP_EFFECTIVE": "1ffffffffff",
    "_CMDLINE": "adduser",
    "_COMM": "adduser",
    "_EXE": "/usr/bin/perl",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "1985",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750165199241038",
    "_SYSTEMD_CGROUP": "/system.slice/live-config.service",
    "_SYSTEMD_INVOCATION_ID": "f07bf09b386b4379835210f04e776c0e",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "live-config.service",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=2670a6887692425bb2ee9b027261a83e;i=405;b=135348e9651140829631d9164801f726;m=16dea1b;t=637c416ffbf68;x=aa98a9c47925c141",
    "__MONOTONIC_TIMESTAMP": "23980571",
    "__REALTIME_TIMESTAMP": "1750165199241064",
    "__SEQNUM": "1029",
    "__SEQNUM_ID": "2670a6887692425bb2ee9b027261a83e"
  },
  {
    "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": "573",
    "_BOOT_ID": "135348e9651140829631d9164801f726",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "573",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750165397935367",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "a9a329098e0743fabe72c638aa861495",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=2670a6887692425bb2ee9b027261a83e;i=8dc;b=135348e9651140829631d9164801f726;m=6ddec16;t=637c422d79553;x=9c56bdc280e0a771",
    "__MONOTONIC_TIMESTAMP": "115207190",
    "__REALTIME_TIMESTAMP": "1750165397935443",
    "__SEQNUM": "2268",
    "__SEQNUM_ID": "2670a6887692425bb2ee9b027261a83e"
  },
  {
    "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": "573",
    "_BOOT_ID": "135348e9651140829631d9164801f726",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "573",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750165397937048",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "a9a329098e0743fabe72c638aa861495",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=2670a6887692425bb2ee9b027261a83e;i=8de;b=135348e9651140829631d9164801f726;m=6ddf261;t=637c422d79ba0;x=26766cd14896e150",
    "__MONOTONIC_TIMESTAMP": "115208801",
    "__REALTIME_TIMESTAMP": "1750165397937056",
    "__SEQNUM": "2270",
    "__SEQNUM_ID": "2670a6887692425bb2ee9b027261a83e"
  },
  {
    "MESSAGE": "The user `amnesia' is not a member of group `sudo'.",
    "SYSLOG_IDENTIFIER": "deluser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "7252",
    "SYSLOG_TIMESTAMP": "Jun 17 13:03:24 ",
    "_AUDIT_LOGINUID": "1000",
    "_AUDIT_SESSION": "4",
    "_BOOT_ID": "135348e9651140829631d9164801f726",
    "_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": "7252",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750165404817623",
    "_SYSTEMD_CGROUP": "/user.slice/user-1000.slice/session-4.scope",
    "_SYSTEMD_INVOCATION_ID": "557e32d5d6324e7ba03247ad9facd229",
    "_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=2670a6887692425bb2ee9b027261a83e;i=1266;b=135348e9651140829631d9164801f726;m=746efa2;t=637c4234098e1;x=665ee74d9f4823ef",
    "__MONOTONIC_TIMESTAMP": "122089378",
    "__REALTIME_TIMESTAMP": "1750165404817633",
    "__SEQNUM": "4710",
    "__SEQNUM_ID": "2670a6887692425bb2ee9b027261a83e"
  }
].
<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 6.549

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/06:58:02_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/06:58:02_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/06:58:02_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/06:58:02_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.journal

After features/support/hooks.rb:100 0.000
Tags: @product
16.842
Scenario No unexpected error messages in the journal after booting from USB drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.752
Then there are no unexpected messages of priority "err" or higher in the journal 0.089
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": "704",
    "_BOOT_ID": "09821d38183d4e199fd88b13c851d908",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "704",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750167762490989",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "353cbcc18f104bebbbb77743a6ddffa9",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=413b8505e33648abaf30bb4b79e89f89;i=363;b=09821d38183d4e199fd88b13c851d908;m=fef69a;t=637c4afc7d6b0;x=3375f3f406d046d1",
    "__MONOTONIC_TIMESTAMP": "16709274",
    "__REALTIME_TIMESTAMP": "1750167762491056",
    "__SEQNUM": "867",
    "__SEQNUM_ID": "413b8505e33648abaf30bb4b79e89f89"
  },
  {
    "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": "704",
    "_BOOT_ID": "09821d38183d4e199fd88b13c851d908",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "704",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750167762491289",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "353cbcc18f104bebbbb77743a6ddffa9",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=413b8505e33648abaf30bb4b79e89f89;i=365;b=09821d38183d4e199fd88b13c851d908;m=fef788;t=637c4afc7d79e;x=244a058e1e5a0230",
    "__MONOTONIC_TIMESTAMP": "16709512",
    "__REALTIME_TIMESTAMP": "1750167762491294",
    "__SEQNUM": "869",
    "__SEQNUM_ID": "413b8505e33648abaf30bb4b79e89f89"
  },
  {
    "MESSAGE": "The group `powerdev' does not exist.",
    "SYSLOG_IDENTIFIER": "adduser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "2451",
    "SYSLOG_TIMESTAMP": "Jun 17 13:42:52 ",
    "_BOOT_ID": "09821d38183d4e199fd88b13c851d908",
    "_CAP_EFFECTIVE": "1ffffffffff",
    "_CMDLINE": "adduser",
    "_COMM": "adduser",
    "_EXE": "/usr/bin/perl",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "2451",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750167772746280",
    "_SYSTEMD_CGROUP": "/system.slice/live-config.service",
    "_SYSTEMD_INVOCATION_ID": "f2e93237026c4f7985793bb8a4870081",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "live-config.service",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=413b8505e33648abaf30bb4b79e89f89;i=419;b=09821d38183d4e199fd88b13c851d908;m=19b7220;t=637c4b0645236;x=9b860d5c062121ec",
    "__MONOTONIC_TIMESTAMP": "26964512",
    "__REALTIME_TIMESTAMP": "1750167772746294",
    "__SEQNUM": "1049",
    "__SEQNUM_ID": "413b8505e33648abaf30bb4b79e89f89"
  },
  {
    "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": "704",
    "_BOOT_ID": "09821d38183d4e199fd88b13c851d908",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "704",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750167936107015",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "353cbcc18f104bebbbb77743a6ddffa9",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=413b8505e33648abaf30bb4b79e89f89;i=ddb;b=09821d38183d4e199fd88b13c851d908;m=b0c205a;t=637c4ba21046d;x=e1233e1a79a4f51b",
    "__MONOTONIC_TIMESTAMP": "185344090",
    "__REALTIME_TIMESTAMP": "1750167936107629",
    "__SEQNUM": "3547",
    "__SEQNUM_ID": "413b8505e33648abaf30bb4b79e89f89"
  },
  {
    "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": "704",
    "_BOOT_ID": "09821d38183d4e199fd88b13c851d908",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "704",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750167936107341",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "353cbcc18f104bebbbb77743a6ddffa9",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=413b8505e33648abaf30bb4b79e89f89;i=ddd;b=09821d38183d4e199fd88b13c851d908;m=b0c21ba;t=637c4ba2105cc;x=e925b67866396751",
    "__MONOTONIC_TIMESTAMP": "185344442",
    "__REALTIME_TIMESTAMP": "1750167936107980",
    "__SEQNUM": "3549",
    "__SEQNUM_ID": "413b8505e33648abaf30bb4b79e89f89"
  },
  {
    "MESSAGE": "The user `amnesia' is not a member of group `sudo'.",
    "SYSLOG_IDENTIFIER": "deluser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "11907",
    "SYSLOG_TIMESTAMP": "Jun 17 13:45:46 ",
    "_AUDIT_LOGINUID": "1000",
    "_AUDIT_SESSION": "4",
    "_BOOT_ID": "09821d38183d4e199fd88b13c851d908",
    "_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": "11907",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750167946587753",
    "_SYSTEMD_CGROUP": "/user.slice/user-1000.slice/session-4.scope",
    "_SYSTEMD_INVOCATION_ID": "a27da8c075c34539871eb8faf945abc7",
    "_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=413b8505e33648abaf30bb4b79e89f89;i=17db;b=09821d38183d4e199fd88b13c851d908;m=bac0a78;t=637c4bac0ee8b;x=c165c2bf6ce4ab36",
    "__MONOTONIC_TIMESTAMP": "195824248",
    "__REALTIME_TIMESTAMP": "1750167946587787",
    "__SEQNUM": "6107",
    "__SEQNUM_ID": "413b8505e33648abaf30bb4b79e89f89"
  }
].
<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.444

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/06:58:25_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/06:58:25_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/06:58:25_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/06:58:25_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.journal

After features/support/hooks.rb:100 0.000
Tags: @product
29.828
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 15.495
When I request a shutdown using the system menu 14.333
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 5.644

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/06:59:00_I_can_shutdown_Tails_via_the_system_menu.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/06:59:00_I_can_shutdown_Tails_via_the_system_menu.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/06:59:00_I_can_shutdown_Tails_via_the_system_menu.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/06:59:00_I_can_shutdown_Tails_via_the_system_menu.journal

After features/support/hooks.rb:100 0.000
29.282
Scenario I can reboot 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 15.096
When I request a reboot using the system menu 14.186
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.000

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/06:59:35_I_can_reboot_Tails_via_the_system_menu.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/06:59:35_I_can_reboot_Tails_via_the_system_menu.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/06:59:35_I_can_reboot_Tails_via_the_system_menu.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/06:59:35_I_can_reboot_Tails_via_the_system_menu.journal

After features/support/hooks.rb:100 0.000
1:26.996
Scenario The Downloads directory is usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Before features/support/hooks.rb:507 0.004
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.699
Then the live user's Downloads directory exists 0.173
And there is a GNOME bookmark for the Downloads directory 21.751
When I start the Tor Browser 29.902
And the Tor Browser loads the startup page 3.697
Then I can save the current page as "index.html" to the Downloads directory 18.772
The
The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'org.gnome.Nautilus' application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/browser.rb:6:in `new'
./features/step_definitions/browser.rb:6:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:38:in `browser_save_page_as'
./features/step_definitions/browser.rb:543:in `/^I (can|cannot) save the current page as "([^"]+[.]html)" to the (.*) (directory|GNOME bookmark)$/'
features/torified_browsing.feature:24:in `Then I can save the current page as "index.html" to the Downloads directory'
And I can print the current page as "output.pdf" to the Downloads directory 0.000
After features/support/hooks.rb:515 0.033
After features/support/hooks.rb:330 9.821

SCENARIO FAILED: 'The Downloads directory is usable in Tor Browser' (at time 07:15:46)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:15:46_The_Downloads_directory_is_usable_in_Tor_Browser.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:15:46_The_Downloads_directory_is_usable_in_Tor_Browser.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:15:46_The_Downloads_directory_is_usable_in_Tor_Browser.journal

After features/support/hooks.rb:100 0.000
1:19.889
Scenario Downloading files with the Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Before features/support/hooks.rb:507 0.010
Steps
Given I have started Tails from DVD and logged in and the network is connected 13.082
When I start the Tor Browser 31.340
Then the Tor Browser loads the startup page 2.441
When I download some file in the Tor Browser to the Downloads directory 33.025
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:32:in `When I download some file in the Tor Browser to the Downloads directory'
Then the file is saved to the Downloads directory 0.000
After features/support/hooks.rb:515 0.038
After features/support/hooks.rb:330 9.294

SCENARIO FAILED: 'Downloading files with the Tor Browser' (at time 07:17:16)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:17:16_Downloading_files_with_the_Tor_Browser.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:17:16_Downloading_files_with_the_Tor_Browser.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:17:16_Downloading_files_with_the_Tor_Browser.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:17:16_Downloading_files_with_the_Tor_Browser.journal

After features/support/hooks.rb:100 0.000
Tags: @product
53.731
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 14.340
When I start the Tor Browser 32.511
Then the Tor Browser uses all expected TBB shared libraries 6.880
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.603

SCENARIO FAILED: 'The Tor Browser uses TBB's shared libraries' (at time 07:23:45)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:23:45_The_Tor_Browser_uses_TBB_s_shared_libraries.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:23:45_The_Tor_Browser_uses_TBB_s_shared_libraries.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:23:45_The_Tor_Browser_uses_TBB_s_shared_libraries.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:23:45_The_Tor_Browser_uses_TBB_s_shared_libraries.journal

After features/support/hooks.rb:100 0.000
Tags: @product
2:20.573
Scenario The Persistent directory is usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.773
And the network is plugged 0.113
And I successfully configure Tor 27.384
And available upgrades have been checked 0.061
And all notifications have disappeared 5.833
And there is a GNOME bookmark for the Persistent directory 21.533
When I start the Tor Browser 35.227
And I download some file in the Tor Browser to the Persistent directory 32.645
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 11.134

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:30:11_The_Persistent_directory_is_usable_in_Tor_Browser.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:30:11_The_Persistent_directory_is_usable_in_Tor_Browser.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:30:11_The_Persistent_directory_is_usable_in_Tor_Browser.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:30:11_The_Persistent_directory_is_usable_in_Tor_Browser.journal

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

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

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:31:41_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:31:41_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:31:41_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.journal

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

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

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:33:12_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___2_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:33:12_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___2_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:33:12_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___2_.journal

After features/support/hooks.rb:100 0.000
Tags: @product
1:20.441
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD without network and logged in 11.726
Then the live user's Music directory exists 0.145
And there is a GNOME bookmark for the Music directory 18.574
Then I start the Tor Browser in offline mode 28.014
And I can save the current page as "index.html" to the Music GNOME bookmark 21.980
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 12.521

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

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:34:45_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___3_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:34:45_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___3_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:34:45_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___3_.journal

After features/support/hooks.rb:100 0.000
Tags: @product
1:23.116
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD without network and logged in 10.446
Then the live user's Pictures directory exists 0.155
And there is a GNOME bookmark for the Pictures directory 21.526
Then I start the Tor Browser in offline mode 26.755
And I can save the current page as "index.html" to the Pictures GNOME bookmark 24.232
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.541

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

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:36:20_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___4_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:36:20_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___4_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:36:20_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___4_.journal

After features/support/hooks.rb:100 0.000
Tags: @product
1:22.262
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 12.129
Then the live user's Videos directory exists 0.162
And there is a GNOME bookmark for the Videos directory 18.396
Then I start the Tor Browser in offline mode 24.446
And I can save the current page as "index.html" to the Videos GNOME bookmark 27.127
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 11.902

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

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:37:52_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___5_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:37:52_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___5_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:37:52_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___5_.journal

After features/support/hooks.rb:100 0.000
1:1.520
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.021
Steps
Given I have started Tails from DVD and logged in and the network is connected 13.122
When I successfully start the Unsafe Browser 23.447
# 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.007

Slept for 10 seconds

And I try to start the Unsafe Browser 0.364
Then I see a warning about another instance already running 14.577
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.071

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

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:54:00_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:54:00_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:54:00_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.journal

After features/support/hooks.rb:100 0.000
25.288
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.327
And I cancel the GNOME authentication prompt 2.436
And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 8.931
And I open this VeraCrypt volume in GNOME Files 4.953
Then I see the expected contents in this VeraCrypt volume 0.508
When I lock the currently opened VeraCrypt volume 0.131
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 6.937

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:59:02_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:59:02_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:59:02_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:59:02_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.journal

After features/support/hooks.rb:100 0.000
30.425
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 12.991
And I cancel the GNOME authentication prompt 3.294
And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 8.969
And I open this VeraCrypt volume in GNOME Files 4.614
Then I see the expected contents in this VeraCrypt volume 0.463
When I lock the currently opened VeraCrypt volume 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: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 7.893

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:59:51_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:59:51_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:59:51_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/07:59:51_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.journal

After features/support/hooks.rb:100 0.001
37.316
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 20.595
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 12.359
And I open this VeraCrypt volume in GNOME Files 3.812
Then I see the expected contents in this VeraCrypt volume 0.456
When I lock the currently opened VeraCrypt file container 0.093
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 7.182

SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a basic VeraCrypt file container with a PIM' (at time 08:00:46)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/08:00:46_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/08:00:46_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/08:00:46_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/08:00:46_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.journal

After features/support/hooks.rb:100 0.002
47.783
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 32.126
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 11.165
And I open this VeraCrypt volume in GNOME Files 3.956
Then I see the expected contents in this VeraCrypt volume 0.425
When I lock the currently opened VeraCrypt file container 0.108
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 9.842

SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a hidden VeraCrypt file container' (at time 08:01:51)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/08:01:51_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/08:01:51_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/08:01:51_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/08:01:51_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.journal

After features/support/hooks.rb:100 0.017
29.725
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.961
And I cancel the GNOME authentication prompt 2.990
And I unlock and mount this VeraCrypt volume with GNOME Disks 12.253
And I open this VeraCrypt volume in GNOME Files 4.923
Then I see the expected contents in this VeraCrypt volume 0.475
When I lock the currently opened VeraCrypt volume 0.119
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/veracrypt.rb:330:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:54:in `When I lock the currently opened VeraCrypt volume'
Then the VeraCrypt volume has been unmounted and locked 0.000
After features/support/hooks.rb:330 6.441

SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile' (at time 08:02:40)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/08:02:40_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/08:02:40_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/08:02:40_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/08:02:40_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
30.917
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.544
And I cancel the GNOME authentication prompt 2.660
And I unlock and mount this VeraCrypt volume with GNOME Disks 11.877
And I open this VeraCrypt volume in GNOME Files 4.295
Then I see the expected contents in this VeraCrypt volume 0.447
When I lock the currently opened VeraCrypt volume 0.092
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 7.482

SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a hidden VeraCrypt volume' (at time 08:03:27)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/08:03:27_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/08:03:27_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/08:03:27_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/08:03:27_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.journal

After features/support/hooks.rb:100 0.001
56.257
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 25.687
And I unlock and mount this VeraCrypt file container with GNOME Disks 25.581
And I open this VeraCrypt volume in GNOME Files 4.304
Then I see the expected contents in this VeraCrypt volume 0.514
When I lock the currently opened VeraCrypt file container 0.169
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/veracrypt.rb:330:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:71:in `When I lock the currently opened VeraCrypt file container'
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 6.761

SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile' (at time 08:04:41)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/08:04:41_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/08:04:41_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/08:04:41_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/08:04:41_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.journal

After features/support/hooks.rb:100 0.044
57.197
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 30.168
And I unlock and mount this VeraCrypt file container with GNOME Disks 22.015
And I open this VeraCrypt volume in GNOME Files 4.611
Then I see the expected contents in this VeraCrypt volume 0.308
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: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 6.639

SCENARIO FAILED: 'Use GNOME Disks to unlock a hidden VeraCrypt file container' (at time 08:05:58)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/08:05:58_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/08:05:58_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/08:05:58_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/08:05:58_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.journal

After features/support/hooks.rb:100 0.014
46.237
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 19.724
And I unlock and mount this VeraCrypt file container with GNOME Disks 20.946
And I open this VeraCrypt volume in GNOME Files 4.949
Then I see the expected contents in this VeraCrypt volume 0.536
When I lock the currently opened VeraCrypt file container 0.080
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 6.687

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/08:07:02_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/08:07:02_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/08:07:02_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_21019-fix-custom-package-versioning-scheme/1/artifact/build-artifacts/08:07:02_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.journal

After features/support/hooks.rb:100 0.000