Cucumber Reports (no 2) - Failures Overview

Project	Number	Date
test_Tails_ISO_21019-fix-custom-package-versioning-scheme	2	18 Jun 2025, 16:38

Feature: System memory erasure on shutdown

15.229

Scenario Erasure of memory freed by killed userspace processes

Hooks

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.188

And I prepare Tails for memory erasure tests 0.467

When I start a process allocating 128 MiB of memory with a known pattern 1.438

Then patterns cover at least 128 MiB in the guest's memory 4.134

99.610%

99.610% of the expected size (128 MiB) has the pattern, but more than 100.000% was expected.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/erase_memory.rb:186:in `/^patterns cover at least (\d+) MiB in the guest's memory$/'
features/erase_memory.feature:17:in `Then patterns cover at least 128 MiB in the guest's memory'

Output 1

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

When I kill the allocating process 0.000

Then I find very few patterns in the guest's memory after 5 seconds 0.000

Hooks

After features/support/hooks.rb:330 5.309

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/00:38:24_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/2/artifact/build-artifacts/00:38:24_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/2/artifact/build-artifacts/00:38:24_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/2/artifact/build-artifacts/00:38:24_Erasure_of_memory_freed_by_killed_userspace_processes.journal

After features/support/hooks.rb:100 0.000

Feature: Additional software

Tags: @product @check_tor_leaks @slow

6:39.871

Scenario I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails

Hooks

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:27.002

And I update APT using apt 58.976

And I install "popularity-contest" using apt 27.895

Then I am proposed to add the "popularity-contest" package to my Additional Software 14.125

When I create a persistent storage and activate the Additional Software feature 31.134

Then Additional Software is correctly configured for package "popularity-contest" 3.118

When I shutdown Tails and wait for the computer to power off 15.651

And I start Tails from USB drive "__internal" with network unplugged 1:53.834

And I enable persistence 33.047

And I log in to a new session 15.083

can

can not find any of the patterns ["TailsGreeterLoginButton.png", "TailsGreeterLoginButtonGerman.png"] on the screen (FindFailed)
./features/support/helpers/screen.rb:248:in `rescue in wait_any'
./features/support/helpers/screen.rb:232:in `wait_any'
./features/step_definitions/common_steps.rb:491: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/additional_software_packages.feature:37:in `And I log in to a new session'

And the Additional Software installation service has started 0.000

Then I am notified that the installation succeeded 0.000

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

Hooks

After features/support/hooks.rb:515 0.033

After features/support/hooks.rb:330 7.569

Output 1

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:23:34)

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/2/artifact/build-artifacts/01:23:34_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

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/2/artifact/build-artifacts/01:23:34_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/2/artifact/build-artifacts/01:23:34_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/2/artifact/build-artifacts/01:23:34_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/2/artifact/build-artifacts/01:23:34_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/2/artifact/build-artifacts/01:23:34_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/2/artifact/build-artifacts/01:23:34_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/2/artifact/build-artifacts/01:23:34_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.011

Feature: Additional software

Tags: @product @check_tor_leaks @slow

25:25.448

Scenario The Additional Software dpkg hook notices when persistence is locked down while installing a package

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.009

Before features/support/hooks.rb:507 0.014

Steps

Given a computer 0.181

And I start Tails from USB drive "__internal" and I login with an administration password 3:6.538

And I update APT using apt 11.504

When I install "makepp" using apt 22:7.224

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

Hooks

After features/support/hooks.rb:515 0.045

After features/support/hooks.rb:330 5.351

Output 1

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

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/2/artifact/build-artifacts/01:49:07_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/2/artifact/build-artifacts/01:49:07_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/2/artifact/build-artifacts/01:49:07_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/2/artifact/build-artifacts/01:49:07_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/2/artifact/build-artifacts/01:49:07_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/2/artifact/build-artifacts/01:49:07_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/2/artifact/build-artifacts/01:49:07_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/2/artifact/build-artifacts/01:49:07_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal

After features/support/hooks.rb:100 0.012

Feature: Additional software

Tags: @product @check_tor_leaks @slow

10:54.592

Scenario My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.006

Before features/support/hooks.rb:507 0.006

Steps

Given a computer 0.420

And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 5:7.659

When I uninstall "popularity-contest" using apt 25.126

And I accept removing "popularity-contest" from Additional Software 2.934

Then "popularity-contest" is not in the list of Additional Software 0.863

When I start Synaptic 16.878

And I update APT using Synaptic 21.741

And I install "cowsay" using Synaptic 4:38.967

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

Hooks

After features/support/hooks.rb:515 0.043

After features/support/hooks.rb:330 6.023

Output 1

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:00:07)

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

Feature: Additional software

Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited

3:33.911

Scenario I am notified when Additional Software fails to install a package

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.003

Before features/support/hooks.rb:507 0.003

Steps

Given a computer 0.154

And I start Tails from USB drive "__internal" with network unplugged 2:1.420

And I enable persistence 19.094

And I remove the "cowsay" deb files from the APT cache 0.057

# Prevent the "Warning: virtual machine detected!" notification from racing

# with the one we'll be interacting with below.

And I disable the tails-virt-notify-user.service user unit 0.089

And I log in to a new session 40.396

Then I see the "The installation of your additional software failed" notification after at most 300 seconds 21.443

And I can open the Additional Software log file from the notification 11.255

The

The Dogtail init script raised: SearchError: descendant of [notification | ]: child with name='Show Log' roleName='button'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/additional_software_packages.rb:39:in `click_gnome_shell_notification_button'
./features/step_definitions/additional_software_packages.rb:166:in `/^I can open the Additional Software log file from the notification$/'
features/additional_software_packages.feature:130:in `And I can open the Additional Software log file from the notification'

And the package "cowsay" is not installed 0.000

Hooks

After features/support/hooks.rb:515 0.043

After features/support/hooks.rb:330 7.947

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/02:18:30_I_am_notified_when_Additional_Software_fails_to_install_a_package.file_content_var_log_boot.log

Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/02:18:30_I_am_notified_when_Additional_Software_fails_to_install_a_package.file_content_run_live-additional-software_log

Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/02:18:30_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_persistent_volume

Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/02:18:30_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_var_cache_apt

Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/02:18:30_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_var_lib_apt

Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/02:18:30_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_mount

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/02:18:30_I_am_notified_when_Additional_Software_fails_to_install_a_package.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/02:18:30_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/02:18:30_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal

