Project Number Date
test_Tails_ISO_feature-trixie 39 26 Jun 2025, 09:06

Failures Overview

The following summary displays scenarios that failed.

Feature: Untrusted partitions
Tags: @product
2:13.935
Scenario Booting Tails does not automount untrusted partitions
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given a computer 0.170
And I temporarily create a 100 MiB disk named "gpt_ext2" 0.039
And I create a gpt partition with an ext2 filesystem on disk "gpt_ext2" 6.331
And I plug SATA drive "gpt_ext2" 1.046
And I temporarily create a 100 MiB disk named "msdos_fat32" 0.061
And I create an msdos partition with a vfat filesystem on disk "msdos_fat32" 7.259
And I plug SATA drive "msdos_fat32" 1.061
And I start Tails from DVD with network unplugged and I login 1:57.964
cannot 
cannot find TailsGreeter.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/common_steps.rb:480:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:255:in `/^I start Tails( from DVD)?( with network unplugged)?( and I login)?$/'
features/untrusted_partitions.feature:48:in `And I start Tails from DVD with network unplugged and I login'
Then drive "gpt_ext2" is detected by Tails 0.000
And drive "gpt_ext2" is not mounted 0.000
And drive "msdos_fat32" is detected by Tails 0.000
And drive "msdos_fat32" is not mounted 0.000
After features/support/hooks.rb:330 6.882 
SCENARIO FAILED: 'Booting Tails does not automount untrusted partitions' (at time 00:10:41)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/00:10:41_Booting_Tails_does_not_automount_untrusted_partitions.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/00:10:41_Booting_Tails_does_not_automount_untrusted_partitions.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/00:10:41_Booting_Tails_does_not_automount_untrusted_partitions.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/00:10:41_Booting_Tails_does_not_automount_untrusted_partitions.journal
After features/support/hooks.rb:100 0.006
Feature: Time syncing
Tags: @product @check_tor_leaks
10:10.124
Scenario Clock with host's time
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:507 0.004
Steps
Given I have started Tails from DVD without network and logged in 9.891
When the network is plugged 10:0.232
Command 
Command failed (pid 10764 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-trixie/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-trixie/features/chutney/test-network", {:err=>[:child, :out]}]
Bootstrap failed: 600 seconds
Node status:
test000auth  :  100, done                     , Done
test001auth  :  100, done                     , Done
test002auth  :  100, done                     , Done
test003auth  :  100, done                     , Done
test004ba    :  100, done                     , Done
test005relay :  100, done                     , Done
test006relay :  100, done                     , Done
test007relay :  100, done                     , Done
test008relay :  100, done                     , Done
test009relay :  100, done                     , Done
test010relay :  100, done                     , Done
test011relay :  100, done                     , Done
test012relay :  100, done                     , Done
test013relay :  100, done                     , Done
test014relay :  100, done                     , Done
test015relay :  100, done                     , Done
test016relay :  100, done                     , Done
test017relay :  100, done                     , Done
test018relay :  100, done                     , Done
test019relay :  100, done                     , Done
test020bridge:  100, done                     , Done
test021bridge:  100, done                     , Done
test022obfs4 :  100, done                     , Done
test023obfs4 :  100, done                     , Done
test024defbr :  100, done                     , Done
test025client:  100, done                     , Done
Published dir info:
test000auth  : -400, 021bridge                , desc ns_cons                  , No dir file
test001auth  : -400, 021bridge                , desc ns_cons                  , No dir file
test002auth  : -400, 021bridge                , desc ns_cons                  , No dir file
test003auth  : -400, 021bridge                , desc ns_cons                  , No dir file
test004ba    : -400, 021bridge                , desc ns_cons                  , No dir file
test005relay : -400, 021bridge                , desc ns_cons                  , No dir file
test006relay : -400, 021bridge                , desc ns_cons                  , No dir file
test007relay : -400, 021bridge                , desc ns_cons                  , No dir file
test008relay : -400, 021bridge                , desc ns_cons                  , No dir file
test009relay : -400, 021bridge                , desc ns_cons                  , No dir file
test010relay : -400, 021bridge                , desc ns_cons                  , No dir file
test011relay : -400, 021bridge                , desc ns_cons                  , No dir file
test012relay : -400, 021bridge                , desc ns_cons                  , No dir file
test013relay : -400, 021bridge                , desc ns_cons                  , No dir file
test014relay : -400, 021bridge                , desc ns_cons                  , No dir file
test015relay : -400, 021bridge                , desc ns_cons                  , No dir file
test016relay : -400, 021bridge                , desc ns_cons                  , No dir file
test017relay : -400, 021bridge                , desc ns_cons                  , No dir file
test018relay : -400, 021bridge                , desc ns_cons                  , No dir file
test019relay : -400, 021bridge                , desc ns_cons                  , No dir file
test020bridge:  100, 004ba                    , desc                          , Dir info cached
test021bridge:  100, 004ba                    , desc                          , Dir info cached
test022obfs4 :  100, 004ba                    , desc                          , Dir info cached
test023obfs4 :  100, 004ba                    , desc                          , Dir info cached
test024defbr :  100, 004ba                    , desc                          , Dir info cached

 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:184:in `/^the network is plugged$/'
features/time_syncing.feature:9:in `When the network is plugged'
And I successfully configure Tor 0.000
Then the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:515 0.047
After features/support/hooks.rb:330 6.498 
SCENARIO FAILED: 'Clock with host's time' (at time 00:26:16)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/00:26:16_Clock_with_host_s_time_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/00:26:16_Clock_with_host_s_time.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/00:26:16_Clock_with_host_s_time.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/00:26:16_Clock_with_host_s_time.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/00:26:16_Clock_with_host_s_time.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/00:26:16_Clock_with_host_s_time.journal
After features/support/hooks.rb:100 0.000
Feature: Time syncing
Tags: @product @check_tor_leaks
10:10.007
Scenario Clock with host's time while using bridges
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:507 0.002
Steps
Given I have started Tails from DVD without network and logged in 8.912
When the network is plugged 10:1.095
Command 
Command failed (pid 10929 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-trixie/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-trixie/features/chutney/test-network", {:err=>[:child, :out]}]
Bootstrap failed: 600 seconds
Node status:
test000auth  :  100, done                     , Done
test001auth  :  100, done                     , Done
test002auth  :  100, done                     , Done
test003auth  :  100, done                     , Done
test004ba    :  100, done                     , Done
test005relay :  100, done                     , Done
test006relay :  100, done                     , Done
test007relay :  100, done                     , Done
test008relay :  100, done                     , Done
test009relay :  100, done                     , Done
test010relay :  100, done                     , Done
test011relay :  100, done                     , Done
test012relay :  100, done                     , Done
test013relay :  100, done                     , Done
test014relay :  100, done                     , Done
test015relay :  100, done                     , Done
test016relay :  100, done                     , Done
test017relay :  100, done                     , Done
test018relay :  100, done                     , Done
test019relay :  100, done                     , Done
test020bridge:  100, done                     , Done
test021bridge:  100, done                     , Done
test022obfs4 :  100, done                     , Done
test023obfs4 :  100, done                     , Done
test024defbr :  100, done                     , Done
test025client:  100, done                     , Done
Published dir info:
test000auth  : -400, 021bridge                , desc ns_cons                  , No dir file
test001auth  : -400, 021bridge                , desc ns_cons                  , No dir file
test002auth  : -400, 021bridge                , desc ns_cons                  , No dir file
test003auth  : -400, 021bridge                , desc ns_cons                  , No dir file
test004ba    : -400, 021bridge                , desc ns_cons                  , No dir file
test005relay : -400, 021bridge                , desc ns_cons                  , No dir file
test006relay : -400, 021bridge                , desc ns_cons                  , No dir file
test007relay : -400, 021bridge                , desc ns_cons                  , No dir file
test008relay : -400, 021bridge                , desc ns_cons                  , No dir file
test009relay : -400, 021bridge                , desc ns_cons                  , No dir file
test010relay : -400, 021bridge                , desc ns_cons                  , No dir file
test011relay : -400, 021bridge                , desc ns_cons                  , No dir file
test012relay : -400, 021bridge                , desc ns_cons                  , No dir file
test013relay : -400, 021bridge                , desc ns_cons                  , No dir file
test014relay : -400, 021bridge                , desc ns_cons                  , No dir file
test015relay : -400, 021bridge                , desc ns_cons                  , No dir file
test016relay : -400, 021bridge                , desc ns_cons                  , No dir file
test017relay : -400, 021bridge                , desc ns_cons                  , No dir file
test018relay : -400, 021bridge                , desc ns_cons                  , No dir file
test019relay : -400, 021bridge                , desc ns_cons                  , No dir file
test020bridge:  100, 004ba                    , desc                          , Dir info cached
test021bridge:  100, 004ba                    , desc                          , Dir info cached
test022obfs4 :  100, 004ba                    , desc                          , Dir info cached
test023obfs4 :  100, 004ba                    , desc                          , Dir info cached
test024defbr :  100, 004ba                    , desc                          , Dir info cached

 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:184:in `/^the network is plugged$/'
features/time_syncing.feature:15:in `When the network is plugged'
And the Tor Connection Assistant autostarts 0.000
And I configure some normal bridges in the Tor Connection Assistant 0.000
And I wait until Tor is ready 0.000
Then the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:515 0.041
After features/support/hooks.rb:330 6.245 
SCENARIO FAILED: 'Clock with host's time while using bridges' (at time 00:36:32)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/00:36:32_Clock_with_host_s_time_while_using_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/00:36:32_Clock_with_host_s_time_while_using_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/00:36:32_Clock_with_host_s_time_while_using_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/00:36:32_Clock_with_host_s_time_while_using_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/00:36:32_Clock_with_host_s_time_while_using_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/00:36:32_Clock_with_host_s_time_while_using_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Time syncing
Tags: @product @check_tor_leaks
10:9.953
Scenario Clock is one day in the future while using obfs4 bridges
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:507 0.002
Steps
Given I have started Tails from DVD without network and logged in 8.395
When I bump the system time with "+1 day" 0.325
And I capture all network traffic 0.002
And the network is plugged 10:1.229
Command 
Command failed (pid 11100 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-trixie/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_feature-trixie/features/chutney/test-network", {:err=>[:child, :out]}]
Bootstrap failed: 601 seconds
Node status:
test000auth  :  100, done                     , Done
test001auth  :  100, done                     , Done
test002auth  :  100, done                     , Done
test003auth  :  100, done                     , Done
test004ba    :  100, done                     , Done
test005relay :  100, done                     , Done
test006relay :  100, done                     , Done
test007relay :  100, done                     , Done
test008relay :  100, done                     , Done
test009relay :  100, done                     , Done
test010relay :  100, done                     , Done
test011relay :  100, done                     , Done
test012relay :  100, done                     , Done
test013relay :  100, done                     , Done
test014relay :  100, done                     , Done
test015relay :  100, done                     , Done
test016relay :  100, done                     , Done
test017relay :  100, done                     , Done
test018relay :  100, done                     , Done
test019relay :  100, done                     , Done
test020bridge:  100, done                     , Done
chutney.errors.ChutneyTimeoutError
test021bridge:  100, done                     , Done
test022obfs4 :  100, done                     , Done
test023obfs4 :  100, done                     , Done
test024defbr :  100, done                     , Done
test025client:  100, done                     , Done
Published dir info:
test000auth  : -400, 021bridge                , desc ns_cons                  , No dir file
test001auth  : -400, 021bridge                , desc ns_cons                  , No dir file
test002auth  : -400, 021bridge                , desc ns_cons                  , No dir file
test003auth  : -400, 021bridge                , desc ns_cons                  , No dir file
test004ba    : -400, 021bridge                , desc ns_cons                  , No dir file
test005relay : -400, 021bridge                , desc ns_cons                  , No dir file
test006relay : -400, 021bridge                , desc ns_cons                  , No dir file
test007relay : -400, 021bridge                , desc ns_cons                  , No dir file
test008relay : -400, 021bridge                , desc ns_cons                  , No dir file
test009relay : -400, 021bridge                , desc ns_cons                  , No dir file
test010relay : -400, 021bridge                , desc ns_cons                  , No dir file
test011relay : -400, 021bridge                , desc ns_cons                  , No dir file
test012relay : -400, 021bridge                , desc ns_cons                  , No dir file
test013relay : -400, 021bridge                , desc ns_cons                  , No dir file
test014relay : -400, 021bridge                , desc ns_cons                  , No dir file
test015relay : -400, 021bridge                , desc ns_cons                  , No dir file
test016relay : -400, 021bridge                , desc ns_cons                  , No dir file
test017relay : -400, 021bridge                , desc ns_cons                  , No dir file
test018relay : -400, 021bridge                , desc ns_cons                  , No dir file
test019relay : -400, 021bridge                , desc ns_cons                  , No dir file
test020bridge:  100, 004ba                    , desc                          , Dir info cached
test021bridge:  100, 004ba                    , desc                          , Dir info cached
test022obfs4 :  100, 004ba                    , desc                          , Dir info cached
test023obfs4 :  100, 004ba                    , desc                          , Dir info cached
test024defbr :  100, 004ba                    , desc                          , Dir info cached

 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:184:in `/^the network is plugged$/'
features/time_syncing.feature:25:in `And the network is plugged'
And the Tor Connection Assistant autostarts 0.000
And I configure some obfs4 bridges in the Tor Connection Assistant in easy mode 0.000
And I wait until Tor is ready 0.000
Then the system clock is less than 5 minutes incorrect 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:515 0.038
After features/support/hooks.rb:330 5.960 
SCENARIO FAILED: 'Clock is one day in the future while using obfs4 bridges' (at time 00:46:49)
Failed to copy Chutney data: No such file or directory @ rb_file_s_lstat - /tmp/TailsToaster/chutney-data/nodes.1750893747/024defbr/diff-cache/1034.tmp
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/00:46:49_Clock_is_one_day_in_the_future_while_using_obfs4_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/00:46:49_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/00:46:49_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/00:46:49_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/00:46:49_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/00:46:49_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.journal
After features/support/hooks.rb:100 0.042
Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
14.972
Scenario Erasure of memory freed by killed userspace processes
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails from DVD without network and logged in 8.283
And I prepare Tails for memory erasure tests 0.730
When I start a process allocating 128 MiB of memory with a known pattern 2.490
Then patterns cover at least 128 MiB in the guest's memory 3.467
99.610% 
99.610% of the expected size (128 MiB) has the pattern, but more than 100.000% was expected.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/erase_memory.rb:186:in `/^patterns cover at least (\d+) MiB in the guest's memory$/'
features/erase_memory.feature:17:in `Then patterns cover at least 128 MiB in the guest's memory'
Output 1 
Pattern coverage: 99.610% (127 MiB out of 128 MiB reference memory)
When I kill the allocating process 0.000
Then I find very few patterns in the guest's memory after 5 seconds 0.000
After features/support/hooks.rb:330 5.293 
SCENARIO FAILED: 'Erasure of memory freed by killed userspace processes' (at time 01:06:18)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/01:06:18_Erasure_of_memory_freed_by_killed_userspace_processes.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/01:06:18_Erasure_of_memory_freed_by_killed_userspace_processes.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/01:06:18_Erasure_of_memory_freed_by_killed_userspace_processes.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/01:06:18_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
11:54.585
Scenario I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Before features/support/hooks.rb:507 0.024
Steps
Given I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login 1:24.506
And I update APT using apt 12.816
And I install "popularity-contest" using apt 26.433
Then I am proposed to add the "popularity-contest" package to my Additional Software 12.299
When I create a persistent storage and activate the Additional Software feature 28.008
Then Additional Software is correctly configured for package "popularity-contest" 2.832
When I shutdown Tails and wait for the computer to power off 15.595
And I start Tails from USB drive "__internal" with network unplugged 1:47.603
And I enable persistence 28.185
And I log in to a new session 57.911
And the Additional Software installation service has started 34.949
Then I am notified that the installation succeeded 5:3.442
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:634:in `/^I see the "(.+)" notification(?: after at most (\d+) seconds)?$/'
./features/step_definitions/additional_software_packages.rb:28:in `/^I am notified that the installation succeeded$/'
features/additional_software_packages.feature:39:in `Then I am notified that the installation succeeded'
And Additional Software is correctly configured for package "popularity-contest" 0.000
And the package "popularity-contest" is installed after Additional Software has been started 0.000
After features/support/hooks.rb:515 0.031
After features/support/hooks.rb:330 6.783 
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:57:00)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/01:57:00_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.file_content_var_log_boot.log
Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/01:57:00_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.file_content_run_live-additional-software_log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/01:57:00_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/01:57:00_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/01:57:00_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/01:57:00_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/01:57:00_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/01:57:00_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/01:57:00_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.016
Feature: Additional software
Tags: @product @check_tor_leaks @slow
25:49.045
Scenario The Additional Software dpkg hook notices when persistence is locked down while installing a package
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Before features/support/hooks.rb:507 0.020
Steps
Given a computer 0.243
And I start Tails from USB drive "__internal" and I login with an administration password 3:32.817
And I update APT using apt 11.091
When I install "makepp" using apt 22:4.893
Tor 
Tor operation failed (despite retrying 10 times) with
Timeout::Error: try_for() timeout expired
Last ignored exception was: ExecutionFailedInVM: Command failed: dpkg -s 'makepp' 2>/dev/null | grep -qs '^Status:.*installed$'
error code: 1
stdout: 
stderr: .
<false> is not true.
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/apt.rb:69:in `block in wait_for_package_installation'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/apt.rb:68:in `wait_for_package_installation'
./features/step_definitions/apt.rb:86:in `block (3 levels) in <top (required)>'
./features/step_definitions/apt.rb:82:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:211:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/apt.rb:81:in `block in <top (required)>' (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/apt.rb:81:in `/^I install "(.+)" using apt$/'
features/additional_software_packages.feature:48:in `When I install "makepp" using apt'
Then the Additional Software dpkg hook has been run for package "makepp" and notices the persistence is locked 0.000
And the package "makepp" is installed 0.000
After features/support/hooks.rb:515 0.046
After features/support/hooks.rb:330 5.186 
SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 02:22:56)
Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/02:22:56_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.file_content_var_log_boot.log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/02:22:56_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/02:22:56_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/02:22:56_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/02:22:56_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/02:22:56_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/02:22:56_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/02:22:56_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal
After features/support/hooks.rb:100 0.049
Feature: Additional software
Tags: @product @check_tor_leaks @slow
10:22.267
Scenario My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Before features/support/hooks.rb:507 0.005
Steps
Given a computer 0.178
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 4:47.448
When I uninstall "popularity-contest" using apt 22.061
And I accept removing "popularity-contest" from Additional Software 4.557
Then "popularity-contest" is not in the list of Additional Software 0.669
When I start Synaptic 15.359
And I update APT using Synaptic 23.062
And I install "cowsay" using Synaptic 4:28.929
Tor 
Tor operation failed (despite retrying 10 times) with
Dogtail::Failure: The Dogtail init script raised: SearchError: child of [application | synaptic]: 'Find' dialog
STDOUT:

STDERR:

 (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/apt.rb:180:in `/^I install "(.+)" using Synaptic$/'
features/additional_software_packages.feature:61:in `And I install "cowsay" using Synaptic'
And I accept adding "cowsay" to Additional Software 0.000
Then Additional Software is correctly configured for package "cowsay" 0.000
When I uninstall "cowsay" using apt 0.000
And I refuse removing "cowsay" from Additional Software 0.000
Then Additional Software is correctly configured for package "cowsay" 0.000
When I start "Additional Software" via GNOME Activities Overview 0.000
And I remove "cowsay" from the list of Additional Software using Additional Software GUI 0.000
Then "cowsay" is not in the list of Additional Software 0.000
When I install "cowsay" using apt 0.000
And I refuse adding "cowsay" to Additional Software 0.000
Then "cowsay" is not in the list of Additional Software 0.000
After features/support/hooks.rb:515 0.062
After features/support/hooks.rb:330 5.715 
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:33:24)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/02:33:24_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.file_content_var_log_boot.log
Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/02:33:24_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.file_content_run_live-additional-software_log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/02:33:24_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/02:33:24_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/02:33:24_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/02:33:24_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/02:33:24_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/02:33:24_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/02:33:24_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.journal
After features/support/hooks.rb:100 0.009
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
12:41.768
Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Before features/support/hooks.rb:507 0.005
Steps
Given a computer 0.180
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 3:30.663
And I configure APT to prefer an old version of cowsay 0.025
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 28.672
And I accept adding "cowsay" to Additional Software 9.473
And Additional Software is correctly configured for package "cowsay" 1.356
And I shutdown Tails and wait for the computer to power off 10.964
And I start Tails from USB drive "__internal" with network unplugged 1:45.398
And I enable persistence 13.926
# We need to add back this custom APT source for the Additional Software
# install step, as it was not saved in persistence
And I configure APT to prefer an old version of cowsay 0.028
# 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.096
And I log in to a new session 56.434
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 34.421
And I revert the APT tweaks that made it prefer an old version of cowsay 0.056
# We remove the newest package after it has been downloaded and before
# it is installed, so that the upgrade process fails
And I prepare the Additional Software upgrade process to fail 0.080
And the network is plugged 0.093
And Tor is ready 24.554
And available upgrades have been checked 1.624
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 4.621
And I can open the Additional Software configuration window from the notification 7.191
And I shutdown Tails and wait for the computer to power off 19.751
And I start Tails from USB drive "__internal" with network unplugged 1:45.896
And I enable persistence 16.419
# We need to add back this custom APT source for the Additional Software
# install step, as it was not saved in persistence
And I configure APT to prefer an old version of cowsay 0.032
And I log in to a new session 1:3.307
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 30.873
And I revert the APT tweaks that made it prefer an old version of cowsay 0.051
And the network is plugged 0.086
And Tor is ready 15.481
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/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:688:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:642:in `/^Tor is ready$/'
features/additional_software_packages.feature:114:in `And Tor is ready'
Then the Additional Software upgrade service has started 0.000
And the installed version of package "cowsay" is newer than "3.03+dfsg2-1" 0.000
After features/support/hooks.rb:515 0.050
After features/support/hooks.rb:330 10.194 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 02:46:11)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/02:46:11_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/02:46:11_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/02:46:11_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal
After features/support/hooks.rb:100 0.025
Feature: Upgrading an old Tails USB installation
Tags: @product
1:57.513
Scenario Creating a persistent partition with the old Tails USB installation
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.026
Steps
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login 1:57.330
cannot 
cannot find TailsGreeter.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/common_steps.rb:480:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:276:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:36:in `And I start Tails from USB drive "old" with network unplugged and I login'
Then Tails is running from USB drive "old" 0.000
And I create a persistent partition 0.000
And I take note of which tps features are available 0.000
Then a Tails persistence partition exists on USB drive "old" 0.000
And I shutdown Tails and wait for the computer to power off 0.000
After features/support/hooks.rb:330 6.004 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 02:54:30)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/02:54:30_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/02:54:30_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/02:54:30_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/02:54:30_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.009
Feature: Upgrading an old Tails USB installation
Tags: @product
2:4.017
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:3.837
The 
The Dogtail init script raised: SearchError: descendant of [application | Welcome to Tails!]: child with roleName='password text'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:671:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:703:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:283:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:46:in `And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled'
Then Tails is running from USB drive "old" 0.000
And all tps features are active 0.000
When I write some files expected to persist 0.000
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.000
And all persistence configuration files have safe access rights 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
And I take note of which tps features are available 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 0.000
After features/support/hooks.rb:330 5.515 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:56:40)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/02:56:40_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/02:56:40_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/02:56:40_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/02:56:40_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.009
Feature: Upgrading an old Tails USB installation
Tags: @product
2:2.340
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given a computer 0.493
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.846
The 
The Dogtail init script raised: SearchError: descendant of [application | Welcome to Tails!]: child with roleName='password text'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:671:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:703:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:283:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:73:in `And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled'
Then all tps features from the old Tails version are active 0.000
And Tails is running from USB drive "to_upgrade" 0.000
And the boot device has safe access rights 0.000
And the expected persistent files created with the old Tails version are present in the filesystem 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:330 5.419 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 03:01:39)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/03:01:39_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/03:01:39_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/03:01:39_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/03:01:39_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.009
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
22:51.288
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.393
And no SquashFS delta is installed 0.342
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.654
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.418
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.412
When the network is plugged 0.108
And Tor is ready 25.281
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:11.618
Tor 
Tor operation failed (despite retrying 10 times) with
FindFailed: can not find any of the patterns ["TailsUpgraderUpgradeTo6.2~testoverlayfs.png", "TailsUpgraderFailure.png"] on the screen (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/usb.rb:1301:in `/^I am proposed to install an incremental upgrade to version (.+)$/'
features/usb_upgrade.feature:90:in `Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs'
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.2~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.2~testoverlayfs are present 0.000
And only the 6.2~testoverlayfs SquashFS delta is installed 0.000
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.3~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.000
And only the 6.3~testoverlayfs SquashFS delta is installed 0.000
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.000
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the Upgrader considers the system as up-to-date 0.000
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:330 5.406 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 03:24:36)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/03:24:36_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/03:24:36_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/03:24:36_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/03:24:36_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:46.144
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.265
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.527
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.077
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 22.989
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:12.148
Tor 
Tor operation failed (despite retrying 10 times) with
FindFailed: can not find any of the patterns ["TailsUpgraderUpgradeTo6.2~testoverlayfs.png", "TailsUpgraderFailure.png"] on the screen (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/usb.rb:1301:in `/^I am proposed to install an incremental upgrade to version (.+)$/'
features/usb_upgrade.feature:134:in `Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs'
After features/support/hooks.rb:330 5.422 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 03:47:28)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/03:47:28_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/03:47:28_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/03:47:28_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/03:47:28_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000
Feature: Emergency shutdown
Tags: @product @not_release_blocker
1:57.903
Scenario Tails erases memory on DVD boot medium removal: vfat
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD without network and logged in 8.604
And I prepare Tails for memory erasure tests 0.802
And I plug and mount a 128 MiB USB drive with a vfat filesystem 10.592
And I fill the USB drive with a known pattern 3.422
And I read the content of the test FS 0.074
And patterns cover at least 90% of the test FS size in the guest's memory 3.800 
Pattern coverage: 100.000% (127 MiB out of 127 MiB reference memory)
When I eject the boot medium 0.291
And I wait for Tails to finish wiping the memory 1:30.315
cannot 
cannot find MemoryWipeCompleted.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/erase_memory.rb:232:in `/^I wait for Tails to finish wiping the memory$/'
features/emergency_shutdown.feature:33:in `And I wait for Tails to finish wiping the memory'
Then I find very few patterns in the guest's memory 0.000
After features/support/hooks.rb:330 10.845 
SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: vfat' (at time 03:51:31)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/03:51:31_Tails_erases_memory_on_DVD_boot_medium_removal:_vfat.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/03:51:31_Tails_erases_memory_on_DVD_boot_medium_removal:_vfat.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/03:51:31_Tails_erases_memory_on_DVD_boot_medium_removal:_vfat.journal
After features/support/hooks.rb:100 0.000
Feature: Emergency shutdown
Tags: @product @not_release_blocker
2:31.709
Scenario Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails from DVD without network and logged in 10.016
And I prepare Tails for memory erasure tests 0.982
And I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 45.200
And I fill the USB drive with a known pattern 1.823
And I read the content of the test FS 0.096
And patterns cover at least 99% of the test FS size in the guest's memory 3.033 
Pattern coverage: 106.113% (97 MiB out of 91 MiB reference memory)
When I eject the boot medium 0.342
And I wait for Tails to finish wiping the memory 1:30.213
cannot 
cannot find MemoryWipeCompleted.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/erase_memory.rb:232:in `/^I wait for Tails to finish wiping the memory$/'
features/emergency_shutdown.feature:44:in `And I wait for Tails to finish wiping the memory'
Then I find very few patterns in the guest's memory 0.000
After features/support/hooks.rb:330 10.649 
SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4' (at time 03:54:14)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/03:54:14_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/03:54:14_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/03:54:14_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
7:16.652
Scenario Persistent Greeter options
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 17.601
When I enable persistence 1:22.621
Then no persistent Greeter options were restored 17.120
When I set all Greeter options to non-default values 52.476
And I log in to a new session in German (de) after having activated the Persistent Storage 1:4.882
Then all Greeter options are set to non-default values 0.240
When I cold reboot the computer 13.010
And the computer reboots Tails 2:22.982
Given I enable persistence 26.299
Then persistent Greeter options were restored 0.636
When I log in to a new session after having activated the Persistent Storage 18.781
The 
The Dogtail init script raised: SearchError: descendant of [application | Welcome to Tails!]: child with name='Start Tails' 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/common_steps.rb:516:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
features/persistence.feature:113:in `When I log in to a new session after having activated the Persistent Storage'
Then all Greeter options are set to non-default values 0.000
After features/support/hooks.rb:330 7.301 
SCENARIO FAILED: 'Persistent Greeter options' (at time 06:26:08)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/06:26:08_Persistent_Greeter_options.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/06:26:08_Persistent_Greeter_options.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/06:26:08_Persistent_Greeter_options.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/06:26:08_Persistent_Greeter_options.journal
After features/support/hooks.rb:100 0.010
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
55.802
Scenario Chatting with some friend over XMPP
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.043
Before features/support/hooks.rb:507 0.051
Steps
Given I have started Tails from DVD and logged in and the network is connected 31.118
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 12.599
Then I see Pidgin's account manager window 6.236
When I create my XMPP account 5.847
cannot 
cannot find PidginAddAccountProtocolXMPP.png on the screen (FindFailed)
./features/support/helpers/screen.rb:157:in `find'
./features/support/helpers/screen.rb:367:in `hover'
./features/support/helpers/screen.rb:394:in `click'
./features/step_definitions/pidgin.rb:126:in `/^I create my XMPP account$/'
features/pidgin.feature:21:in `When I create my XMPP account'
And I close Pidgin's account manager window 0.000
Then Pidgin automatically enables my XMPP account 0.000
Given my XMPP friend goes online 0.000
When I start a conversation with my friend 0.000
And I say something to my friend 0.000
Then I receive a response from my friend 0.000
After features/support/hooks.rb:515 0.039
After features/support/hooks.rb:330 6.080 
SCENARIO FAILED: 'Chatting with some friend over XMPP' (at time 07:14:48)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/07:14:48_Chatting_with_some_friend_over_XMPP.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/07:14:48_Chatting_with_some_friend_over_XMPP.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/07:14:48_Chatting_with_some_friend_over_XMPP.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/07:14:48_Chatting_with_some_friend_over_XMPP.journal
After features/support/hooks.rb:100 0.000
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
41.147
Scenario Chatting with some friend over XMPP in a multi-user chat
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Before features/support/hooks.rb:507 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 19.697
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.914
Then I see Pidgin's account manager window 4.694
When I create my XMPP account 4.840
cannot 
cannot find PidginAddAccountProtocolXMPP.png on the screen (FindFailed)
./features/support/helpers/screen.rb:157:in `find'
./features/support/helpers/screen.rb:367:in `hover'
./features/support/helpers/screen.rb:394:in `click'
./features/step_definitions/pidgin.rb:126:in `/^I create my XMPP account$/'
features/pidgin.feature:34:in `When I create my XMPP account'
And I close Pidgin's account manager window 0.000
Then Pidgin automatically enables my XMPP account 0.000
When I join some empty multi-user chat 0.000
And I clear the multi-user chat's scrollback 0.000
And my XMPP friend goes online and joins the multi-user chat 0.000
Then I can see that my friend joined the multi-user chat 0.000
And I say something to my friend in the multi-user chat 0.000
Then I receive a response from my friend in the multi-user chat 0.000
When I say https://gitlab.tails.boum.org/tails to my friend in the multi-user chat 0.000
Then I see the Tails GitLab URL 0.000
When I wait 10 seconds 0.000
And I click on the Tails GitLab URL 0.000
Then the Tor Browser loads the Tails GitLab 0.000
After features/support/hooks.rb:515 0.061
After features/support/hooks.rb:330 9.907 
SCENARIO FAILED: 'Chatting with some friend over XMPP in a multi-user chat' (at time 07:15:38)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/07:15:38_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/07:15:38_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/07:15:38_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/07:15:38_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:17.996
Scenario The Tor Browser cannot access the LAN
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Steps
Given I have started Tails from DVD and logged in and the network is connected 35.479
And a web server is running on the LAN 1.125
And I capture all network traffic 0.008
When I start the Tor Browser 41.382
cannot 
cannot find TorBrowserNewTabButton.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:495:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:482:in `/^I start the Tor Browser( in offline mode)?$/'
features/torified_browsing.feature:11:in `When I start the Tor Browser'
And the Tor Browser loads the startup page 0.000
And I open a page on the LAN web server in the Tor Browser 0.000
Then the Tor Browser shows the "Unable to connect" error 0.000
And no traffic was sent to the web server on the LAN 0.000
After features/support/hooks.rb:330 14.084 
SCENARIO FAILED: 'The Tor Browser cannot access the LAN' (at time 08:18:51)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/08:18:51_The_Tor_Browser_cannot_access_the_LAN.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/08:18:51_The_Tor_Browser_cannot_access_the_LAN.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/08:18:51_The_Tor_Browser_cannot_access_the_LAN.journal
After features/support/hooks.rb:100 0.049
Feature: Browsing the web using the Tor Browser
Tags: @product
2:12.908
Scenario I can view a file stored in "~/Downloads" but not in ~/.gnupg
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails from DVD and logged in and the network is connected 28.636
And I copy "/usr/share/synaptic/html/index.html" to "/home/amnesia/Downloads/synaptic.html" as user "amnesia" 0.552
And I copy "/usr/share/synaptic/html/index.html" to "/home/amnesia/.gnupg/synaptic.html" as user "amnesia" 0.672
And I copy "/usr/share/synaptic/html/index.html" to "/tmp/synaptic.html" as user "amnesia" 0.336
Then the file "/home/amnesia/.gnupg/synaptic.html" exists 0.837
And the file "/lib/live/mount/overlay/rw/home/amnesia/.gnupg/synaptic.html" exists 1.336
And the file "/live/overlay/rw/home/amnesia/.gnupg/synaptic.html" exists 0.541
And the file "/tmp/synaptic.html" exists 0.514
Given I start monitoring the AppArmor log of "torbrowser_firefox" 0.456
When I start the Tor Browser 42.337
And the Tor Browser loads the startup page 2.835
And I open the address "file:///home/amnesia/Downloads/synaptic.html" in the Tor Browser 46.791
Then I see "TorBrowserSynapticManual.png" after at most 5 seconds 7.060
cannot 
cannot find TorBrowserSynapticManual.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/common_steps.rb:793:in `/^I (do not )?see "([^"]*)" after at most (\d+) seconds$/'
features/torified_browsing.feature:62:in `Then I see "TorBrowserSynapticManual.png" after at most 5 seconds'
And AppArmor has not denied "torbrowser_firefox" from opening "/home/amnesia/Downloads/synaptic.html" 0.000
When I open the address "file:///home/amnesia/.gnupg/synaptic.html" in the Tor Browser 0.000
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.000
When I open the address "file:///lib/live/mount/overlay/rw/home/amnesia/.gnupg/synaptic.html" in the Tor Browser 0.000
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.000
When I open the address "file:///live/overlay/rw/home/amnesia/.gnupg/synaptic.html" in the Tor Browser 0.000
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.000
When I open the address "file:///tmp/synaptic.html" in the Tor Browser 0.000
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.000
After features/support/hooks.rb:330 14.598 
SCENARIO FAILED: 'I can view a file stored in "~/Downloads" but not in ~/.gnupg' (at time 08:34:28)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/08:34:28_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/08:34:28_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/08:34:28_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:37.278
Scenario The Tor Browser's circuit view feature works as expected
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Steps
Given I have started Tails from DVD and logged in and the network is connected 58.270
When I start the Tor Browser 39.008
cannot 
cannot find TorBrowserNewTabButton.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:495:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:482:in `/^I start the Tor Browser( in offline mode)?$/'
features/torified_browsing.feature:92:in `When I start the Tor Browser'
And the Tor Browser loads the startup page 0.000
Then Tor Browser's circuit view is working 0.000
After features/support/hooks.rb:330 12.795 
SCENARIO FAILED: 'The Tor Browser's circuit view feature works as expected' (at time 08:40:31)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/08:40:31_The_Tor_Browser_s_circuit_view_feature_works_as_expected.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/08:40:31_The_Tor_Browser_s_circuit_view_feature_works_as_expected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/08:40:31_The_Tor_Browser_s_circuit_view_feature_works_as_expected.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
48.237
Scenario The Persistent directory is usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.023
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.245
And the network is plugged 0.089
And I successfully configure Tor 26.903
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/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:688:in `/^I successfully configure Tor$/'
features/torified_browsing.feature:108:in `And I successfully configure Tor'
And available upgrades have been checked 0.000
And all notifications have disappeared 0.000
And there is a GNOME bookmark for the Persistent directory 0.000
When I start the Tor Browser 0.000
And I download some file in the Tor Browser to the Persistent directory 0.000
Then the file is saved to the Persistent directory 0.000
When I open the address "https://tails.net/about" in the Tor Browser 0.000
Then "Tails - How Tails works" has loaded in the Tor Browser 0.000
And I can print the current page as "output.pdf" to the Persistent directory 0.000
After features/support/hooks.rb:330 8.300 
SCENARIO FAILED: 'The Persistent directory is usable in Tor Browser' (at time 08:44:05)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/08:44:05_The_Persistent_directory_is_usable_in_Tor_Browser.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/08:44:05_The_Persistent_directory_is_usable_in_Tor_Browser.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/08:44:05_The_Persistent_directory_is_usable_in_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/08:44:05_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
2:52.148
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Steps
Given I have started Tails from DVD without network and logged in 1:7.163
Then the live user's Documents directory exists 2.642
And there is a GNOME bookmark for the Documents directory 21.135
Then I start the Tor Browser in offline mode 32.589
And I can save the current page as "index.html" to the Documents GNOME bookmark 48.616
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'org.gnome.Nautilus' application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/browser.rb:8:in `new'
./features/step_definitions/browser.rb:8:in `block in desktop_portal_save_as'
./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/browser.rb:7:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:47:in `browser_save_page_as'
./features/step_definitions/browser.rb:559:in `block in <top (required)>' (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:7:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:47:in `browser_save_page_as'
./features/step_definitions/browser.rb:559:in `/^I (can|cannot) save the current page as "([^"]+[.]html)" to the (.*) (directory|GNOME bookmark)$/'
features/torified_browsing.feature:127:in `And I can save the current page as "index.html" to the Documents GNOME bookmark'
features/torified_browsing.feature:124:in `And I can save the current page as "index.html" to the <dir> GNOME bookmark'
After features/support/hooks.rb:330 10.098 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#1)' (at time 08:47:06)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/08:47:06_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/08:47:06_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/08:47:06_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/08:47:06_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
2:8.157
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Steps
Given I have started Tails from DVD without network and logged in 20.443
Then the live user's Downloads directory exists 0.083
And there is a GNOME bookmark for the Downloads directory 27.507
Then I start the Tor Browser in offline mode 46.811
And I can save the current page as "index.html" to the Downloads GNOME bookmark 33.312
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'org.gnome.Nautilus' application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/browser.rb:8:in `new'
./features/step_definitions/browser.rb:8:in `block in desktop_portal_save_as'
./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/browser.rb:7:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:47:in `browser_save_page_as'
./features/step_definitions/browser.rb:559:in `block in <top (required)>' (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:7:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:47:in `browser_save_page_as'
./features/step_definitions/browser.rb:559:in `/^I (can|cannot) save the current page as "([^"]+[.]html)" to the (.*) (directory|GNOME bookmark)$/'
features/torified_browsing.feature:128:in `And I can save the current page as "index.html" to the Downloads GNOME bookmark'
features/torified_browsing.feature:124:in `And I can save the current page as "index.html" to the <dir> GNOME bookmark'
After features/support/hooks.rb:330 11.540 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#2)' (at time 08:49:25)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/08:49:25_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/08:49:25_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/08:49:25_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
2:10.723
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD without network and logged in 19.826
Then the live user's Music directory exists 0.601
And there is a GNOME bookmark for the Music directory 27.641
Then I start the Tor Browser in offline mode 45.369
And I can save the current page as "index.html" to the Music GNOME bookmark 37.284
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'org.gnome.Nautilus' application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/browser.rb:8:in `new'
./features/step_definitions/browser.rb:8:in `block in desktop_portal_save_as'
./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/browser.rb:7:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:47:in `browser_save_page_as'
./features/step_definitions/browser.rb:559:in `block in <top (required)>' (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:7:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:47:in `browser_save_page_as'
./features/step_definitions/browser.rb:559:in `/^I (can|cannot) save the current page as "([^"]+[.]html)" to the (.*) (directory|GNOME bookmark)$/'
features/torified_browsing.feature:129:in `And I can save the current page as "index.html" to the Music GNOME bookmark'
features/torified_browsing.feature:124:in `And I can save the current page as "index.html" to the <dir> GNOME bookmark'
After features/support/hooks.rb:330 8.743 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#3)' (at time 08:51:47)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/08:51:47_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___3_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/08:51:47_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/08:51:47_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/08:51:47_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
2:8.418
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Steps
Given I have started Tails from DVD without network and logged in 20.546
Then the live user's Pictures directory exists 0.173
And there is a GNOME bookmark for the Pictures directory 26.202
Then I start the Tor Browser in offline mode 36.152
And I can save the current page as "index.html" to the Pictures GNOME bookmark 45.344
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'org.gnome.Nautilus' application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/browser.rb:8:in `new'
./features/step_definitions/browser.rb:8:in `block in desktop_portal_save_as'
./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/browser.rb:7:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:47:in `browser_save_page_as'
./features/step_definitions/browser.rb:559:in `block in <top (required)>' (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:7:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:47:in `browser_save_page_as'
./features/step_definitions/browser.rb:559:in `/^I (can|cannot) save the current page as "([^"]+[.]html)" to the (.*) (directory|GNOME bookmark)$/'
features/torified_browsing.feature:130:in `And I can save the current page as "index.html" to the Pictures GNOME bookmark'
features/torified_browsing.feature:124:in `And I can save the current page as "index.html" to the <dir> GNOME bookmark'
After features/support/hooks.rb:330 11.042 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#4)' (at time 08:54:06)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/08:54:06_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___4_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/08:54:06_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___4_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/08:54:06_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
2:6.641
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Steps
Given I have started Tails from DVD without network and logged in 19.820
Then the live user's Videos directory exists 0.502
And there is a GNOME bookmark for the Videos directory 28.488
Then I start the Tor Browser in offline mode 33.505
And I can save the current page as "index.html" to the Videos GNOME bookmark 44.324
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'org.gnome.Nautilus' application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/browser.rb:8:in `new'
./features/step_definitions/browser.rb:8:in `block in desktop_portal_save_as'
./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/browser.rb:7:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:47:in `browser_save_page_as'
./features/step_definitions/browser.rb:559:in `block in <top (required)>' (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:7:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:47:in `browser_save_page_as'
./features/step_definitions/browser.rb:559:in `/^I (can|cannot) save the current page as "([^"]+[.]html)" to the (.*) (directory|GNOME bookmark)$/'
features/torified_browsing.feature:131:in `And I can save the current page as "index.html" to the Videos GNOME bookmark'
features/torified_browsing.feature:124:in `And I can save the current page as "index.html" to the <dir> GNOME bookmark'
After features/support/hooks.rb:330 11.671 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#5)' (at time 08:56:24)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/08:56:24_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___5_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/08:56:24_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___5_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/08:56:24_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
8:52.089
Scenario Persistent browser bookmarks
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.460
And all tps features are active 3.320
And all persistent filesystems have safe access rights 2.439
And all persistence configuration files have safe access rights 2.092
And all persistent directories have safe access rights 7.946
When I start the Tor Browser in offline mode 58.674
And I add a bookmark to eff.org in the Tor Browser 29.535
And I cold reboot the computer 33.659
And the computer reboots Tails 2:58.377
And I enable persistence 41.013
And I log in to a new session 1:5.393
And all notifications have disappeared 21.973
And I start the Tor Browser in offline mode 55.497
Then the Tor Browser has a bookmark to eff.org 11.702
cannot 
cannot find TorBrowserEFFBookmark.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:542:in `/^the Tor Browser has a bookmark to eff.org$/'
features/torified_browsing.feature:147:in `Then the Tor Browser has a bookmark to eff.org'
After features/support/hooks.rb:330 9.804 
SCENARIO FAILED: 'Persistent browser bookmarks' (at time 09:05:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/09:05:26_Persistent_browser_bookmarks.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/09:05:26_Persistent_browser_bookmarks.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/09:05:26_Persistent_browser_bookmarks.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/09:05:26_Persistent_browser_bookmarks.journal
After features/support/hooks.rb:100 0.019
Feature: Using Totem
Tags: @product
2:20.323
Scenario Watching a MP4 video stored on the non-persistent filesystem
Steps
Given I have started Tails from DVD without network and logged in 50.689
And I plug and mount a USB drive containing sample videos 52.917
And I copy the sample videos to "/home/amnesia" as user "amnesia" 0.123
And the file "/home/amnesia/video.mp4" exists 0.101
Given I start monitoring the AppArmor log of "/usr/bin/totem" 0.176
When I open "/home/amnesia/video.mp4" with Totem 6.114
Then I see "SampleLocalMp4VideoFrame.png" after at most 40 seconds 12.166
And AppArmor has not denied "/usr/bin/totem" from opening "/home/amnesia/video.mp4" 1.347
Given I close Totem 0.389
And I copy the sample videos to "/home/amnesia/.gnupg" as user "amnesia" 0.227
And the file "/home/amnesia/.gnupg/video.mp4" exists 0.221
And I restart monitoring the AppArmor log of "/usr/bin/totem" 0.302
When I try to open "/home/amnesia/.gnupg/video.mp4" with Totem 3.491
Then Totem tells me it is not allowed to open this file 12.054
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
After features/support/hooks.rb:330 8.047 
SCENARIO FAILED: 'Watching a MP4 video stored on the non-persistent filesystem' (at time 09:10:31)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/09:10:31_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_feature-trixie/39/artifact/build-artifacts/09:10:31_Watching_a_MP4_video_stored_on_the_non-persistent_filesystem.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/09:10:31_Watching_a_MP4_video_stored_on_the_non-persistent_filesystem.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/09:10:31_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:55.434
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 23.155
And I plug and mount a USB drive containing sample videos 41.234
And I copy the sample videos to "/home/amnesia/Persistent" as user "amnesia" 0.092
When I open "/home/amnesia/Persistent/video.mp4" with Totem 14.442
Then I see "SampleLocalMp4VideoFrame.png" after at most 40 seconds 20.200
Given I close Totem 2.146
And I start monitoring the AppArmor log of "/usr/bin/totem" 0.218
And I copy the sample videos to "/home/amnesia/.gnupg" as user "amnesia" 0.069
When I try to open "/home/amnesia/.gnupg/video.mp4" with Totem 2.418
Then Totem tells me it is not allowed to open this file 11.455
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
After features/support/hooks.rb:330 6.385 
SCENARIO FAILED: 'Watching MP4 videos stored on the persistent volume should work as expected given our AppArmor confinement' (at time 09:13:27)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/09:13:27_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_feature-trixie/39/artifact/build-artifacts/09:13:27_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_feature-trixie/39/artifact/build-artifacts/09:13:27_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_feature-trixie/39/artifact/build-artifacts/09:13:27_Watching_MP4_videos_stored_on_the_persistent_volume_should_work_as_expected_given_our_AppArmor_confinement.journal
After features/support/hooks.rb:100 0.001
Feature: Browsing the web using the Unsafe Browser
Tags: @product @not_release_blocker
1:58.038
Scenario Starting a second instance of the Unsafe Browser results in an error message being shown
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails from DVD and logged in and the network is connected 37.849
When I successfully start the Unsafe Browser 38.912
# 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.009 
Slept for 10 seconds
And I try to start the Unsafe Browser 1.264
Then I see a warning about another instance already running 30.002
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'zenity' application
STDOUT:

STDERR:


./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 `block (2 levels) in <top (required)>'
./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/unsafe_browser.rb:75:in `block in <top (required)>' (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/unsafe_browser.rb:75:in `/^I see a warning about another instance already running$/'
features/unsafe_browser.feature:59:in `Then I see a warning about another instance already running'
After features/support/hooks.rb:330 13.229 
SCENARIO FAILED: 'Starting a second instance of the Unsafe Browser results in an error message being shown' (at time 09:24:50)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/09:24:50_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/09:24:50_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/09:24:50_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
1:22.212
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.125
Steps
Given I have started Tails from DVD without network and logged in 1:22.212
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:98:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ without\ network\ and\ logged\ in$/'
features/veracrypt.feature:8:in `Given I have started Tails from DVD without network and logged in'
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
0.000
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 0.000
And I cancel the GNOME authentication prompt 0.000
And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 0.000
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt volume 0.000
Then the VeraCrypt volume has been unmounted and locked 0.000
After features/support/hooks.rb:330 6.507 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a USB drive that has a basic VeraCrypt volume' (at time 09:32:48)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/09:32:48_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/09:32:48_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/09:32:48_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/39/artifact/build-artifacts/09:32:48_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.journal
After features/support/hooks.rb:100 0.000