After features/support/hooks.rb:100 0.009

Feature: Upgrading an old Tails USB installation

Tags: @product @automatic_upgrade

22:58.179

Scenario Upgrading an initial Tails installation with an incremental upgrade

Hooks

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 15.637

And no SquashFS delta is installed 1.512

And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.872

And Tails is fooled to think it is running version 6.0~testoverlayfs 0.230

And the file system changes introduced in version 6.2~testoverlayfs are not present 0.427

And the file system changes introduced in version 6.3~testoverlayfs are not present 0.567

When the network is plugged 0.073

And Tor is ready 24.423

Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:14.436

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

Hooks

After features/support/hooks.rb:330 6.120

Output 1

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

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

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/03:01:29_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/2/artifact/build-artifacts/03:01:29_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/2/artifact/build-artifacts/03:01:29_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal

After features/support/hooks.rb:100 0.000

Feature: Upgrading an old Tails USB installation

Tags: @product @automatic_upgrade

22:53.005

Scenario Upgrading a Tails whose signing key is outdated

Hooks

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 12.437

And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.787

And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061

And the signing key used by the Upgrader is outdated 0.113

But a current signing key is available on our website 0.000

When the network is plugged 0.113

And Tor is ready 25.236

Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:14.254

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'

Hooks

After features/support/hooks.rb:330 5.944

Output 1

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

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

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/03:24:28_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/2/artifact/build-artifacts/03:24:28_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/2/artifact/build-artifacts/03:24:28_Upgrading_a_Tails_whose_signing_key_is_outdated.journal

After features/support/hooks.rb:100 0.000

Feature: Hardware failures

Tags: @product

3:20.810

Scenario Outline GPT backup corruption with a persistent partition

Hooks

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.107

And I corrupt the boot device's GPT backup header 0.391

And I power off the computer 0.536

When I start the computer 1.126

Then the computer boots Tails 2:10.219

When I log in to a new session 34.332

And all notifications have disappeared 16.834

Then I am recommended to migrate to a new USB stick due to partitioning errors 0.264

<nil>

<nil> was expected to not be nil. (Test::Unit::AssertionFailedError)
./features/step_definitions/hardware.rb:84:in `/^I am recommended to migrate to a new USB stick due to partitioning errors$/'
features/hardware_failure.feature:45:in `Then I am recommended to migrate to a new USB stick due to partitioning errors'
features/hardware_failure.feature:41:in `Then I am recommended to migrate to a new USB stick due to partitioning errors'

And Tails detected partitioning error partitioning-corruption 0.000

Hooks

After features/support/hooks.rb:330 7.105

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/03:56:40_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/2/artifact/build-artifacts/03:56:40_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/2/artifact/build-artifacts/03:56:40_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/2/artifact/build-artifacts/03:56:40_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.journal

After features/support/hooks.rb:100 0.011

Feature: Hardware failures

Tags: @product

3:14.716

Scenario Outline GPT backup corruption with a persistent partition

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.006

Steps

Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 12.231

And I corrupt the boot device's GPT backup partition table 0.466

And I power off the computer 0.554

When I start the computer 1.206

Then the computer boots Tails 2:5.374

When I log in to a new session 35.347

And all notifications have disappeared 19.164

Then I am recommended to migrate to a new USB stick due to partitioning errors 0.369

<nil>

<nil> was expected to not be nil. (Test::Unit::AssertionFailedError)
./features/step_definitions/hardware.rb:84:in `/^I am recommended to migrate to a new USB stick due to partitioning errors$/'
features/hardware_failure.feature:46:in `Then I am recommended to migrate to a new USB stick due to partitioning errors'
features/hardware_failure.feature:41:in `Then I am recommended to migrate to a new USB stick due to partitioning errors'

And Tails detected partitioning error partitioning-corruption 0.000

Hooks

After features/support/hooks.rb:330 8.883

Output 1

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

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

After features/support/hooks.rb:100 0.007

Feature: Hardware failures

Tags: @product

4:26.040

Scenario GPT backup corruption without a persistent partition

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.004

Steps

Given a computer 0.248

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.043

And I plug USB drive "temp" 1.047

And I write the Tails USB image to disk "temp" 40.378

When I start Tails from USB drive "temp" with network unplugged 2:49.992

Then Tails is running from USB drive "temp" 0.422

And the Greeter forbids creating a persistent partition 0.108

When I log in to a new session 33.101

And all notifications have disappeared 20.178

Then I am recommended to reinstall Tails due to partitioning errors 0.519

<"OK">

<"OK"> was expected to include
<"Creation of Persistent Storage has been disabled">. (Test::Unit::AssertionFailedError)
./features/step_definitions/hardware.rb:94:in `/^I am recommended to reinstall Tails due to partitioning errors$/'
features/hardware_failure.feature:59:in `Then I am recommended to reinstall Tails due to partitioning errors'

# We are gonna verify the dialog again so we need to clean up the

# first instance.

And I close the "zenity" window 0.000

And I am told that Persistent Storage cannot be created 0.000

And Tails detected partitioning error partitioning-corruption 0.000

Hooks

After features/support/hooks.rb:330 6.551

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/04:04:37_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/2/artifact/build-artifacts/04:04:37_GPT_backup_corruption_without_a_persistent_partition.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/04:04:37_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/2/artifact/build-artifacts/04:04:37_GPT_backup_corruption_without_a_persistent_partition.journal

After features/support/hooks.rb:100 0.118

Feature: Tails-related cryptographic keys are up-to-date

Tags: @product

9.244

Scenario The included APT repository keys are up-to-date

Hooks

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.184

Then the keys trusted by APT are valid for the next 3 months 0.060

Command

Command failed: apt-key adv --batch --with-colons --fingerprint --list-key
error code: 127
stdout: 
stderr: /bin/sh: 1: apt-key: not found
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/checks.rb:19:in `assert_all_keys_are_valid_for_n_months'
./features/step_definitions/checks.rb:8:in `/^the keys trusted by APT are valid for the next (\d+) months$/'
features/keys.feature:11:in `Then the keys trusted by APT are valid for the next 3 months'

Hooks

After features/support/hooks.rb:330 5.500

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/04:16:24_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/2/artifact/build-artifacts/04:16:24_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/2/artifact/build-artifacts/04:16:24_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/2/artifact/build-artifacts/04:16:24_The_included_APT_repository_keys_are_up-to-date.journal

After features/support/hooks.rb:100 0.000

Feature: Localization

Tags: @product @doc @slow @not_release_blocker

2:56.244

Scenario Outline Tails is localized for every tier-1 language

Hooks

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 stopped at Tails Greeter's login screen 12.195

When I log in to a new session in Indonesian (id) 45.312

Then the keyboard layout is set to "id" 0.335

When the network is plugged 0.106

And Tor is ready 30.501

Then I successfully start the Unsafe Browser 1:27.792

cannot

cannot find UnsafeBrowserStartPage.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/unsafe_browser.rb:63:in `/^the Unsafe Browser shows a warning as its start page$/'
./features/step_definitions/unsafe_browser.rb:71:in `/^the Unsafe Browser has started$/'
./features/step_definitions/browser.rb:90:in `/^I successfully start the Unsafe Browser$/'
features/localization.feature:49:in `Then I successfully start the Unsafe Browser'
features/localization.feature:27:in `Then I successfully start the Unsafe Browser'

And I kill the Unsafe Browser 0.000

When I enable the screen keyboard 0.000

Then the screen keyboard works in Tor Browser 0.000

And DuckDuckGo is the default search engine 0.000

And I kill the Tor Browser 0.000

And the screen keyboard works in Thunderbird 0.000

And the layout of the screen keyboard is set to "us" 0.000

Hooks

After features/support/hooks.rb:330 11.978

Output 1

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

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/04:50:37_Tails_is_localized_for_every_tier-1_language,_Examples___7_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/04:50:37_Tails_is_localized_for_every_tier-1_language,_Examples___7_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/04:50:37_Tails_is_localized_for_every_tier-1_language,_Examples___7_.journal

After features/support/hooks.rb:100 0.000

Feature: Localization

Tags: @product @doc @slow @not_release_blocker

2:25.294

Scenario Outline Tails is localized for every tier-1 language

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.005

Steps

Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 9.466

When I log in to a new session in Persian (fa) 49.228

Then the keyboard layout is set to "ir" 1.499

When the network is plugged 0.091

And Tor is ready 25.686

Then I successfully start the Unsafe Browser 21.476

And I kill the Unsafe Browser 7.214

When I enable the screen keyboard 0.199

Then the screen keyboard works in Tor Browser 30.431

try_for()

try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:1040:in `launch_app'
./features/step_definitions/common_steps.rb:1095:in `launch_tor_browser'
./features/step_definitions/browser.rb:456:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:422:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:51:in `Then the screen keyboard works in Tor Browser'
features/localization.feature:30:in `Then the screen keyboard works in Tor Browser'

And DuckDuckGo is the default search engine 0.000

And I kill the Tor Browser 0.000

And the screen keyboard works in Thunderbird 0.000

And the layout of the screen keyboard is set to "ir" 0.000

Hooks

After features/support/hooks.rb:330 11.046

Output 1

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

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/04:57:14_Tails_is_localized_for_every_tier-1_language,_Examples___9_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/04:57:14_Tails_is_localized_for_every_tier-1_language,_Examples___9_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/04:57:14_Tails_is_localized_for_every_tier-1_language,_Examples___9_.journal

After features/support/hooks.rb:100 0.000

Feature: Tails has a sane default configuration

Tags: @product

26.768

Scenario No unexpected error messages in the journal after booting from DVD

Hooks

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 26.597

Then there are no unexpected messages of priority "err" or higher in the journal 0.170

Unexpected

Unexpected error messages in the journal: [
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:18 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "579",
    "_BOOT_ID": "fd1270419b4a4fa1b9bc904fc8fb3033",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "579",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750236896412436",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "236b518893ec40cea4aae864f0fb7496",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=cfc4524877cc40e08ed684df996a5c46;i=372;b=fd1270419b4a4fa1b9bc904fc8fb3033;m=d48cb1;t=637d4c87be3ff;x=20e1c92ca89fac1a",
    "__MONOTONIC_TIMESTAMP": "13929649",
    "__REALTIME_TIMESTAMP": "1750236896420863",
    "__SEQNUM": "882",
    "__SEQNUM_ID": "cfc4524877cc40e08ed684df996a5c46"
  },
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:22 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "579",
    "_BOOT_ID": "fd1270419b4a4fa1b9bc904fc8fb3033",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "579",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750236896412471",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "236b518893ec40cea4aae864f0fb7496",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=cfc4524877cc40e08ed684df996a5c46;i=374;b=fd1270419b4a4fa1b9bc904fc8fb3033;m=d48e3e;t=637d4c87be58c;x=2822baf5099f3a70",
    "__MONOTONIC_TIMESTAMP": "13930046",
    "__REALTIME_TIMESTAMP": "1750236896421260",
    "__SEQNUM": "884",
    "__SEQNUM_ID": "cfc4524877cc40e08ed684df996a5c46"
  },
  {
    "MESSAGE": "The group `powerdev' does not exist.",
    "SYSLOG_IDENTIFIER": "adduser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "2077",
    "SYSLOG_TIMESTAMP": "Jun 18 08:55:05 ",
    "_BOOT_ID": "fd1270419b4a4fa1b9bc904fc8fb3033",
    "_CAP_EFFECTIVE": "1ffffffffff",
    "_CMDLINE": "adduser",
    "_COMM": "adduser",
    "_EXE": "/usr/bin/perl",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "2077",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750236905325323",
    "_SYSTEMD_CGROUP": "/system.slice/live-config.service",
    "_SYSTEMD_INVOCATION_ID": "2a09d83c56a04d77aa771ea4695d8a49",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "live-config.service",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=cfc4524877cc40e08ed684df996a5c46;i=404;b=fd1270419b4a4fa1b9bc904fc8fb3033;m=15c6d24;t=637d4c903c46f;x=3c2d2b11050a4bea",
    "__MONOTONIC_TIMESTAMP": "22834468",
    "__REALTIME_TIMESTAMP": "1750236905325679",
    "__SEQNUM": "1028",
    "__SEQNUM_ID": "cfc4524877cc40e08ed684df996a5c46"
  },
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:18 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "579",
    "_BOOT_ID": "fd1270419b4a4fa1b9bc904fc8fb3033",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "579",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750237078769411",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "236b518893ec40cea4aae864f0fb7496",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=cfc4524877cc40e08ed684df996a5c46;i=8cc;b=fd1270419b4a4fa1b9bc904fc8fb3033;m=6493993;t=637d4d35a4f6b;x=1dfaa0183b89cea6",
    "__MONOTONIC_TIMESTAMP": "105462163",
    "__REALTIME_TIMESTAMP": "1750237078769515",
    "__SEQNUM": "2252",
    "__SEQNUM_ID": "cfc4524877cc40e08ed684df996a5c46"
  },
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:22 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "579",
    "_BOOT_ID": "fd1270419b4a4fa1b9bc904fc8fb3033",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "579",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750237078769440",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "236b518893ec40cea4aae864f0fb7496",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=cfc4524877cc40e08ed684df996a5c46;i=8ce;b=fd1270419b4a4fa1b9bc904fc8fb3033;m=6493afe;t=637d4d35a50d7;x=192e4be5b2100e06",
    "__MONOTONIC_TIMESTAMP": "105462526",
    "__REALTIME_TIMESTAMP": "1750237078769879",
    "__SEQNUM": "2254",
    "__SEQNUM_ID": "cfc4524877cc40e08ed684df996a5c46"
  },
  {
    "MESSAGE": "The user `amnesia' is not a member of group `sudo'.",
    "SYSLOG_IDENTIFIER": "deluser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "8183",
    "SYSLOG_TIMESTAMP": "Jun 18 08:58:04 ",
    "_AUDIT_LOGINUID": "1000",
    "_AUDIT_SESSION": "4",
    "_BOOT_ID": "fd1270419b4a4fa1b9bc904fc8fb3033",
    "_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": "8183",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750237084385147",
    "_SYSTEMD_CGROUP": "/user.slice/user-1000.slice/session-4.scope",
    "_SYSTEMD_INVOCATION_ID": "6d2d4bae84014082a1ef03448692c950",
    "_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=cfc4524877cc40e08ed684df996a5c46;i=125a;b=fd1270419b4a4fa1b9bc904fc8fb3033;m=69ee9ac;t=637d4d3afff84;x=3bc9edf29bb0baff",
    "__MONOTONIC_TIMESTAMP": "111077804",
    "__REALTIME_TIMESTAMP": "1750237084385156",
    "__SEQNUM": "4698",
    "__SEQNUM_ID": "cfc4524877cc40e08ed684df996a5c46"
  }
].
<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'

Hooks

After features/support/hooks.rb:330 6.284

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/06:43:44_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/2/artifact/build-artifacts/06:43:44_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/2/artifact/build-artifacts/06:43:44_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/2/artifact/build-artifacts/06:43:44_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.journal

After features/support/hooks.rb:100 0.000

Feature: Tails has a sane default configuration

Tags: @product

16.184

Scenario No unexpected error messages in the journal after booting from USB drive

Hooks

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 15.447

Then there are no unexpected messages of priority "err" or higher in the journal 0.737

Unexpected

Unexpected error messages in the journal: [
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:18 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "711",
    "_BOOT_ID": "8b90413451b14d1e888b9d466f36f626",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "711",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750239073846110",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "45bd026ef0414fcbbaf1d7f4a3f97bbf",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=9167a1a40ba5463db6101a5baa45d800;i=368;b=8b90413451b14d1e888b9d466f36f626;m=e1e81d;t=637d54a44dee8;x=83443b182f0bdafd",
    "__MONOTONIC_TIMESTAMP": "14805021",
    "__REALTIME_TIMESTAMP": "1750239073853160",
    "__SEQNUM": "872",
    "__SEQNUM_ID": "9167a1a40ba5463db6101a5baa45d800"
  },
  {
    "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": "711",
    "_BOOT_ID": "8b90413451b14d1e888b9d466f36f626",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "711",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750239073846140",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "45bd026ef0414fcbbaf1d7f4a3f97bbf",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=9167a1a40ba5463db6101a5baa45d800;i=36a;b=8b90413451b14d1e888b9d466f36f626;m=e1e966;t=637d54a44e033;x=ce3065b9ad76c193",
    "__MONOTONIC_TIMESTAMP": "14805350",
    "__REALTIME_TIMESTAMP": "1750239073853491",
    "__SEQNUM": "874",
    "__SEQNUM_ID": "9167a1a40ba5463db6101a5baa45d800"
  },
  {
    "MESSAGE": "The group `powerdev' does not exist.",
    "SYSLOG_IDENTIFIER": "adduser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "2180",
    "SYSLOG_TIMESTAMP": "Jun 18 09:31:22 ",
    "_BOOT_ID": "8b90413451b14d1e888b9d466f36f626",
    "_CAP_EFFECTIVE": "1ffffffffff",
    "_CMDLINE": "adduser",
    "_COMM": "adduser",
    "_EXE": "/usr/bin/perl",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "2180",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750239082271248",
    "_SYSTEMD_CGROUP": "/system.slice/live-config.service",
    "_SYSTEMD_INVOCATION_ID": "e793068a8a7341498ef2138acc72e0da",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "live-config.service",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=9167a1a40ba5463db6101a5baa45d800;i=416;b=8b90413451b14d1e888b9d466f36f626;m=1625b52;t=637d54ac5521f;x=65fb5e2d6a319c8e",
    "__MONOTONIC_TIMESTAMP": "23223122",
    "__REALTIME_TIMESTAMP": "1750239082271263",
    "__SEQNUM": "1046",
    "__SEQNUM_ID": "9167a1a40ba5463db6101a5baa45d800"
  },
  {
    "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": "711",
    "_BOOT_ID": "8b90413451b14d1e888b9d466f36f626",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "711",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750239228518884",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "45bd026ef0414fcbbaf1d7f4a3f97bbf",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=9167a1a40ba5463db6101a5baa45d800;i=e74;b=8b90413451b14d1e888b9d466f36f626;m=9d77969;t=637d5537cf6fc;x=6142bb8e5944718e",
    "__MONOTONIC_TIMESTAMP": "165116265",
    "__REALTIME_TIMESTAMP": "1750239228524284",
    "__SEQNUM": "3700",
    "__SEQNUM_ID": "9167a1a40ba5463db6101a5baa45d800"
  },
  {
    "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": "711",
    "_BOOT_ID": "8b90413451b14d1e888b9d466f36f626",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "711",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750239228518902",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "45bd026ef0414fcbbaf1d7f4a3f97bbf",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=9167a1a40ba5463db6101a5baa45d800;i=e76;b=8b90413451b14d1e888b9d466f36f626;m=9d77b73;t=637d5537cf906;x=5ac3ca462d5c4fb1",
    "__MONOTONIC_TIMESTAMP": "165116787",
    "__REALTIME_TIMESTAMP": "1750239228524806",
    "__SEQNUM": "3702",
    "__SEQNUM_ID": "9167a1a40ba5463db6101a5baa45d800"
  },
  {
    "MESSAGE": "The user `amnesia' is not a member of group `sudo'.",
    "SYSLOG_IDENTIFIER": "deluser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "12228",
    "SYSLOG_TIMESTAMP": "Jun 18 09:33:55 ",
    "_AUDIT_LOGINUID": "1000",
    "_AUDIT_SESSION": "4",
    "_BOOT_ID": "8b90413451b14d1e888b9d466f36f626",
    "_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": "12228",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1750239235594684",
    "_SYSTEMD_CGROUP": "/user.slice/user-1000.slice/session-4.scope",
    "_SYSTEMD_INVOCATION_ID": "a43dd33c078641dd926a5ac873dae5e0",
    "_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=9167a1a40ba5463db6101a5baa45d800;i=185a;b=8b90413451b14d1e888b9d466f36f626;m=a435c54;t=637d553e8d9e6;x=79b3a5b7011d5b2a",
    "__MONOTONIC_TIMESTAMP": "172186708",
    "__REALTIME_TIMESTAMP": "1750239235594726",
    "__SEQNUM": "6234",
    "__SEQNUM_ID": "9167a1a40ba5463db6101a5baa45d800"
  }
].
<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'

Hooks

After features/support/hooks.rb:330 5.468

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/06:44:05_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/2/artifact/build-artifacts/06:44:05_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/2/artifact/build-artifacts/06:44:05_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/2/artifact/build-artifacts/06:44:05_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.journal

After features/support/hooks.rb:100 0.000

Feature: Shutdown buttons in the system menu

Tags: @product

28.708

Scenario I can shutdown Tails via the system menu

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.003

Steps

Given I have started Tails from DVD and logged in and the network is connected 13.143

When I request a shutdown using the system menu 15.565

try_for()

try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/support/helpers/dogtail.rb:371:in `grabFocus'
./features/step_definitions/common_steps.rb:887:in `/^I request a (shutdown|reboot) using the system menu$/'
features/shutdown_applet.feature:6:in `When I request a shutdown using the system menu'

Then Tails eventually shuts down 0.000

Hooks

After features/support/hooks.rb:330 6.597

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/06:44:39_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/2/artifact/build-artifacts/06:44:39_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/2/artifact/build-artifacts/06:44:39_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/2/artifact/build-artifacts/06:44:39_I_can_shutdown_Tails_via_the_system_menu.journal

After features/support/hooks.rb:100 0.000

Feature: Shutdown buttons in the system menu

Tags: @product @not_release_blocker

28.822

Scenario I can reboot Tails via the system menu

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.003

Steps

Given I have started Tails from DVD and logged in and the network is connected 13.938

When I request a reboot using the system menu 14.884

try_for()

try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/support/helpers/dogtail.rb:371:in `grabFocus'
./features/step_definitions/common_steps.rb:887:in `/^I request a (shutdown|reboot) using the system menu$/'
features/shutdown_applet.feature:12:in `When I request a reboot using the system menu'

Then Tails eventually restarts 0.000

Hooks

After features/support/hooks.rb:330 5.671

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/06:45:15_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/2/artifact/build-artifacts/06:45:15_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/2/artifact/build-artifacts/06:45:15_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/2/artifact/build-artifacts/06:45:15_I_can_reboot_Tails_via_the_system_menu.journal

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Tor Browser

Tags: @product @check_tor_leaks

1:35.225

Scenario The Downloads directory is usable in Tor Browser

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.004

Before features/support/hooks.rb:507 0.007

Steps

Given I have started Tails from DVD and logged in and the network is connected 25.836

Then the live user's Downloads directory exists 0.058

And there is a GNOME bookmark for the Downloads directory 21.696

When I start the Tor Browser 28.241

And the Tor Browser loads the startup page 1.777

Then I can save the current page as "index.html" to the Downloads directory 17.613

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

Hooks

After features/support/hooks.rb:515 0.037

After features/support/hooks.rb:330 12.416

Output 1

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

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

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Tor Browser

Tags: @product @check_tor_leaks

1:19.386

Scenario Downloading files with the Tor Browser

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.003

Before features/support/hooks.rb:507 0.005

Steps

Given I have started Tails from DVD and logged in and the network is connected 14.771

When I start the Tor Browser 29.173

Then the Tor Browser loads the startup page 2.474

When I download some file in the Tor Browser to the Downloads directory 32.967

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

Hooks

After features/support/hooks.rb:515 0.039

After features/support/hooks.rb:330 11.249

Output 1

SCENARIO FAILED: 'Downloading files with the Tor Browser' (at time 07:02:04)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/07:02:04_Downloading_files_with_the_Tor_Browser.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/07:02:04_Downloading_files_with_the_Tor_Browser.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/07:02:04_Downloading_files_with_the_Tor_Browser.journal

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Tor Browser

Tags: @product

45.713

Scenario The Tor Browser uses TBB's shared libraries

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.007

Steps

Given I have started Tails from DVD and logged in and the network is connected 15.053

When I start the Tor Browser 28.520

Then the Tor Browser uses all expected TBB shared libraries 2.139

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'

Hooks

After features/support/hooks.rb:330 6.617

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/07:08:04_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/2/artifact/build-artifacts/07:08:04_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/2/artifact/build-artifacts/07:08:04_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/2/artifact/build-artifacts/07:08:04_The_Tor_Browser_uses_TBB_s_shared_libraries.journal

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Tor Browser

Tags: @product

2:24.465

Scenario The Persistent directory is usable in Tor Browser

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.006

Steps

Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.825

And the network is plugged 0.134

And I successfully configure Tor 28.695

And available upgrades have been checked 0.066

And all notifications have disappeared 5.925

And there is a GNOME bookmark for the Persistent directory 21.138

When I start the Tor Browser 31.737

And I download some file in the Tor Browser to the Persistent directory 40.940

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

Hooks

After features/support/hooks.rb:330 11.398

Output 1

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

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/07:14:08_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/2/artifact/build-artifacts/07:14:08_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/2/artifact/build-artifacts/07:14:08_The_Persistent_directory_is_usable_in_Tor_Browser.journal

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Tor Browser

Tags: @product

1:41.592

Scenario Outline The default XDG directories are usable in Tor Browser

Hooks

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 12.547

Then the live user's Documents directory exists 0.279

And there is a GNOME bookmark for the Documents directory 20.576

Then I start the Tor Browser in offline mode 39.053

And I can save the current page as "index.html" to the Documents GNOME bookmark 29.135

try_for()

try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/browser.rb:19:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:38:in `browser_save_page_as'
./features/step_definitions/browser.rb:543:in `/^I (can|cannot) save the current page as "([^"]+[.]html)" to the (.*) (directory|GNOME bookmark)$/'
features/torified_browsing.feature:127:in `And I can save the current page as "index.html" to the Documents GNOME bookmark'
features/torified_browsing.feature:124:in `And I can save the current page as "index.html" to the <dir> GNOME bookmark'

Hooks

After features/support/hooks.rb:330 10.323

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/07:16:02_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/07:16:02_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/2/artifact/build-artifacts/07:16:02_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/2/artifact/build-artifacts/07:16:02_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.journal

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Tor Browser

Tags: @product

1:53.937

Scenario Outline The default XDG directories are usable in Tor Browser

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.006

Steps

Given I have started Tails from DVD without network and logged in 9.815

Then the live user's Downloads directory exists 0.087

And there is a GNOME bookmark for the Downloads directory 21.022

Then I start the Tor Browser in offline mode 35.079

And I can save the current page as "index.html" to the Downloads GNOME bookmark 47.932

The

The page was not saved to /home/amnesia/Downloads/index.html (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/browser.rb:546:in `/^I (can|cannot) save the current page as "([^"]+[.]html)" to the (.*) (directory|GNOME bookmark)$/'
features/torified_browsing.feature: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'

Hooks

After features/support/hooks.rb:330 6.418

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/07:18:06_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___2_.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/07:18:06_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/2/artifact/build-artifacts/07:18:06_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/2/artifact/build-artifacts/07:18:06_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___2_.journal

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Tor Browser

Tags: @product

1:21.266

Scenario Outline The default XDG directories are usable in Tor Browser

Hooks

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 logged in 9.672

Then the live user's Music directory exists 0.100

And there is a GNOME bookmark for the Music directory 20.380

Then I start the Tor Browser in offline mode 33.075

And I can save the current page as "index.html" to the Music GNOME bookmark 18.036

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'

Hooks

After features/support/hooks.rb:330 10.602

Output 1

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

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/07:19:33_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/2/artifact/build-artifacts/07:19:33_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/2/artifact/build-artifacts/07:19:33_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___3_.journal

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Tor Browser

Tags: @product

1:42.066

Scenario Outline The default XDG directories are usable in Tor Browser

Hooks

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 14.001

Then the live user's Pictures directory exists 0.073

And there is a GNOME bookmark for the Pictures directory 18.267

Then I start the Tor Browser in offline mode 42.462

And I can save the current page as "index.html" to the Pictures GNOME bookmark 27.261

try_for()

try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/browser.rb:19:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:38:in `browser_save_page_as'
./features/step_definitions/browser.rb:543:in `/^I (can|cannot) save the current page as "([^"]+[.]html)" to the (.*) (directory|GNOME bookmark)$/'
features/torified_browsing.feature: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'

Hooks

After features/support/hooks.rb:330 8.926

Output 1

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

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/07:21:26_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/2/artifact/build-artifacts/07:21:26_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/2/artifact/build-artifacts/07:21:26_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___4_.journal

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Tor Browser

Tags: @product

1:32.938

Scenario Outline The default XDG directories are usable in Tor Browser

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.006

Steps

Given I have started Tails from DVD without network and logged in 9.705

Then the live user's Videos directory exists 0.576

And there is a GNOME bookmark for the Videos directory 20.479

Then I start the Tor Browser in offline mode 34.687

And I can save the current page as "index.html" to the Videos GNOME bookmark 27.489

try_for()

try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/browser.rb:19:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:38:in `browser_save_page_as'
./features/step_definitions/browser.rb:543:in `/^I (can|cannot) save the current page as "([^"]+[.]html)" to the (.*) (directory|GNOME bookmark)$/'
features/torified_browsing.feature: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'

Hooks

After features/support/hooks.rb:330 8.541

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/07:23:08_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___5_.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/07:23:08_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/2/artifact/build-artifacts/07:23:08_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/2/artifact/build-artifacts/07:23:08_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___5_.journal

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Tor Browser

Tags: @product

7:36.656

Scenario Persistent browser bookmarks

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.006

Steps

Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.693

And all tps features are active 2.543

And all persistent filesystems have safe access rights 0.391

And all persistence configuration files have safe access rights 0.498

And all persistent directories have safe access rights 2.942

When I start the Tor Browser in offline mode 39.269

And I add a bookmark to eff.org in the Tor Browser 21.769

And I cold reboot the computer 18.770

And the computer reboots Tails 2:13.219

And I enable persistence 21.753

And I log in to a new session 39.333

And all notifications have disappeared 17.503

And I start the Tor Browser in offline mode 2:24.968

try_for()

try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/browser.rb:480:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:466:in `/^I start the Tor Browser( in offline mode)?$/'
features/torified_browsing.feature:146:in `And I start the Tor Browser in offline mode'

Then the Tor Browser has a bookmark to eff.org 0.000

Hooks

After features/support/hooks.rb:330 6.760

Output 1

SCENARIO FAILED: 'Persistent browser bookmarks' (at time 07:30:53)

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

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/07:30:53_Persistent_browser_bookmarks.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/07:30:53_Persistent_browser_bookmarks.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/07:30:53_Persistent_browser_bookmarks.journal

After features/support/hooks.rb:100 0.011

Feature: Using Totem

Tags: @product

59.810

Scenario Watching a MP4 video stored on the non-persistent filesystem

Steps

Given I have started Tails from DVD without network and logged in 13.063

And I plug and mount a USB drive containing sample videos 19.197

And I copy the sample videos to "/home/amnesia" as user "amnesia" 0.195

And the file "/home/amnesia/video.mp4" exists 0.065

Given I start monitoring the AppArmor log of "/usr/bin/totem" 0.187

When I open "/home/amnesia/video.mp4" with Totem 3.877

Then I see "SampleLocalMp4VideoFrame.png" after at most 40 seconds 6.859

And AppArmor has not denied "/usr/bin/totem" from opening "/home/amnesia/video.mp4" 1.976

Given I close Totem 0.713

And I copy the sample videos to "/home/amnesia/.gnupg" as user "amnesia" 0.086

And the file "/home/amnesia/.gnupg/video.mp4" exists 0.060

And I restart monitoring the AppArmor log of "/usr/bin/totem" 0.277

When I try to open "/home/amnesia/.gnupg/video.mp4" with Totem 2.533

Then Totem tells me it is not allowed to open this file 10.716

The

The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'totem' application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/totem.rb:59:in `new'
./features/step_definitions/totem.rb:59:in `/^Totem tells me it is not allowed to open this file$/'
features/totem.feature:25:in `Then Totem tells me it is not allowed to open this file'

And AppArmor has denied "/usr/bin/totem" from opening "/home/amnesia/.gnupg/video.mp4" 0.000

Given I close Totem 0.000

And the file "/lib/live/mount/overlay/rw/home/amnesia/.gnupg/video.mp4" exists 0.000

And I restart monitoring the AppArmor log of "/usr/bin/totem" 0.000

When I try to open "/lib/live/mount/overlay/rw/home/amnesia/.gnupg/video.mp4" with Totem 0.000

Then Totem tells me it is not allowed to open this file 0.000

And AppArmor has denied "/usr/bin/totem" from opening "/usr/lib/live/mount/overlay/rw/home/amnesia/.gnupg/video.mp4" 0.000

Given I close Totem 0.000

And the file "/live/overlay/rw/home/amnesia/.gnupg/video.mp4" exists 0.000

And I restart monitoring the AppArmor log of "/usr/bin/totem" 0.000

When I try to open "/live/overlay/rw/home/amnesia/.gnupg/video.mp4" with Totem 0.000

Then Totem tells me it is not allowed to open this file 0.000

# Due to our AppArmor aliases, /live/overlay will be treated

# as /usr/lib/live/mount/overlay.

And AppArmor has denied "/usr/bin/totem" from opening "/usr/lib/live/mount/overlay/rw/home/amnesia/.gnupg/video.mp4" 0.000

Given I close Totem 0.000

And I copy "/home/amnesia/video.mp4" to "/home/amnesia/.purple/otr.private_key" as user "amnesia" 0.000

And the file "/home/amnesia/.purple/otr.private_key" exists 0.000

And I restart monitoring the AppArmor log of "/usr/bin/totem" 0.000

When I try to open "/home/amnesia/.purple/otr.private_key" with Totem 0.000

Then Totem tells me it is not allowed to open this file 0.000

And AppArmor has denied "/usr/bin/totem" from opening "/home/amnesia/.purple/otr.private_key" 0.000

Hooks

After features/support/hooks.rb:330 6.934

Output 1

SCENARIO FAILED: 'Watching a MP4 video stored on the non-persistent filesystem' (at time 07:33:20)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/07:33:20_Watching_a_MP4_video_stored_on_the_non-persistent_filesystem.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/07:33:20_Watching_a_MP4_video_stored_on_the_non-persistent_filesystem.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/07:33:20_Watching_a_MP4_video_stored_on_the_non-persistent_filesystem.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/07:33:20_Watching_a_MP4_video_stored_on_the_non-persistent_filesystem.journal

After features/support/hooks.rb:100 0.003

Feature: Using Totem

Tags: @product

1:8.376

Scenario Watching MP4 videos stored on the persistent volume should work as expected given our AppArmor confinement

Steps

Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.303

And I plug and mount a USB drive containing sample videos 18.541

And I copy the sample videos to "/home/amnesia/Persistent" as user "amnesia" 0.502

When I open "/home/amnesia/Persistent/video.mp4" with Totem 12.997

Then I see "SampleLocalMp4VideoFrame.png" after at most 40 seconds 8.411

Given I close Totem 1.485

And I start monitoring the AppArmor log of "/usr/bin/totem" 0.235

And I copy the sample videos to "/home/amnesia/.gnupg" as user "amnesia" 0.118

When I try to open "/home/amnesia/.gnupg/video.mp4" with Totem 2.335

Then Totem tells me it is not allowed to open this file 10.446

The

The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'totem' application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/totem.rb:59:in `new'
./features/step_definitions/totem.rb:59:in `/^Totem tells me it is not allowed to open this file$/'
features/totem.feature:64:in `Then Totem tells me it is not allowed to open this file'

And AppArmor has denied "/usr/bin/totem" from opening "/home/amnesia/.gnupg/video.mp4" 0.000

Hooks

After features/support/hooks.rb:330 5.722

Output 1

SCENARIO FAILED: 'Watching MP4 videos stored on the persistent volume should work as expected given our AppArmor confinement' (at time 07:35:06)

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

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/07:35:06_Watching_MP4_videos_stored_on_the_persistent_volume_should_work_as_expected_given_our_AppArmor_confinement.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/07:35:06_Watching_MP4_videos_stored_on_the_persistent_volume_should_work_as_expected_given_our_AppArmor_confinement.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/07:35:06_Watching_MP4_videos_stored_on_the_persistent_volume_should_work_as_expected_given_our_AppArmor_confinement.journal

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Unsafe Browser

Tags: @product @not_release_blocker

55.782

Scenario Starting a second instance of the Unsafe Browser results in an error message being shown

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.006

Steps

Given I have started Tails from DVD and logged in and the network is connected 12.970

When I successfully start the Unsafe Browser 21.314

# 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.011

Output 1

Slept for 10 seconds

And I try to start the Unsafe Browser 0.476

Then I see a warning about another instance already running 11.009

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'

Hooks

After features/support/hooks.rb:330 11.861

Output 1

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

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

After features/support/hooks.rb:100 0.000

Feature: Using VeraCrypt encrypted volumes

Tags: @product @not_release_blocker

22.910

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.188

And I cancel the GNOME authentication prompt 2.339

And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 7.150

And I open this VeraCrypt volume in GNOME Files 4.611

Then I see the expected contents in this VeraCrypt volume 0.521

When I lock the currently opened VeraCrypt volume 0.099

Command

Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/veracrypt.rb:330:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:18:in `When I lock the currently opened VeraCrypt volume'

Then the VeraCrypt volume has been unmounted and locked 0.000

Hooks

After features/support/hooks.rb:330 5.274

Output 1

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

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

After features/support/hooks.rb:100 0.000

Feature: Using VeraCrypt encrypted volumes

Tags: @product @not_release_blocker

28.410

Scenario Use Unlock VeraCrypt Volumes to unlock a USB drive that has a hidden VeraCrypt volume

Steps

When I plug a USB drive containing a hidden VeraCrypt volume 11.589

And I cancel the GNOME authentication prompt 2.564

And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 8.537

And I open this VeraCrypt volume in GNOME Files 4.937

Then I see the expected contents in this VeraCrypt volume 0.689

When I lock the currently opened VeraCrypt volume 0.090

Command

Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/veracrypt.rb:330:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:27:in `When I lock the currently opened VeraCrypt volume'

Then the VeraCrypt volume has been unmounted and locked 0.000

Hooks

After features/support/hooks.rb:330 5.345

Output 1

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

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

After features/support/hooks.rb:100 0.000

Feature: Using VeraCrypt encrypted volumes

Tags: @product @not_release_blocker

32.125

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 17.618

And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 9.490

And I open this VeraCrypt volume in GNOME Files 4.368

Then I see the expected contents in this VeraCrypt volume 0.543

When I lock the currently opened VeraCrypt file container 0.104

Command

Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/veracrypt.rb:330:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:35:in `When I lock the currently opened VeraCrypt file container'

Then the VeraCrypt file container has been unmounted and locked 0.000

Hooks

After features/support/hooks.rb:330 6.161

Output 1

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

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

After features/support/hooks.rb:100 0.000

Feature: Using VeraCrypt encrypted volumes

Tags: @product @not_release_blocker

43.008

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 28.703

And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 9.936

And I open this VeraCrypt volume in GNOME Files 3.804

Then I see the expected contents in this VeraCrypt volume 0.466

When I lock the currently opened VeraCrypt file container 0.097

Command

Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/veracrypt.rb:330:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:43:in `When I lock the currently opened VeraCrypt file container'

Then the VeraCrypt file container has been unmounted and locked 0.000

Hooks

After features/support/hooks.rb:330 5.769

Output 1

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

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

After features/support/hooks.rb:100 0.035

Feature: Using VeraCrypt encrypted volumes

Tags: @product @not_release_blocker

26.640

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.995

And I cancel the GNOME authentication prompt 2.525

And I unlock and mount this VeraCrypt volume with GNOME Disks 10.224

And I open this VeraCrypt volume in GNOME Files 4.368

Then I see the expected contents in this VeraCrypt volume 0.447

When I lock the currently opened VeraCrypt volume 0.079

Command

Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/veracrypt.rb:330:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:54:in `When I lock the currently opened VeraCrypt volume'

Then the VeraCrypt volume has been unmounted and locked 0.000

Hooks

After features/support/hooks.rb:330 5.271

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/07:49:44_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/2/artifact/build-artifacts/07:49:44_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/2/artifact/build-artifacts/07:49:44_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/2/artifact/build-artifacts/07:49:44_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.journal

After features/support/hooks.rb:100 0.000

Feature: Using VeraCrypt encrypted volumes

Tags: @product @not_release_blocker

28.663

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.832

And I cancel the GNOME authentication prompt 2.554

And I unlock and mount this VeraCrypt volume with GNOME Disks 8.940

And I open this VeraCrypt volume in GNOME Files 4.678

Then I see the expected contents in this VeraCrypt volume 0.512

When I lock the currently opened VeraCrypt volume 0.145

Command

Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/veracrypt.rb:330:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:63:in `When I lock the currently opened VeraCrypt volume'

Then the VeraCrypt volume has been unmounted and locked 0.000

Hooks

After features/support/hooks.rb:330 5.474

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/07:50: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/2/artifact/build-artifacts/07:50: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/2/artifact/build-artifacts/07:50: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/2/artifact/build-artifacts/07:50:27_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.journal

After features/support/hooks.rb:100 0.001

Feature: Using VeraCrypt encrypted volumes

Tags: @product @not_release_blocker

53.505

Scenario Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile

Steps

When I plug and mount a USB drive containing a basic VeraCrypt file container with a keyfile 24.181

And I unlock and mount this VeraCrypt file container with GNOME Disks 23.987

And I open this VeraCrypt volume in GNOME Files 4.762

Then I see the expected contents in this VeraCrypt volume 0.479

When I lock the currently opened VeraCrypt file container 0.094

Command

Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/veracrypt.rb:330:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:71:in `When I lock the currently opened VeraCrypt file container'

Then the VeraCrypt file container has been unmounted and locked 0.000

Hooks

After features/support/hooks.rb:330 5.483

Output 1

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

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

After features/support/hooks.rb:100 0.014

Feature: Using VeraCrypt encrypted volumes

Tags: @product @not_release_blocker

56.438

Scenario Use GNOME Disks to unlock a hidden VeraCrypt file container

Steps

When I plug and mount a USB drive containing a hidden VeraCrypt file container 29.366

And I unlock and mount this VeraCrypt file container with GNOME Disks 21.672

And I open this VeraCrypt volume in GNOME Files 4.880

Then I see the expected contents in this VeraCrypt volume 0.440

When I lock the currently opened VeraCrypt file container 0.077

Command

Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/veracrypt.rb:330:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:79:in `When I lock the currently opened VeraCrypt file container'

Then the VeraCrypt file container has been unmounted and locked 0.000

Hooks

After features/support/hooks.rb:330 5.506

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/07:52:49_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/2/artifact/build-artifacts/07:52:49_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/2/artifact/build-artifacts/07:52:49_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/2/artifact/build-artifacts/07:52:49_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.journal

After features/support/hooks.rb:100 0.014

Feature: Using VeraCrypt encrypted volumes

Tags: @product @not_release_blocker

42.925

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 17.788

And I unlock and mount this VeraCrypt file container with GNOME Disks 19.913

And I open this VeraCrypt volume in GNOME Files 4.557

Then I see the expected contents in this VeraCrypt volume 0.582

When I lock the currently opened VeraCrypt file container 0.083

Command

Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/veracrypt.rb:330:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:87:in `When I lock the currently opened VeraCrypt file container'

Then the VeraCrypt file container has been unmounted and locked 0.000

Hooks

After features/support/hooks.rb:330 5.572

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21019-fix-custom-package-versioning-scheme/2/artifact/build-artifacts/07:53:46_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/2/artifact/build-artifacts/07:53:46_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/2/artifact/build-artifacts/07:53:46_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/2/artifact/build-artifacts/07:53:46_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.journal

After features/support/hooks.rb:100 0.000