Project Number Date
test_Tails_ISO_21002-ponytail-keyboard-input 7 09 Jun 2025, 04:47

Failures Overview

The following summary displays scenarios that failed.

Feature: Root access control enforcement
Tags: @product
1:31.153
Scenario If cannot perform administrative tasks unless I have set up an administration password in the Welcome Screen
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 1:6.269
And running a command as root with pkexec requires PolicyKit administrator privileges 0.131
Then I cannot run a command as root with sudo and the standard passwords 0.225
And I cannot run a command as root with pkexec and the standard passwords 20.634
Then I cannot login as root using su with the standard passwords 3.891
<nil> 
<nil> was expected to not be nil. (Test::Unit::AssertionFailedError)
./features/step_definitions/root_access_control.rb:25:in `block (2 levels) in <top (required)>'
./features/step_definitions/root_access_control.rb:19:in `each'
./features/step_definitions/root_access_control.rb:19:in `/^I cannot login as root using su with the standard passwords$/'
features/root_access_control.feature:17:in `Then I cannot login as root using su with the standard passwords'
After features/support/hooks.rb:330 5.803 
SCENARIO FAILED: 'If cannot perform administrative tasks unless I have set up an administration password in the Welcome Screen' (at time 00:15:57)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/00:15:57_If_cannot_perform_administrative_tasks_unless_I_have_set_up_an_administration_password_in_the_Welcome_Screen.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/00:15:57_If_cannot_perform_administrative_tasks_unless_I_have_set_up_an_administration_password_in_the_Welcome_Screen.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/00:15:57_If_cannot_perform_administrative_tasks_unless_I_have_set_up_an_administration_password_in_the_Welcome_Screen.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/00:15:57_If_cannot_perform_administrative_tasks_unless_I_have_set_up_an_administration_password_in_the_Welcome_Screen.journal
After features/support/hooks.rb:100 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product
1:12.468
Scenario TCA can scan QR code after a connection failure
Steps
Given the Tor network and default bridges are blocked 1.864
When I unsuccessfully configure a direct connection in the Tor Connection Assistant 30.408
Then the Tor Connection Assistant reports that it failed to connect 0.123
And tca.conf is empty 1.155
Given I scan a QR code from the error page in Tor Connection Assistant 38.916
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:737:in `/^I scan a QR code from the error page in Tor Connection Assistant$/'
features/tor_bridges.feature:39:in `Given I scan a QR code from the error page in Tor Connection Assistant'
And I retry connecting to Tor 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:330 6.419 
SCENARIO FAILED: 'TCA can scan QR code after a connection failure' (at time 00:32:10)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/00:32:10_TCA_can_scan_QR_code_after_a_connection_failure.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/00:32:10_TCA_can_scan_QR_code_after_a_connection_failure.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/00:32:10_TCA_can_scan_QR_code_after_a_connection_failure.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/00:32:10_TCA_can_scan_QR_code_after_a_connection_failure.journal
After features/support/hooks.rb:100 0.040
Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
16.782
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 9.134
And I prepare Tails for memory erasure tests 0.811
When I start a process allocating 128 MiB of memory with a known pattern 2.569
Then patterns cover at least 128 MiB in the guest's memory 4.266
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.579 
SCENARIO FAILED: 'Erasure of memory freed by killed userspace processes' (at time 00:39:01)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/00:39:01_Erasure_of_memory_freed_by_killed_userspace_processes.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/00:39:01_Erasure_of_memory_freed_by_killed_userspace_processes.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/00:39:01_Erasure_of_memory_freed_by_killed_userspace_processes.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/00:39:01_Erasure_of_memory_freed_by_killed_userspace_processes.journal
After features/support/hooks.rb:100 0.000
Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
7:44.297
Scenario Erasure of read and write disk caches of persistent data on shutdown
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7:44.297
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/erase_memory.feature:75:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I prepare Tails for memory erasure tests 0.000
When I fill a 128 MiB file with a known pattern on the persistent filesystem 0.000
When I trigger shutdown 0.000
Then I find very few patterns in the guest's memory after 20 seconds 0.000
After features/support/hooks.rb:330 5.276 
SCENARIO FAILED: 'Erasure of read and write disk caches of persistent data on shutdown' (at time 00:50:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/00:50:35_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/00:50:35_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/00:50:35_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/00:50:35_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.journal
After features/support/hooks.rb:100 0.011
Feature: Installing Tails to a USB drive
Tags: @product
21.333
Scenario Installing Tails with Tails Installer to a used USB drive, cloning the Persistent Storage
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.333
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_install.feature:45:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I create a file in the Persistent directory 0.000
And I temporarily create a 7200 MiB disk named "install" 0.000
And I create a gpt partition with a vfat filesystem on disk "install" 0.000
And I plug USB drive "install" 0.000
And I install Tails with Persistent Storage to USB drive "install" by cloning 0.000
Then the running Tails is installed on USB drive "install" 0.000
And there is a random seed on USB drive "install" 0.000
And there is a persistence partition on USB drive "install" 0.000
And the USB drive "install" contains the same files as my persistent storage 0.000
After features/support/hooks.rb:330 6.149 
SCENARIO FAILED: 'Installing Tails with Tails Installer to a used USB drive, cloning the Persistent Storage' (at time 00:57:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/00:57:35_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/00:57:35_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/00:57:35_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/00:57:35_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.journal
After features/support/hooks.rb:100 0.000
Feature: Installing Tails to a USB drive
Tags: @product
19.547
Scenario Installing Tails with Tails Installer to a pristine USB drive, without cloning the Persistent Storage
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.547
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_install.feature:57:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I temporarily create a 7200 MiB disk named "install" 0.000
And I plug USB drive "install" 0.000
And I install Tails to USB drive "install" by cloning 0.000
Then the running Tails is installed on USB drive "install" 0.000
And there is a random seed on USB drive "install" 0.000
And there is no persistence partition on USB drive "install" 0.000
After features/support/hooks.rb:330 5.781 
SCENARIO FAILED: 'Installing Tails with Tails Installer to a pristine USB drive, without cloning the Persistent Storage' (at time 00:58:00)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/00:58:00_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive,_without_cloning_the_Persistent_Storage.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/00:58:00_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive,_without_cloning_the_Persistent_Storage.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/00:58:00_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive,_without_cloning_the_Persistent_Storage.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/00:58:00_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive,_without_cloning_the_Persistent_Storage.journal
After features/support/hooks.rb:100 0.000
Feature: Installing Tails to a USB drive
Tags: @product
19.409
Scenario Re-installing Tails over an existing USB installation with a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
# We reach this first checkpoint only to ensure that the ' __internal' disk has reached the state (Tails installed + persistent partition set up) we need before we clone it below.
# This first part is done without Tails Installer (install from Tails USB image)
# Note: the "__internal" disk will keep its state across scenarios
# and features until one of its snapshots is restored.
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.409
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_install.feature:70:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I have started Tails from DVD without network and logged in 0.000
And I clone USB drive "__internal" to a temporary USB drive "install" 0.000
And I plug USB drive "install" 0.000
# This second part is done with Tails Installer, that's what this scenario is about
When I reinstall Tails to USB drive "install" by cloning 0.000
Then the running Tails is installed on USB drive "install" 0.000
And there is a random seed on USB drive "install" 0.000
And there is no persistence partition on USB drive "install" 0.000
After features/support/hooks.rb:330 5.544 
SCENARIO FAILED: 'Re-installing Tails over an existing USB installation with a persistent partition' (at time 00:58:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/00:58:26_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/00:58:26_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/00:58:26_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/00:58:26_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.journal
After features/support/hooks.rb:100 0.000
Feature: Additional software
Tags: @product @check_tor_leaks @slow
4:50.807
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.003
Before features/support/hooks.rb:513 0.012
Steps
Given I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login 1:25.200
And I update APT using apt 11.215
And I install "popularity-contest" using apt 26.746
Then I am proposed to add the "popularity-contest" package to my Additional Software 9.385
When I create a persistent storage and activate the Additional Software feature 23.241
Then Additional Software is correctly configured for package "popularity-contest" 2.579
When I shutdown Tails and wait for the computer to power off 14.787
And I start Tails from USB drive "__internal" with network unplugged 1:46.985
And I enable persistence 10.663
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/additional_software_packages.feature:36:in `And I enable persistence'
And I log in to a new session 0.000
And the Additional Software installation service has started 0.000
Then I am notified that the installation succeeded 0.000
And Additional Software is correctly configured for package "popularity-contest" 0.000
And the package "popularity-contest" is installed after Additional Software has been started 0.000
After features/support/hooks.rb:521 0.060
After features/support/hooks.rb:330 5.620 
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:11:16)
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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:11:16_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.file_content_var_log_boot.log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:11:16_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:11:16_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:11:16_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:11:16_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:11:16_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:11:16_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:11:16_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.009
Feature: Additional software
Tags: @product @check_tor_leaks @slow
25:19.014
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.003
Before features/support/hooks.rb:513 0.003
Steps
Given a computer 0.171
And I start Tails from USB drive "__internal" and I login with an administration password 3:1.284
And I update APT using apt 12.096
When I install "makepp" using apt 22:5.462
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:521 0.041
After features/support/hooks.rb:330 5.329 
SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 01:36:41)
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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:36:41_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:36:41_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:36:41_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:36:41_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:36:41_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:36:41_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:36:41_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:36:41_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal
After features/support/hooks.rb:100 0.008
Feature: Additional software
Tags: @product @check_tor_leaks @slow
1:58.853
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.002
Before features/support/hooks.rb:513 0.002
Steps
Given a computer 0.171
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 1:58.681
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/additional_software_packages.feature:55:in `And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password'
When I uninstall "popularity-contest" using apt 0.000
And I accept removing "popularity-contest" from Additional Software 0.000
Then "popularity-contest" is not in the list of Additional Software 0.000
When I start Synaptic 0.000
And I update APT using Synaptic 0.000
And I install "cowsay" using Synaptic 0.000
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:521 0.047
After features/support/hooks.rb:330 6.030 
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 01:38:45)
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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:38:45_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
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:38:45_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:38:45_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:38:45_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:38:45_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:38:45_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:38:45_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:38:45_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.005
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
1:58.705
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.002
Before features/support/hooks.rb:513 0.002
Steps
Given a computer 0.186
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 1:58.518
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/additional_software_packages.feature:79:in `And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password'
And I configure APT to prefer an old version of cowsay 0.000
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 0.000
And I accept adding "cowsay" to Additional Software 0.000
And Additional Software is correctly configured for package "cowsay" 0.000
And I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged 0.000
And I enable persistence 0.000
# 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.000
# 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.000
And I log in to a new session 0.000
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 0.000
And I revert the APT tweaks that made it prefer an old version of cowsay 0.000
# 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.000
And the network is plugged 0.000
And Tor is ready 0.000
And available upgrades have been checked 0.000
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 0.000
And I can open the Additional Software configuration window from the notification 0.000
And I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged 0.000
And I enable persistence 0.000
# 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.000
And I log in to a new session 0.000
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 0.000
And I revert the APT tweaks that made it prefer an old version of cowsay 0.000
And the network is plugged 0.000
And Tor is ready 0.000
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:521 0.045
After features/support/hooks.rb:330 5.987 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:40:50)
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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:40:50_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:40:50_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:40:50_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:40:50_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:40:50_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:40:50_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:40:50_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:40:50_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.007
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
2:1.706
Scenario I am notified when Additional Software fails to install a package
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Before features/support/hooks.rb:513 0.003
Steps
Given a computer 0.162
And I start Tails from USB drive "__internal" with network unplugged 1:50.862
And I enable persistence 10.681
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/additional_software_packages.feature:123:in `And I enable persistence'
And I remove the "cowsay" deb files from the APT cache 0.000
# 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.000
And I log in to a new session 0.000
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 0.000
And I can open the Additional Software log file from the notification 0.000
And the package "cowsay" is not installed 0.000
After features/support/hooks.rb:521 0.032
After features/support/hooks.rb:330 5.717 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 01:42:58)
Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:42:58_I_am_notified_when_Additional_Software_fails_to_install_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:42:58_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:42:58_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:42:58_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:42:58_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:42:58_I_am_notified_when_Additional_Software_fails_to_install_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:42:58_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:42:58_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal
After features/support/hooks.rb:100 0.006
Feature: Upgrading an old Tails USB installation
Tags: @product
3:7.501
Scenario Installing an old version of Tails to a pristine USB drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 33.623
When I start Tails from USB drive "old" with network unplugged 2:32.600
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:427:in `wait_for_ponytail'
./features/step_definitions/common_steps.rb:463:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:276:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:25:in `When I start Tails from USB drive "old" with network unplugged'
Then the boot device has safe access rights 0.000
And Tails is running from USB drive "old" 0.000
And there is no persistence partition on USB drive "old" 0.000
And process "udev-watchdog" is running 0.000
And udev-watchdog is monitoring the correct device 0.000
And I unplug USB drive "old" 0.000
After features/support/hooks.rb:330 7.790 
SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 01:46:11)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:46:11_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:46:11_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:46:11_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.journal
After features/support/hooks.rb:100 0.018
Feature: Upgrading an old Tails USB installation
Tags: @product
2:3.677
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.003
Steps
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 2:3.474
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:427:in `wait_for_ponytail'
./features/step_definitions/common_steps.rb:463:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:276:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:36:in `And I start Tails from USB drive "old" with network unplugged and I login'
Then Tails is running from USB drive "old" 0.000
And I create a persistent partition 0.000
And I take note of which tps features are available 0.000
Then a Tails persistence partition exists on USB drive "old" 0.000
And I shutdown Tails and wait for the computer to power off 0.000
After features/support/hooks.rb:330 5.748 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 01:48:23)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:48:23_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:48:23_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:48:23_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:48:23_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.008
Feature: Upgrading an old Tails USB installation
Tags: @product
2:0.704
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.003
Steps
Given a computer 0.262
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:0.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:427:in `wait_for_ponytail'
./features/step_definitions/common_steps.rb:463:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:276:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:46:in `And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled'
Then Tails is running from USB drive "old" 0.000
And all tps features are active 0.000
When I write some files expected to persist 0.000
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.000
And all persistence configuration files have safe access rights 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
And I take note of which tps features are available 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 0.000
After features/support/hooks.rb:330 5.770 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:50:29)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:50:29_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:50:29_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:50:29_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:50:29_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.006
Feature: Upgrading an old Tails USB installation
Tags: @product
2:2.022
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.003
Steps
Given a computer 0.159
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.863
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 6.153 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:55:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:55:35_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:55:35_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:55:35_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:55:35_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.019
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
22.626
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 22.626
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_upgrade.feature:82:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And no SquashFS delta is installed 0.000
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.000
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.000
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.000
And the file system changes introduced in version 6.3~testoverlayfs are not present 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.2~testoverlayfs 0.000
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.680 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:56:04)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:56:04_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:56:04_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:56:04_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:56:04_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
20.508
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.508
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_upgrade.feature:127:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.000
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.000
And the signing key used by the Upgrader is outdated 0.000
But a current signing key is available on our website 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.2~testoverlayfs 0.000
After features/support/hooks.rb:330 5.602 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 01:56:30)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:56:30_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:56:30_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:56:30_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/01:56:30_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:59.794
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.003
Steps
Given I have started Tails from DVD without network and logged in 8.430
And I prepare Tails for memory erasure tests 0.809
And I plug and mount a 128 MiB USB drive with a vfat filesystem 10.777
And I fill the USB drive with a known pattern 3.179
And I read the content of the test FS 0.068
And patterns cover at least 90% of the test FS size in the guest's memory 4.443 
Pattern coverage: 100.000% (127 MiB out of 127 MiB reference memory)
When I eject the boot medium 1.883
And I wait for Tails to finish wiping the memory 1:30.201
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.731 
SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: vfat' (at time 02:01:59)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:01:59_Tails_erases_memory_on_DVD_boot_medium_removal:_vfat.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:01:59_Tails_erases_memory_on_DVD_boot_medium_removal:_vfat.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:01:59_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:30.884
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.003
Steps
Given I have started Tails from DVD without network and logged in 8.549
And I prepare Tails for memory erasure tests 0.694
And I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 46.274
And I fill the USB drive with a known pattern 1.420
And I read the content of the test FS 0.067
And patterns cover at least 99% of the test FS size in the guest's memory 3.528 
Pattern coverage: 106.113% (97 MiB out of 91 MiB reference memory)
When I eject the boot medium 0.275
And I wait for Tails to finish wiping the memory 1:30.073
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.510 
SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4' (at time 02:04:41)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:04:41_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:04:41_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:04:41_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.journal
After features/support/hooks.rb:100 0.000
Feature: Emergency shutdown
Tags: @product @not_release_blocker
19.797
Scenario Tails erases memory and shuts down on USB boot medium removal: persistent data
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.797
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/emergency_shutdown.feature:48:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I prepare Tails for memory erasure tests 0.000
And I fill a 128 MiB file with a known pattern on the persistent filesystem 0.000
And patterns cover at least 100 MiB in the guest's memory 0.000
When I eject the boot medium 0.000
And I wait for Tails to finish wiping the memory 0.000
Then I find very few patterns in the guest's memory 0.000
And Tails eventually shuts down 0.000
After features/support/hooks.rb:330 5.523 
SCENARIO FAILED: 'Tails erases memory and shuts down on USB boot medium removal: persistent data' (at time 02:05:11)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:05:11_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:05:11_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:05:11_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:05:11_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.journal
After features/support/hooks.rb:100 0.000
Feature: Backing up the persistent storage
Tags: @product
21.058
Scenario Using Tails' custom backup tool to backup a newly added file
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.058
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/backup.feature:8:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
# The volume cannot be in use when GuestFs clones it, which we do below
And I shutdown Tails and wait for the computer to power off 0.000
And I clone USB drive "__internal" to a temporary USB drive "backup" 0.000
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 0.000
And I write a file "/live/persistence/TailsData_unlocked/new" with contents "foo" 0.000
When I start Tails' custom backup tool 0.000
Then the backup tool displays "Plug in your backup Tails USB stick" 0.000
When I plug USB drive "backup" 0.000
And I give the Persistent Storage on drive "backup" its own UUID 0.000
And I click "Retry" in the backup tool 0.000
Then the backup tool displays "Do you want to back up your Persistent Storage now?" 0.000
When I click "Back Up" in the backup tool 0.000
And I enter my persistent storage passphrase into the polkit prompt 0.000
Then the backup tool displays "Your Persistent Storage was backed up successfully to your backup Tails USB stick!" 0.000
# The backup tool ejects the drive, so we have to replug it
When I unplug USB drive "backup" 0.000
And I plug USB drive "backup" 0.000
Then the USB drive "backup" contains the same files as my persistent storage 0.000
After features/support/hooks.rb:330 5.588 
SCENARIO FAILED: 'Using Tails' custom backup tool to backup a newly added file' (at time 02:07:24)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:07:24_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:07:24_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:07:24_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:07:24_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal
After features/support/hooks.rb:100 0.000
Feature: Getting a DHCP lease without leaking too much information
Tags: @product
0.085
Scenario Getting a DHCP lease with the default NetworkManager connection
Steps
Then the hostname should not have been leaked on the network 0.085
Hostname 
Hostname leak detected (DhcpLeakError)
./features/step_definitions/dhcp.rb:15:in `/^the hostname should not have been leaked on the network$/'
features/dhcp.feature:17:in `Then the hostname should not have been leaked on the network'
After features/support/hooks.rb:330 4.939 
SCENARIO FAILED: 'Getting a DHCP lease with the default NetworkManager connection' (at time 02:08:14)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:08:14_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.file_content_var_log_boot.log
Network capture: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:08:14_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.pcap
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:08:14_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:08:14_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:08:14_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.journal
After features/support/hooks.rb:100 0.037
Feature: Getting a DHCP lease without leaking too much information
Tags: @product
1.074
Scenario Getting a DHCP lease with a manually configured NetworkManager connection
Steps
When I add a wired DHCP NetworkManager connection called "manually-added-con" 0.452
And I switch to the "manually-added-con" NetworkManager connection 0.524
Then the hostname should not have been leaked on the network 0.097
Hostname 
Hostname leak detected (DhcpLeakError)
./features/step_definitions/dhcp.rb:15:in `/^the hostname should not have been leaked on the network$/'
features/dhcp.feature:22:in `Then the hostname should not have been leaked on the network'
After features/support/hooks.rb:330 4.942 
SCENARIO FAILED: 'Getting a DHCP lease with a manually configured NetworkManager connection' (at time 02:08:52)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:08:52_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.file_content_var_log_boot.log
Network capture: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:08:52_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.pcap
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:08:52_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:08:52_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:08:52_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.journal
After features/support/hooks.rb:100 0.044
Feature: Using Evince
Tags: @product
20.223
Scenario I can view and print a PDF file stored in persistent /home/amnesia/Persistent
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.223
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/evince.feature:45:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I copy "/usr/share/cups/data/default-testpage.pdf" to "/home/amnesia/Persistent" as user "amnesia" 0.000
Then the file "/home/amnesia/Persistent/default-testpage.pdf" exists 0.000
When I open "/home/amnesia/Persistent/default-testpage.pdf" with Evince 0.000
Then I see "CupsTestPage.png" after at most 40 seconds 0.000
And I can print the current document to "/home/amnesia/Persistent/output.pdf" 0.000
After features/support/hooks.rb:330 5.611 
SCENARIO FAILED: 'I can view and print a PDF file stored in persistent /home/amnesia/Persistent' (at time 02:12:46)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:12:46_I_can_view_and_print_a_PDF_file_stored_in_persistent__home_amnesia_Persistent.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:12:46_I_can_view_and_print_a_PDF_file_stored_in_persistent__home_amnesia_Persistent.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:12:46_I_can_view_and_print_a_PDF_file_stored_in_persistent__home_amnesia_Persistent.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:12:46_I_can_view_and_print_a_PDF_file_stored_in_persistent__home_amnesia_Persistent.journal
After features/support/hooks.rb:100 0.000
Feature: Using Evince
Tags: @product @not_release_blocker
21.852
Scenario I cannot view a PDF file stored in persistent /home/amnesia/.gnupg
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.852
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/evince.feature:54:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I copy "/usr/share/cups/data/default-testpage.pdf" to "/home/amnesia/.gnupg" as user "amnesia" 0.000
Then the file "/home/amnesia/.gnupg/default-testpage.pdf" exists 0.000
Given I start monitoring the AppArmor log of "/usr/bin/evince" 0.000
And I try to open "/home/amnesia/.gnupg/default-testpage.pdf" with Evince 0.000
Then Evince tells me it cannot open "/home/amnesia/.gnupg/default-testpage.pdf" 0.000
And AppArmor has denied "/usr/bin/evince" from opening "/home/amnesia/.gnupg/default-testpage.pdf" 0.000
After features/support/hooks.rb:330 5.732 
SCENARIO FAILED: 'I cannot view a PDF file stored in persistent /home/amnesia/.gnupg' (at time 02:13:13)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:13:13_I_cannot_view_a_PDF_file_stored_in_persistent__home_amnesia_.gnupg.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:13:13_I_cannot_view_a_PDF_file_stored_in_persistent__home_amnesia_.gnupg.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:13:13_I_cannot_view_a_PDF_file_stored_in_persistent__home_amnesia_.gnupg.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:13:13_I_cannot_view_a_PDF_file_stored_in_persistent__home_amnesia_.gnupg.journal
After features/support/hooks.rb:100 0.000
Feature: GNOME is well-integrated into Tails
Tags: @product @not_release_blocker
19.421
Scenario A screenshot is taken when the PRINTSCREEN key is pressed
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.899
And I wait 10 seconds 10.001 
Slept for 10 seconds
And there is no screenshot in the live user's Pictures directory 0.505
When I press the "PRINTSCREEN" key 0.015
Ponytail 
Ponytail failed while pressing key combo: ValueError: Cannot find key 'PRINTSCREEN'
STDOUT:

STDERR:

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/common_steps.rb:1220:in `/^I press the "([^"]+)" key$/'
features/gnome.feature:9:in `When I press the "PRINTSCREEN" key'
And GNOME offers me various screenshot options 0.000
And I press the "Return" key 0.000
Then a screenshot is saved to the live user's Pictures directory 0.000
After features/support/hooks.rb:330 5.686 
SCENARIO FAILED: 'A screenshot is taken when the PRINTSCREEN key is pressed' (at time 02:13:39)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:13:39_A_screenshot_is_taken_when_the_PRINTSCREEN_key_is_pressed.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:13:39_A_screenshot_is_taken_when_the_PRINTSCREEN_key_is_pressed.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:13:39_A_screenshot_is_taken_when_the_PRINTSCREEN_key_is_pressed.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:13:39_A_screenshot_is_taken_when_the_PRINTSCREEN_key_is_pressed.journal
After features/support/hooks.rb:100 0.000
Feature: GNOME is well-integrated into Tails
Tags: @product
19.597
Scenario I can launch various apps via GNOME Activities Overview
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
# Some apps (Electrum and Persistent Storage Backup) only start when
# a Persistent Storage is available.
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.597
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/gnome.feature:22:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
# Some apps (Tor Browser) only start when the network is plugged.
And the network is plugged 0.000
And Tor is ready 0.000
And all notifications have disappeared 0.000
When I start "Additional Software" via GNOME Activities Overview 0.000
And I close the "tails-additional-software-config" window 0.000
When I start "Disks" via GNOME Activities Overview 0.000
# The close button of GNOME Disks is not accessible
And I close the "gnome-disks" window via Alt+F4 0.000
When I start "GNOME Terminal" via GNOME Activities Overview 0.000
And I close the "org.gnome.Terminal" window 0.000
When I start "Files" via GNOME Activities Overview 0.000
And I close the "org.gnome.Nautilus" window 0.000
When I start "Persistent Storage" via GNOME Activities Overview 0.000
And I close the "tps-frontend" window 0.000
When I start "Back Up Persistent Storage" via GNOME Activities Overview 0.000
And I close the "zenity" window 0.000
When I start "Pidgin" via GNOME Activities Overview 0.000
And I close the "Pidgin" window via Alt+F4 0.000
When I start "Thunderbird" via GNOME Activities Overview 0.000
And I close the "Thunderbird" window 0.000
When I start "Tor Browser" via GNOME Activities Overview 0.000
And I close the "Firefox" window 0.000
When I start "Unlock VeraCrypt Volumes" via GNOME Activities Overview 0.000
And I close the "unlock-veracrypt-volumes" window 0.000
When I start "Unsafe Browser" via GNOME Activities Overview 0.000
And I close the "Firefox" window 0.000
After features/support/hooks.rb:330 6.978 
SCENARIO FAILED: 'I can launch various apps via GNOME Activities Overview' (at time 02:14:15)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:14:15_I_can_launch_various_apps_via_GNOME_Activities_Overview.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:14:15_I_can_launch_various_apps_via_GNOME_Activities_Overview.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:14:15_I_can_launch_various_apps_via_GNOME_Activities_Overview.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:14:15_I_can_launch_various_apps_via_GNOME_Activities_Overview.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
19.894
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given a computer 0.163
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.731
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/hardware_failure.feature:29:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
features/hardware_failure.feature:23:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
When Tails detects disk read failures on the SquashFS 0.000
Then I see a disk failure message 0.000
Then I can open the hardware failure documentation from the disk failure message 0.000
After features/support/hooks.rb:330 5.546 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 02:17:48)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:17:48_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:17:48_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:17:48_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:17:48_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
19.781
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given a computer 0.223
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.558
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/hardware_failure.feature:30:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
features/hardware_failure.feature:23:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
When Tails detects disk read failures on the boot device 0.000
Then I see a disk failure message 0.000
Then I can open the hardware failure documentation from the disk failure message 0.000
After features/support/hooks.rb:330 6.129 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 02:18:13)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:18:13_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:18:13_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:18:13_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:18:13_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
19.635
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given a computer 0.172
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.463
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/hardware_failure.feature:31:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
features/hardware_failure.feature:23:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
When Tails detects disk read failures on the boot device with a target error 0.000
Then I see a disk failure message 0.000
Then I can open the hardware failure documentation from the disk failure message 0.000
After features/support/hooks.rb:330 5.850 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 02:18:39)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:18:39_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:18:39_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:18:39_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:18:39_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product
2:47.289
Scenario Outline GPT backup corruption with a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 9.685
And I corrupt the boot device's GPT backup header 0.373
And I power off the computer 0.364
When I start the computer 0.997
Then the computer boots Tails 1:47.659
When I log in to a new session 34.942
And all notifications have disappeared 12.988
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.278
<nil> 
<nil> was expected to not be nil. (Test::Unit::AssertionFailedError)
./features/step_definitions/hardware.rb:84:in `/^I am recommended to migrate to a new USB stick due to partitioning errors$/'
features/hardware_failure.feature:45:in `Then I am recommended to migrate to a new USB stick due to partitioning errors'
features/hardware_failure.feature:41:in `Then I am recommended to migrate to a new USB stick due to partitioning errors'
And Tails detected partitioning error partitioning-corruption 0.000
After features/support/hooks.rb:330 6.061 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#1)' (at time 02:21:32)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:21:32_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:21:32_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:21:32_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:21:32_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.journal
After features/support/hooks.rb:100 0.006
Feature: Hardware failures
Tags: @product
2:48.014
Scenario Outline GPT backup corruption with a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 8.936
And I corrupt the boot device's GPT backup partition table 0.396
And I power off the computer 0.336
When I start the computer 1.004
Then the computer boots Tails 1:50.053
When I log in to a new session 33.567
And all notifications have disappeared 13.487
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.233
<nil> 
<nil> was expected to not be nil. (Test::Unit::AssertionFailedError)
./features/step_definitions/hardware.rb:84:in `/^I am recommended to migrate to a new USB stick due to partitioning errors$/'
features/hardware_failure.feature:46:in `Then I am recommended to migrate to a new USB stick due to partitioning errors'
features/hardware_failure.feature:41:in `Then I am recommended to migrate to a new USB stick due to partitioning errors'
And Tails detected partitioning error partitioning-corruption 0.000
After features/support/hooks.rb:330 6.133 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#2)' (at time 02:24:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:24:26_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:24:26_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:24:26_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:24:26_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.journal
After features/support/hooks.rb:100 0.006
Feature: Hardware failures
Tags: @product
4:8.444
Scenario GPT backup corruption without a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given a computer 0.168
And I set Tails to boot with options "test_gpt_corruption=gpt_backup,gpt_backup_table" 0.000
And I temporarily create a 7200 MiB disk named "temp" 0.039
And I plug USB drive "temp" 1.046
And I write the Tails USB image to disk "temp" 31.527
When I start Tails from USB drive "temp" with network unplugged 2:45.134
Then Tails is running from USB drive "temp" 0.398
And the Greeter forbids creating a persistent partition 0.086
When I log in to a new session 36.621
And all notifications have disappeared 13.128
Then I am recommended to reinstall Tails due to partitioning errors 0.289
<"OK"> 
<"OK"> was expected to include
<"Creation of Persistent Storage has been disabled">. (Test::Unit::AssertionFailedError)
./features/step_definitions/hardware.rb:94:in `/^I am recommended to reinstall Tails due to partitioning errors$/'
features/hardware_failure.feature:59:in `Then I am recommended to reinstall Tails due to partitioning errors'
# We are gonna verify the dialog again so we need to clean up the
# first instance.
And I close the "zenity" window 0.000
And I am told that Persistent Storage cannot be created 0.000
And Tails detected partitioning error partitioning-corruption 0.000
After features/support/hooks.rb:330 6.104 
SCENARIO FAILED: 'GPT backup corruption without a persistent partition' (at time 02:28:41)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:28:41_GPT_backup_corruption_without_a_persistent_partition.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:28:41_GPT_backup_corruption_without_a_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:28:41_GPT_backup_corruption_without_a_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:28:41_GPT_backup_corruption_without_a_persistent_partition.journal
After features/support/hooks.rb:100 0.118
Feature: Tails-related cryptographic keys are up-to-date
Tags: @product
8.944
Scenario The included APT repository keys are up-to-date
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails from DVD without network and logged in 8.806
Then the keys trusted by APT are valid for the next 3 months 0.137
Command 
Command failed: apt-key adv --batch --with-colons --fingerprint --list-key
error code: 127
stdout: 
stderr: /bin/sh: 1: apt-key: not found
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/checks.rb:19:in `assert_all_keys_are_valid_for_n_months'
./features/step_definitions/checks.rb:8:in `/^the keys trusted by APT are valid for the next (\d+) months$/'
features/keys.feature:11:in `Then the keys trusted by APT are valid for the next 3 months'
After features/support/hooks.rb:330 5.464 
SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 02:39:00)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:39:00_The_included_APT_repository_keys_are_up-to-date.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:39:00_The_included_APT_repository_keys_are_up-to-date.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:39:00_The_included_APT_repository_keys_are_up-to-date.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/02:39:00_The_included_APT_repository_keys_are_up-to-date.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
2:15.991
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 7.934
When I log in to a new session in Spanish (es) 52.163
Then the keyboard layout is set to "es" 0.157
When the network is plugged 0.112
And Tor is ready 21.263
Then I successfully start the Unsafe Browser 16.329
And I kill the Unsafe Browser 7.657
When I enable the screen keyboard 0.179
Then the screen keyboard works in Tor Browser 30.194
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:1055:in `launch_app'
./features/step_definitions/common_steps.rb:1110:in `launch_tor_browser'
./features/step_definitions/browser.rb:456:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:422:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:54:in `Then the screen keyboard works in Tor Browser'
features/localization.feature:30:in `Then the screen keyboard works in Tor Browser'
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 9.846 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#12)' (at time 03:25:07)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:25:07_Tails_is_localized_for_every_tier-1_language,_Examples___12_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:25:07_Tails_is_localized_for_every_tier-1_language,_Examples___12_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:25:07_Tails_is_localized_for_every_tier-1_language,_Examples___12_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
2:41.645
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 7.864
When I log in to a new session in Turkish (tr) 48.883
Then the keyboard layout is set to "tr" 0.323
When the network is plugged 0.115
And Tor is ready 19.049
Then I successfully start the Unsafe Browser 1:25.408
cannot 
cannot find UnsafeBrowserStartPage.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/unsafe_browser.rb:63:in `/^the Unsafe Browser shows a warning as its start page$/'
./features/step_definitions/unsafe_browser.rb:71:in `/^the Unsafe Browser has started$/'
./features/step_definitions/browser.rb:90:in `/^I successfully start the Unsafe Browser$/'
features/localization.feature:55:in `Then I successfully start the Unsafe Browser'
features/localization.feature:27:in `Then I successfully start the Unsafe Browser'
And I kill the Unsafe Browser 0.000
When I enable the screen keyboard 0.000
Then the screen keyboard works in Tor Browser 0.000
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 8.306 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#13)' (at time 03:27:58)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:27:58_Tails_is_localized_for_every_tier-1_language,_Examples___13_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:27:58_Tails_is_localized_for_every_tier-1_language,_Examples___13_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:27:58_Tails_is_localized_for_every_tier-1_language,_Examples___13_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:27:58_Tails_is_localized_for_every_tier-1_language,_Examples___13_.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
3:5.242
Scenario Creating a Persistent Storage
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 12.360
Then Tails is running from USB drive "__internal" 0.500
When I create a file in the Persistent directory 0.224
And I create a persistent partition with the default settings 24.344
Then the file I created was copied to the Persistent Storage 2.458
When I shutdown Tails and wait for the computer to power off 19.136
And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.218
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/persistence.feature:26:in `And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
Then persistence for "Persistent" is active 0.000
And the file I created in the Persistent directory exists 0.000
After features/support/hooks.rb:330 5.468 
SCENARIO FAILED: 'Creating a Persistent Storage' (at time 03:47:27)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:47:27_Creating_a_Persistent_Storage.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:47:27_Creating_a_Persistent_Storage.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:47:27_Creating_a_Persistent_Storage.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:47:27_Creating_a_Persistent_Storage.journal
After features/support/hooks.rb:100 0.007
Feature: Tails persistence
Tags: @product
25.179
Scenario Booting Tails from a USB drive with an enabled persistent partition and reconfiguring it
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 25.179
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:42:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
Then Tails is running from USB drive "__internal" 0.000
And all tps features are active 0.000
And all persistent directories have safe access rights 0.000
When I disable the first tps feature 0.000
Then all tps features but the first one are active 0.000
And I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then all tps features but the first one are active 0.000
After features/support/hooks.rb:330 6.187 
SCENARIO FAILED: 'Booting Tails from a USB drive with an enabled persistent partition and reconfiguring it' (at time 03:48:56)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:48:56_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:48:56_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:48:56_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:48:56_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
21.075
Scenario Activating and deactivating Persistent Storage features
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.075
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:53:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
Then persistence for "Persistent" is active 0.000
And I create a file in the Persistent directory 0.000
Then the file I created was copied to the Persistent Storage 0.000
When I disable the first tps feature 0.000
Then persistence for "Persistent" is not active 0.000
And the Persistent directory does not exist 0.000
When I enable the first tps feature 0.000
Then persistence for "Persistent" is active 0.000
And the file I created in the Persistent directory exists 0.000
After features/support/hooks.rb:330 5.618 
SCENARIO FAILED: 'Activating and deactivating Persistent Storage features' (at time 03:49:23)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:49:23_Activating_and_deactivating_Persistent_Storage_features.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:49:23_Activating_and_deactivating_Persistent_Storage_features.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:49:23_Activating_and_deactivating_Persistent_Storage_features.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:49:23_Activating_and_deactivating_Persistent_Storage_features.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
20.252
Scenario Deleting data of a Persistent Storage feature
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.252
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:65:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
Then persistence for "Persistent" is active 0.000
When I create a file in the Persistent directory 0.000
And I disable the first tps feature 0.000
And I delete the data of the Persistent Folder feature 0.000
Then the file I created does not exist on the Persistent Storage 0.000
After features/support/hooks.rb:330 5.601 
SCENARIO FAILED: 'Deleting data of a Persistent Storage feature' (at time 03:49:49)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:49:49_Deleting_data_of_a_Persistent_Storage_feature.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:49:49_Deleting_data_of_a_Persistent_Storage_feature.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:49:49_Deleting_data_of_a_Persistent_Storage_feature.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:49:49_Deleting_data_of_a_Persistent_Storage_feature.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
19.913
Scenario Writing files to a read/write-enabled persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.913
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:73:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And the network is plugged 0.000
And Tor is ready 0.000
And I take note of which tps features are available 0.000
When I write some files expected to persist 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# XXX: The next step succeeds (and the --debug output confirms that it's actually looking for the files) but will fail in a subsequent scenario restoring the same snapshot. This exactly what we want, but why does it work? What is guestfs's behaviour when qcow2 internal snapshots are involved?
Then only the expected files are present on the persistence partition on USB drive "__internal" 0.000
After features/support/hooks.rb:330 5.555 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition' (at time 03:50:15)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:50:15_Writing_files_to_a_read_write-enabled_persistent_partition.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:50:15_Writing_files_to_a_read_write-enabled_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:50:15_Writing_files_to_a_read_write-enabled_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:50:15_Writing_files_to_a_read_write-enabled_persistent_partition.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
19.688
Scenario Creating and using a persistent NetworkManager connection
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.688
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:83:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And the network is plugged 0.000
And Tor is ready 0.000
And I add a wired DHCP NetworkManager connection called "persistent-con-current" 0.000
And I shutdown Tails and wait for the computer to power off 0.000
Given I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
And I capture all network traffic 0.000
And the network is plugged 0.000
And Tor is ready 0.000
And I switch to the "persistent-con-current" NetworkManager connection 0.000
And the 1st network device has a spoofed MAC address configured 0.000
And no network device leaked the real MAC address 0.000
After features/support/hooks.rb:330 5.608 
SCENARIO FAILED: 'Creating and using a persistent NetworkManager connection' (at time 03:50:40)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:50:40_Creating_and_using_a_persistent_NetworkManager_connection.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:50:40_Creating_and_using_a_persistent_NetworkManager_connection.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:50:40_Creating_and_using_a_persistent_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:50:40_Creating_and_using_a_persistent_NetworkManager_connection.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
20.078
Scenario Persistent Greeter options
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 9.132
When I enable persistence 10.946
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/persistence.feature:104:in `When I enable persistence'
Then no persistent Greeter options were restored 0.000
When I set all Greeter options to non-default values 0.000
And I log in to a new session in German (de) after having activated the Persistent Storage 0.000
Then all Greeter options are set to non-default values 0.000
When I cold reboot the computer 0.000
And the computer reboots Tails 0.000
Given I enable persistence 0.000
Then persistent Greeter options were restored 0.000
When I log in to a new session after having activated the Persistent Storage 0.000
Then all Greeter options are set to non-default values 0.000
After features/support/hooks.rb:330 6.034 
SCENARIO FAILED: 'Persistent Greeter options' (at time 03:52:21)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:52:21_Persistent_Greeter_options.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:52:21_Persistent_Greeter_options.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:52:21_Persistent_Greeter_options.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:52:21_Persistent_Greeter_options.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
19.992
Scenario Changing the Persistent Storage passphrase
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.992
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:117:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
# Note that if anything fails after the passphrase was changed and
# before it's changed back below, subsequent scenarios might fail
# because the Persistent Storage doesn't have the expected passphrase.
When I change the passphrase of the Persistent Storage 0.000
And I shutdown Tails and wait for the computer to power off 0.000
Then I start Tails from USB drive "__internal" with network unplugged and I login with the changed persistence passphrase 0.000
And I change the passphrase of the Persistent Storage back to the original 0.000
After features/support/hooks.rb:330 5.710 
SCENARIO FAILED: 'Changing the Persistent Storage passphrase' (at time 03:52:47)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:52:47_Changing_the_Persistent_Storage_passphrase.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:52:47_Changing_the_Persistent_Storage_passphrase.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:52:47_Changing_the_Persistent_Storage_passphrase.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:52:47_Changing_the_Persistent_Storage_passphrase.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
19.336
Scenario Dotfiles persistence
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.336
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:136:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
When I write some dotfile expected to persist 0.000
And I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then the expected persistent dotfile is present in the filesystem 0.000
After features/support/hooks.rb:330 5.529 
SCENARIO FAILED: 'Dotfiles persistence' (at time 03:54:36)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:54:36_Dotfiles_persistence.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:54:36_Dotfiles_persistence.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:54:36_Dotfiles_persistence.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:54:36_Dotfiles_persistence.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
20.112
Scenario Feature activation fails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 9.172
And I create a symlink "/home/amnesia/Persistent" to "/etc" 0.097
When I try to enable persistence 10.841
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679:in `/^I try to enable persistence( with the changed passphrase)?$/'
features/persistence.feature:145:in `When I try to enable persistence'
Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated 0.000
When I log in to a new session after having activated the Persistent Storage 0.000
And all notifications have disappeared 0.000
Then the Persistent Storage settings tell me that the Persistent Folder feature couldn't be activated 0.000
And all tps features are enabled 0.000
And all tps features but the first one are active 0.000
After features/support/hooks.rb:330 6.475 
SCENARIO FAILED: 'Feature activation fails' (at time 03:55:01)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:55:01_Feature_activation_fails.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:55:01_Feature_activation_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:55:01_Feature_activation_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:55:01_Feature_activation_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
4:18.141
Scenario LUKS header is automatically upgraded when unlocking the Persistent Storage
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a LUKS 1 persistent partition and stopped at Tails Greeter's login screen 4:5.728
And I enable persistence 12.413
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/persistence.feature:155:in `And I enable persistence'
And I log in to a new session after having activated the Persistent Storage 0.000
Then a Tails persistence partition with LUKS version 2 and argon2id exists on USB drive "__internal" 0.000
And persistence is enabled 0.000
After features/support/hooks.rb:330 6.148 
SCENARIO FAILED: 'LUKS header is automatically upgraded when unlocking the Persistent Storage' (at time 03:59:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:59:26_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:59:26_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:59:26_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:59:26_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
23.111
Scenario LUKS backup header is restored if something goes wrong during 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 LUKS 1 persistent partition and stopped at Tails Greeter's login screen 9.461
And I enable persistence but something goes wrong during the LUKS header upgrade 13.650
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/usb.rb:714:in `/^I enable persistence but something goes wrong during the LUKS header upgrade$/'
features/persistence.feature:162:in `And I enable persistence but something goes wrong during the LUKS header upgrade'
Then the Tails persistence partition on USB drive "__internal" still has LUKS version 1 0.000
After features/support/hooks.rb:330 6.068 
SCENARIO FAILED: 'LUKS backup header is restored if something goes wrong during upgrade' (at time 03:59:55)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:59:55_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:59:55_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:59:55_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/03:59:55_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
33.895
Scenario Automatic filesystem repair
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 9.153
And I corrupt the Persistent Storage filesystem on USB drive "__internal" 10.515
When I enable persistence 14.225
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/persistence.feature:168:in `When I enable persistence'
Then the filesystem of the Persistent Storage was repaired 0.000
And persistence is successfully enabled 0.000
After features/support/hooks.rb:330 7.166 
SCENARIO FAILED: 'Automatic filesystem repair' (at time 04:00:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:00:35_Automatic_filesystem_repair.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:00:35_Automatic_filesystem_repair.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:00:35_Automatic_filesystem_repair.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:00:35_Automatic_filesystem_repair.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
29.567
Scenario Manual filesystem repair is successful
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 8.903
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 6.897
When I try to enable persistence 13.767
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679:in `/^I try to enable persistence( with the changed passphrase)?$/'
features/persistence.feature:175:in `When I try to enable persistence'
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 0.000
When I repair the filesystem of the Persistent Storage 0.000
Then the Welcome Screen tells me that the filesystem was repaired successfully 0.000
And the filesystem of the Persistent Storage was repaired 0.000
When I close the filesystem repair dialog 0.000
Then persistence is successfully enabled 0.000
After features/support/hooks.rb:330 5.865 
SCENARIO FAILED: 'Manual filesystem repair is successful' (at time 04:01:12)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:01:12_Manual_filesystem_repair_is_successful.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:01:12_Manual_filesystem_repair_is_successful.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:01:12_Manual_filesystem_repair_is_successful.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:01:12_Manual_filesystem_repair_is_successful.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product @doc
19.738
Scenario Manual filesystem repair fails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 8.758
And the Persistent Storage filesystem is corrupted beyond what e2fsck can repair 0.099
When I try to enable persistence 10.880
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679:in `/^I try to enable persistence( with the changed passphrase)?$/'
features/persistence.feature:187:in `When I try to enable persistence'
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 0.000
When I repair the filesystem of the Persistent Storage 0.000
Then the Welcome Screen tells me that it failed to repair the Persistent Storage 0.000
When I log in to a new session 0.000
And all notifications have disappeared 0.000
# Now both WhisperBack and Tor Browser has started at the same
# time, so we do not know which window is focused. The steps about
# Tor Browser care about that, but the ones about WhisperBack do
# not, so we first deal with WhisperBack and then kill it to
# ensure that Tor Browser is focused.
Then WhisperBack is prefilled for fsck with summary: "Failed to repair the file system of your Persistent Storage" 0.000
And the file "/var/lib/gdm3/post-greeter-whisperback.json" is empty 0.000
When I close the "whisperback" window 0.000
Then the Tor Browser starts 0.000
And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:330 5.483 
SCENARIO FAILED: 'Manual filesystem repair fails' (at time 04:01:38)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:01:38_Manual_filesystem_repair_fails.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:01:38_Manual_filesystem_repair_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:01:38_Manual_filesystem_repair_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:01:38_Manual_filesystem_repair_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product @doc
39.236
Scenario Filesystem and I/O errors
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 9.196
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 14.585
And Tails detects disk read failures on the boot device 1.848
When I try to enable persistence 13.606
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679:in `/^I try to enable persistence( with the changed passphrase)?$/'
features/persistence.feature:209:in `When I try to enable persistence'
Then the Welcome Screen tells me that my hardware is probably failing 0.000
When I log in to a new session 0.000
And all notifications have disappeared 0.000
Then the Tor Browser starts 0.000
And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:330 6.451 
SCENARIO FAILED: 'Filesystem and I/O errors' (at time 04:02:23)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:02:23_Filesystem_and_I_O_errors.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:02:23_Filesystem_and_I_O_errors.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:02:23_Filesystem_and_I_O_errors.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:02:23_Filesystem_and_I_O_errors.journal
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
3:28.453
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 12.463
And I create a persistent partition with the default settings 22.161
Then the "TorConfiguration" tps feature is not enabled 3.114
When the network is plugged 0.078
And the Tor Connection Assistant autostarts 11.056
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 17.845
And I wait until Tor is ready 1.480
Then tca.conf includes the configured bridges 0.014
And the "TorConfiguration" tps feature is enabled and active 1.194
When I cold reboot the computer 11.863
And the computer reboots Tails 1:56.298
And I enable persistence 10.881
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/persistent_tor_bridges.feature:19:in `And I enable persistence'
And I capture all network traffic 0.000
And I log in to a new session 0.000
Then tca.conf includes the configured bridges 0.000
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
Feature: Using persistent Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Using Persistent Tor bridges
Steps
When I choose to connect to Tor automatically 0.000
And I accept Tor Connection's offer to use my persistent bridges 0.000
And I click "Connect to Tor" 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:330 5.312 
SCENARIO FAILED: 'Using Persistent Tor bridges' (at time 04:05:58)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:05:58_Using_Persistent_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:05:58_Using_Persistent_Tor_bridges.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:05:58_Using_Persistent_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:05:58_Using_Persistent_Tor_bridges.journal
After features/support/hooks.rb:100 0.007
Feature: Using persistent Tor bridges and pluggable transports
3:45.209
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 9.726
And I create a persistent partition with the default settings 22.753
Then the "TorConfiguration" tps feature is not enabled 3.033
When the network is plugged 0.078
And the Tor Connection Assistant autostarts 8.668
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 18.748
And I wait until Tor is ready 29.041
Then tca.conf includes the configured bridges 0.013
And the "TorConfiguration" tps feature is enabled and active 1.231
When I cold reboot the computer 13.243
And the computer reboots Tails 1:48.063
And I enable persistence 10.606
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/persistent_tor_bridges.feature:19:in `And I enable persistence'
And I capture all network traffic 0.000
And I log in to a new session 0.000
Then tca.conf includes the configured bridges 0.000
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
Feature: Using persistent Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Disabling persistence of Tor bridges
Steps
When I choose to connect to Tor automatically 0.000
And I accept Tor Connection's offer to use my persistent bridges 0.000
And I disable saving bridges to Persistent Storage 0.000
And I configure a direct connection in the Tor Connection Assistant 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes no bridge 0.000
And the "TorConfiguration" tps feature is not enabled and not active 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:330 5.282 
SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 04:09:48)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:09:48_Disabling_persistence_of_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:09:48_Disabling_persistence_of_Tor_bridges.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:09:48_Disabling_persistence_of_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:09:48_Disabling_persistence_of_Tor_bridges.journal
After features/support/hooks.rb:100 0.007
Feature: Tails has a sane default configuration
Tags: @product
11.417
Scenario No unexpected error messages in the journal after booting from DVD
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails from DVD without network and logged in 11.335
Then there are no unexpected messages of priority "err" or higher in the journal 0.081
Unexpected 
Unexpected error messages in the journal: [
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:18 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "577",
    "_BOOT_ID": "47c0c520a1054767916bfd6c3879eaad",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "577",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749426192737997",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "be9d3c48df054d2fa1d752bd21d3f8b9",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=c18811c390f645f6810aa814609a975c;i=37c;b=47c0c520a1054767916bfd6c3879eaad;m=c8ffd3;t=6371806c76d20;x=4d80e6982a22df9d",
    "__MONOTONIC_TIMESTAMP": "13172691",
    "__REALTIME_TIMESTAMP": "1749426192739616",
    "__SEQNUM": "892",
    "__SEQNUM_ID": "c18811c390f645f6810aa814609a975c"
  },
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:22 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "577",
    "_BOOT_ID": "47c0c520a1054767916bfd6c3879eaad",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "577",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749426192738006",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "be9d3c48df054d2fa1d752bd21d3f8b9",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=c18811c390f645f6810aa814609a975c;i=37e;b=47c0c520a1054767916bfd6c3879eaad;m=c900fc;t=6371806c76e49;x=d1e07547c47ec63e",
    "__MONOTONIC_TIMESTAMP": "13172988",
    "__REALTIME_TIMESTAMP": "1749426192739913",
    "__SEQNUM": "894",
    "__SEQNUM_ID": "c18811c390f645f6810aa814609a975c"
  },
  {
    "MESSAGE": "The group `powerdev' does not exist.",
    "SYSLOG_IDENTIFIER": "adduser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "1941",
    "SYSLOG_TIMESTAMP": "Jun  8 23:43:20 ",
    "_BOOT_ID": "47c0c520a1054767916bfd6c3879eaad",
    "_CAP_EFFECTIVE": "1ffffffffff",
    "_CMDLINE": "adduser",
    "_COMM": "adduser",
    "_EXE": "/usr/bin/perl",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "1941",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749426200405716",
    "_SYSTEMD_CGROUP": "/system.slice/live-config.service",
    "_SYSTEMD_INVOCATION_ID": "e5bc89a207794763a126e5883309102a",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "live-config.service",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=c18811c390f645f6810aa814609a975c;i=404;b=47c0c520a1054767916bfd6c3879eaad;m=13df995;t=63718073c66e2;x=6b58e5c3bc0e2920",
    "__MONOTONIC_TIMESTAMP": "20838805",
    "__REALTIME_TIMESTAMP": "1749426200405730",
    "__SEQNUM": "1028",
    "__SEQNUM_ID": "c18811c390f645f6810aa814609a975c"
  },
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:18 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "577",
    "_BOOT_ID": "47c0c520a1054767916bfd6c3879eaad",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "577",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749426373716528",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "be9d3c48df054d2fa1d752bd21d3f8b9",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=c18811c390f645f6810aa814609a975c;i=8bf;b=47c0c520a1054767916bfd6c3879eaad;m=6201074;t=637181190ea54;x=2c1303d4ffcdc617",
    "__MONOTONIC_TIMESTAMP": "102764660",
    "__REALTIME_TIMESTAMP": "1749426373716564",
    "__SEQNUM": "2239",
    "__SEQNUM_ID": "c18811c390f645f6810aa814609a975c"
  },
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:22 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "577",
    "_BOOT_ID": "47c0c520a1054767916bfd6c3879eaad",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "577",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749426373716553",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "be9d3c48df054d2fa1d752bd21d3f8b9",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=c18811c390f645f6810aa814609a975c;i=8c1;b=47c0c520a1054767916bfd6c3879eaad;m=62011a8;t=637181190eb89;x=5969ea0a54647f51",
    "__MONOTONIC_TIMESTAMP": "102764968",
    "__REALTIME_TIMESTAMP": "1749426373716873",
    "__SEQNUM": "2241",
    "__SEQNUM_ID": "c18811c390f645f6810aa814609a975c"
  },
  {
    "MESSAGE": "The user `amnesia' is not a member of group `sudo'.",
    "SYSLOG_IDENTIFIER": "deluser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "7637",
    "SYSLOG_TIMESTAMP": "Jun  8 23:46:18 ",
    "_AUDIT_LOGINUID": "1000",
    "_AUDIT_SESSION": "4",
    "_BOOT_ID": "47c0c520a1054767916bfd6c3879eaad",
    "_CAP_EFFECTIVE": "1ffffffffff",
    "_CMDLINE": "/usr/bin/perl -T /usr/sbin/deluser amnesia sudo",
    "_COMM": "deluser",
    "_EXE": "/usr/bin/perl",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "7637",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749426378104100",
    "_SYSTEMD_CGROUP": "/user.slice/user-1000.slice/session-4.scope",
    "_SYSTEMD_INVOCATION_ID": "a1d49f1cf1274c489bf6d0ccc95babf3",
    "_SYSTEMD_OWNER_UID": "1000",
    "_SYSTEMD_SESSION": "4",
    "_SYSTEMD_SLICE": "user-1000.slice",
    "_SYSTEMD_UNIT": "session-4.scope",
    "_SYSTEMD_USER_SLICE": "-.slice",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=c18811c390f645f6810aa814609a975c;i=1219;b=47c0c520a1054767916bfd6c3879eaad;m=6630350;t=6371811d3dd30;x=dfa8f001984f3d93",
    "__MONOTONIC_TIMESTAMP": "107152208",
    "__REALTIME_TIMESTAMP": "1749426378104112",
    "__SEQNUM": "4633",
    "__SEQNUM_ID": "c18811c390f645f6810aa814609a975c"
  }
].
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/checks.rb:237:in `/^there are no unexpected messages of priority "err" or higher in the journal$/'
features/sane_defaults.feature:21:in `Then there are no unexpected messages of priority "err" or higher in the journal'
After features/support/hooks.rb:330 5.553 
SCENARIO FAILED: 'No unexpected error messages in the journal after booting from DVD' (at time 04:15:43)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:15:43_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:15:43_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:15:43_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:15:43_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.journal
After features/support/hooks.rb:100 0.000
Feature: Tails has a sane default configuration
Tags: @product
22.432
Scenario No unexpected error messages in the journal after booting from USB drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 22.432
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/sane_defaults.feature:24:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
Then there are no unexpected messages of priority "err" or higher in the journal 0.000
After features/support/hooks.rb:330 5.611 
SCENARIO FAILED: 'No unexpected error messages in the journal after booting from USB drive' (at time 04:16:11)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:16:11_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:16:11_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:16:11_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:16:11_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.journal
After features/support/hooks.rb:100 0.000
Feature: Shutdown buttons in the system menu
Tags: @product
26.354
Scenario I can shutdown Tails via the system menu
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.142
When I request a shutdown using the system menu 14.212
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/support/helpers/dogtail.rb:371:in `grabFocus'
./features/step_definitions/common_steps.rb:902:in `/^I request a (shutdown|reboot) using the system menu$/'
features/shutdown_applet.feature:6:in `When I request a shutdown using the system menu'
Then Tails eventually shuts down 0.000
After features/support/hooks.rb:330 5.757 
SCENARIO FAILED: 'I can shutdown Tails via the system menu' (at time 04:16:43)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:16:43_I_can_shutdown_Tails_via_the_system_menu.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:16:43_I_can_shutdown_Tails_via_the_system_menu.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:16:43_I_can_shutdown_Tails_via_the_system_menu.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:16:43_I_can_shutdown_Tails_via_the_system_menu.journal
After features/support/hooks.rb:100 0.000
Feature: Shutdown buttons in the system menu
Tags: @product @not_release_blocker
25.721
Scenario I can reboot Tails via the system menu
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD and logged in and the network is connected 11.768
When I request a reboot using the system menu 13.953
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/support/helpers/dogtail.rb:371:in `grabFocus'
./features/step_definitions/common_steps.rb:902:in `/^I request a (shutdown|reboot) using the system menu$/'
features/shutdown_applet.feature:12:in `When I request a reboot using the system menu'
Then Tails eventually restarts 0.000
After features/support/hooks.rb:330 5.940 
SCENARIO FAILED: 'I can reboot Tails via the system menu' (at time 04:17:15)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:17:15_I_can_reboot_Tails_via_the_system_menu.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:17:15_I_can_reboot_Tails_via_the_system_menu.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:17:15_I_can_reboot_Tails_via_the_system_menu.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:17:15_I_can_reboot_Tails_via_the_system_menu.journal
After features/support/hooks.rb:100 0.000
Feature: Logging in via SSH
Tags: @product @check_tor_leaks
8.780
Scenario Connecting to an SSH server on the Internet works and uses the default SocksPort
Steps
Given I monitor the network connections of SSH 0.092
And I have the SSH key pair for an SSH server 0.448
When I connect to an SSH server on the Internet 8.240
undefined 
undefined local variable or method `kwargs' for #<Screen:0x00007f66112c5000 @w=1024, @h=768, @_assertion_wrapped=false>

        press(*arg, **kwargs)
                      ^^^^^^
Did you mean?  args (NameError)
./features/support/helpers/screen.rb:376:in `block in type'
./features/support/helpers/screen.rb:357:in `each'
./features/support/helpers/screen.rb:357:in `type'
./features/step_definitions/ssh.rb:73:in `/^I (?:am prompted to )?verify the SSH fingerprint for the (?:Git|SSH) (?:repository|server)$/'
./features/step_definitions/ssh.rb:116: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/ssh.rb:113:in `/^I connect to an SSH server on the (Internet|LAN)$/'
features/ssh.feature:14:in `When I connect to an SSH server on the Internet'
Then I have sucessfully logged into the SSH server 0.000
And I see that SSH is properly stream isolated 0.000
After features/support/hooks.rb:521 0.037
After features/support/hooks.rb:330 5.017 
SCENARIO FAILED: 'Connecting to an SSH server on the Internet works and uses the default SocksPort' (at time 04:17:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:17:42_Connecting_to_an_SSH_server_on_the_Internet_works_and_uses_the_default_SocksPort.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:17:42_Connecting_to_an_SSH_server_on_the_Internet_works_and_uses_the_default_SocksPort.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:17:42_Connecting_to_an_SSH_server_on_the_Internet_works_and_uses_the_default_SocksPort.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:17:42_Connecting_to_an_SSH_server_on_the_Internet_works_and_uses_the_default_SocksPort.journal
After features/support/hooks.rb:100 0.000
Feature: Logging in via SSH
Tags: @product @check_tor_leaks
8.001
Scenario Connecting to an SSH server on the LAN
Steps
Given I have the SSH key pair for an SSH server 0.262
And an SSH server is running on the LAN 0.356
When I connect to an SSH server on the LAN 7.382
undefined 
undefined local variable or method `kwargs' for #<Screen:0x00007f661185ef48 @w=1024, @h=768, @_assertion_wrapped=false>

        press(*arg, **kwargs)
                      ^^^^^^
Did you mean?  args (NameError)
./features/support/helpers/screen.rb:376:in `block in type'
./features/support/helpers/screen.rb:357:in `each'
./features/support/helpers/screen.rb:357:in `type'
./features/step_definitions/ssh.rb:73:in `/^I (?:am prompted to )?verify the SSH fingerprint for the (?:Git|SSH) (?:repository|server)$/'
./features/step_definitions/ssh.rb:116: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/ssh.rb:113:in `/^I connect to an SSH server on the (Internet|LAN)$/'
features/ssh.feature:22:in `When I connect to an SSH server on the LAN'
Then I am prompted to verify the SSH fingerprint for the SSH server 0.000
After features/support/hooks.rb:521 0.038
After features/support/hooks.rb:330 4.879 
SCENARIO FAILED: 'Connecting to an SSH server on the LAN' (at time 04:18:06)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:18:06_Connecting_to_an_SSH_server_on_the_LAN.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:18:06_Connecting_to_an_SSH_server_on_the_LAN.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:18:06_Connecting_to_an_SSH_server_on_the_LAN.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:18:06_Connecting_to_an_SSH_server_on_the_LAN.journal
After features/support/hooks.rb:100 0.000
Feature: Logging in via SSH
Tags: @product @check_tor_leaks @not_release_blocker
14.063
Scenario Connecting to an SFTP server on the Internet using the GNOME "Connect to Server" feature
Steps
Given I have the SSH key pair for an SFTP server 0.273
When I connect to an SFTP server on the Internet 13.790
undefined 
undefined local variable or method `kwargs' for #<Screen:0x00007f66101bc3a8 @w=1024, @h=768, @_assertion_wrapped=false>

        press(*arg, **kwargs)
                      ^^^^^^
Did you mean?  args (NameError)
./features/support/helpers/screen.rb:376:in `block in type'
./features/support/helpers/screen.rb:357:in `each'
./features/support/helpers/screen.rb:357:in `type'
./features/step_definitions/ssh.rb:162:in `/^I verify the SSH fingerprint for the SFTP server$/'
./features/step_definitions/ssh.rb:151: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/ssh.rb:141:in `/^I connect to an SFTP server on the Internet$/'
features/ssh.feature:28:in `When I connect to an SFTP server on the Internet'
Then I successfully connect to the SFTP server 0.000
After features/support/hooks.rb:521 0.040
After features/support/hooks.rb:330 6.994 
SCENARIO FAILED: 'Connecting to an SFTP server on the Internet using the GNOME "Connect to Server" feature' (at time 04:18:37)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:18:37_Connecting_to_an_SFTP_server_on_the_Internet_using_the_GNOME__Connect_to_Server__feature.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:18:37_Connecting_to_an_SFTP_server_on_the_Internet_using_the_GNOME__Connect_to_Server__feature.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:18:37_Connecting_to_an_SFTP_server_on_the_Internet_using_the_GNOME__Connect_to_Server__feature.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:18:37_Connecting_to_an_SFTP_server_on_the_Internet_using_the_GNOME__Connect_to_Server__feature.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product @check_tor_leaks
1:25.788
Scenario The Downloads directory is usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Before features/support/hooks.rb:513 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 11.953
Then the live user's Downloads directory exists 0.076
And there is a GNOME bookmark for the Downloads directory 21.663
When I start the Tor Browser 29.731
And the Tor Browser loads the startup page 2.780
Then I can save the current page as "index.html" to the Downloads directory 19.583
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'org.gnome.Nautilus' application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/browser.rb:6:in `new'
./features/step_definitions/browser.rb:6:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:38:in `browser_save_page_as'
./features/step_definitions/browser.rb:543:in `/^I (can|cannot) save the current page as "([^"]+[.]html)" to the (.*) (directory|GNOME bookmark)$/'
features/torified_browsing.feature:24:in `Then I can save the current page as "index.html" to the Downloads directory'
And I can print the current page as "output.pdf" to the Downloads directory 0.000
After features/support/hooks.rb:521 0.035
After features/support/hooks.rb:330 8.344 
SCENARIO FAILED: 'The Downloads directory is usable in Tor Browser' (at time 04:32:01)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:32:01_The_Downloads_directory_is_usable_in_Tor_Browser.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:32:01_The_Downloads_directory_is_usable_in_Tor_Browser.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:32:01_The_Downloads_directory_is_usable_in_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:32:01_The_Downloads_directory_is_usable_in_Tor_Browser.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product @check_tor_leaks
1:20.657
Scenario Downloading files with the Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Before features/support/hooks.rb:513 0.005
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.215
When I start the Tor Browser 37.306
Then the Tor Browser loads the startup page 1.635
When I download some file in the Tor Browser to the Downloads directory 29.500
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'org.gnome.Nautilus' application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/browser.rb:6:in `new'
./features/step_definitions/browser.rb:6:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:310:in `/^I download some file in the Tor Browser to the (.*) directory$/'
features/torified_browsing.feature:32:in `When I download some file in the Tor Browser to the Downloads directory'
Then the file is saved to the Downloads directory 0.000
After features/support/hooks.rb:521 0.047
After features/support/hooks.rb:330 8.634 
SCENARIO FAILED: 'Downloading files with the Tor Browser' (at time 04:33:30)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:33:30_Downloading_files_with_the_Tor_Browser.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:33:30_Downloading_files_with_the_Tor_Browser.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:33:30_Downloading_files_with_the_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:33:30_Downloading_files_with_the_Tor_Browser.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
46.865
Scenario The Tor Browser uses TBB's shared libraries
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.181
When I start the Tor Browser 32.521
Then the Tor Browser uses all expected TBB shared libraries 2.162
The 
The loaded shared libraries for the firefox process are not the way we expect them.
Expected TBB libs that are absent: ["libfreeblpriv3.so", "libgkcodecs.so", "liblgpllibs.so", "libmozgtk.so", "libmozsandbox.so", "libmozsqlite3.so", "libmozwayland.so", "libnspr4.so", "libnss3.so", "libnssckbi.so", "libnssutil3.so", "libplc4.so", "libplds4.so", "libsmime3.so", "libsoftokn3.so", "libssl3.so", "libxul.so"]
Native libs that we don't want: [].
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/browser.rb:259:in `xul_app_shared_lib_check'
./features/step_definitions/browser.rb:273:in `/^the (.*) uses all expected TBB shared libraries$/'
features/torified_browsing.feature:76:in `Then the Tor Browser uses all expected TBB shared libraries'
After features/support/hooks.rb:330 6.381 
SCENARIO FAILED: 'The Tor Browser uses TBB's shared libraries' (at time 04:39:50)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:39:50_The_Tor_Browser_uses_TBB_s_shared_libraries.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:39:50_The_Tor_Browser_uses_TBB_s_shared_libraries.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:39:50_The_Tor_Browser_uses_TBB_s_shared_libraries.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:39:50_The_Tor_Browser_uses_TBB_s_shared_libraries.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
21.855
Scenario The Persistent directory is usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.855
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/torified_browsing.feature:106:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And the network is plugged 0.000
And I successfully configure Tor 0.000
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 5.802 
SCENARIO FAILED: 'The Persistent directory is usable in Tor Browser' (at time 04:44:02)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:44:02_The_Persistent_directory_is_usable_in_Tor_Browser.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:44:02_The_Persistent_directory_is_usable_in_Tor_Browser.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:44:02_The_Persistent_directory_is_usable_in_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:44:02_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
59.705
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Steps
Given I have started Tails from DVD without network and logged in 9.252
Then the live user's Documents directory exists 0.138
And there is a GNOME bookmark for the Documents directory 19.772
Then I start the Tor Browser in offline mode 30.543
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:479:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:466:in `/^I start the Tor Browser( in offline mode)?$/'
features/torified_browsing.feature:127:in `Then I start the Tor Browser in offline mode'
features/torified_browsing.feature:123:in `Then I start the Tor Browser in offline mode'
And I can save the current page as "index.html" to the Documents GNOME bookmark 0.000
After features/support/hooks.rb:330 10.617 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#1)' (at time 04:45:08)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:45:08_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:45:08_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:45:08_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:17.305
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD without network and logged in 8.532
Then the live user's Pictures directory exists 0.333
And there is a GNOME bookmark for the Pictures directory 18.373
Then I start the Tor Browser in offline mode 35.179
And I can save the current page as "index.html" to the Pictures GNOME bookmark 14.886
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'org.gnome.Nautilus' application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/browser.rb:6:in `new'
./features/step_definitions/browser.rb:6:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:38:in `browser_save_page_as'
./features/step_definitions/browser.rb:543:in `/^I (can|cannot) save the current page as "([^"]+[.]html)" to the (.*) (directory|GNOME bookmark)$/'
features/torified_browsing.feature:130:in `And I can save the current page as "index.html" to the Pictures GNOME bookmark'
features/torified_browsing.feature:124:in `And I can save the current page as "index.html" to the <dir> GNOME bookmark'
After features/support/hooks.rb:330 8.025 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#4)' (at time 04:49:30)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:49:30_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___4_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:49:30_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___4_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:49:30_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___4_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:49:30_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
20.541
Scenario Persistent browser bookmarks
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.541
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/torified_browsing.feature:134:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And all tps features are active 0.000
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 have safe access rights 0.000
When I start the Tor Browser in offline mode 0.000
And I add a bookmark to eff.org in the Tor Browser 0.000
And I cold reboot the computer 0.000
And the computer reboots Tails 0.000
And I enable persistence 0.000
And I log in to a new session 0.000
And all notifications have disappeared 0.000
And I start the Tor Browser in offline mode 0.000
Then the Tor Browser has a bookmark to eff.org 0.000
After features/support/hooks.rb:330 6.063 
SCENARIO FAILED: 'Persistent browser bookmarks' (at time 04:51:28)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:51:28_Persistent_browser_bookmarks.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:51:28_Persistent_browser_bookmarks.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:51:28_Persistent_browser_bookmarks.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:51:28_Persistent_browser_bookmarks.journal
After features/support/hooks.rb:100 0.000
Feature: Cloning a Git repository
Tags: @product @check_tor_leaks
8.004
Scenario Cloning git repository over SSH
Steps
Given I have the SSH key pair for a Git repository 0.287
When I clone the Git repository "ssh://gitolite3@lizard.tails.boum.org:3004/myprivatekeyispublic/testing.git" in GNOME Terminal 7.717
undefined 
undefined local variable or method `kwargs' for #<Screen:0x00007f6615383a38 @w=1024, @h=768, @_assertion_wrapped=false>

        press(*arg, **kwargs)
                      ^^^^^^
Did you mean?  args (NameError)
./features/support/helpers/screen.rb:376:in `block in type'
./features/support/helpers/screen.rb:357:in `each'
./features/support/helpers/screen.rb:357:in `type'
./features/step_definitions/ssh.rb:73:in `/^I (?:am prompted to )?verify the SSH fingerprint for the (?:Git|SSH) (?:repository|server)$/'
./features/step_definitions/git.rb:16: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/git.rb:13:in `/^I clone the Git repository "(\S+)" in GNOME Terminal$/'
features/torified_git.feature:16:in `When I clone the Git repository "ssh://gitolite3@lizard.tails.boum.org:3004/myprivatekeyispublic/testing.git" in GNOME Terminal'
Then the Git repository "testing" has been cloned successfully 0.000
After features/support/hooks.rb:521 0.034
After features/support/hooks.rb:330 6.142 
SCENARIO FAILED: 'Cloning git repository over SSH' (at time 04:52:15)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:52:15_Cloning_git_repository_over_SSH.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:52:15_Cloning_git_repository_over_SSH.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:52:15_Cloning_git_repository_over_SSH.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:52:15_Cloning_git_repository_over_SSH.journal
After features/support/hooks.rb:100 0.000
Feature: Using Totem
Tags: @product
20.597
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 20.597
Ponytail 
Ponytail failed while pressing key combo: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
STDOUT:

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

 (RuntimeError)
./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/usb.rb:679: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/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/totem.feature:55:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I plug and mount a USB drive containing sample videos 0.000
And I copy the sample videos to "/home/amnesia/Persistent" as user "amnesia" 0.000
When I open "/home/amnesia/Persistent/video.mp4" with Totem 0.000
Then I see "SampleLocalMp4VideoFrame.png" after at most 40 seconds 0.000
Given I close Totem 0.000
And I start monitoring the AppArmor log of "/usr/bin/totem" 0.000
And I copy the sample videos to "/home/amnesia/.gnupg" as user "amnesia" 0.000
When I try to open "/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 "/home/amnesia/.gnupg/video.mp4" 0.000
After features/support/hooks.rb:330 5.796 
SCENARIO FAILED: 'Watching MP4 videos stored on the persistent volume should work as expected given our AppArmor confinement' (at time 04:54:44)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:54:44_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:54:44_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:54:44_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/04:54:44_Watching_MP4_videos_stored_on_the_persistent_volume_should_work_as_expected_given_our_AppArmor_confinement.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Unsafe Browser
Tags: @product @not_release_blocker
54.488
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 11.456
When I successfully start the Unsafe Browser 22.311
# 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.010 
Slept for 10 seconds
And I try to start the Unsafe Browser 0.089
Then I see a warning about another instance already running 10.619
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'zenity' application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/unsafe_browser.rb:76:in `new'
./features/step_definitions/unsafe_browser.rb:76:in `/^I see a warning about another instance already running$/'
features/unsafe_browser.feature:59:in `Then I see a warning about another instance already running'
After features/support/hooks.rb:330 10.992 
SCENARIO FAILED: 'Starting a second instance of the Unsafe Browser results in an error message being shown' (at time 05:00:56)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:00:56_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:00:56_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:00:56_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
22.585
Scenario Use Unlock VeraCrypt Volumes to unlock a USB drive that has a basic VeraCrypt volume
Steps
When I plug a USB drive containing a basic VeraCrypt volume 8.218
And I cancel the GNOME authentication prompt 3.472
And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 6.364
And I open this VeraCrypt volume in GNOME Files 3.957
Then I see the expected contents in this VeraCrypt volume 0.485
When I lock the currently opened VeraCrypt volume 0.087
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/veracrypt.rb:330:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:18:in `When I lock the currently opened VeraCrypt volume'
Then the VeraCrypt volume has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.630 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a USB drive that has a basic VeraCrypt volume' (at time 05:05:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:05:42_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:05:42_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:05:42_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_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:05:42_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
26.393
Scenario Use Unlock VeraCrypt Volumes to unlock a USB drive that has a hidden VeraCrypt volume
Steps
When I plug a USB drive containing a hidden VeraCrypt volume 11.435
And I cancel the GNOME authentication prompt 2.827
And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 7.210
And I open this VeraCrypt volume in GNOME Files 4.309
Then I see the expected contents in this VeraCrypt volume 0.529
When I lock the currently opened VeraCrypt volume 0.079
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/veracrypt.rb:330:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:27:in `When I lock the currently opened VeraCrypt volume'
Then the VeraCrypt volume has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.593 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a USB drive that has a hidden VeraCrypt volume' (at time 05:06:23)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:06:23_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:06:23_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:06:23_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:06:23_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
30.308
Scenario Use Unlock VeraCrypt Volumes to unlock a basic VeraCrypt file container with a PIM
Steps
When I plug and mount a USB drive containing a basic VeraCrypt file container with a PIM 16.939
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 9.126
And I open this VeraCrypt volume in GNOME Files 3.695
Then I see the expected contents in this VeraCrypt volume 0.468
When I lock the currently opened VeraCrypt file container 0.078
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/veracrypt.rb:330:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:35:in `When I lock the currently opened VeraCrypt file container'
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.462 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a basic VeraCrypt file container with a PIM' (at time 05:07:07)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:07:07_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:07:07_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:07:07_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:07:07_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
42.832
Scenario Use Unlock VeraCrypt Volumes to unlock a hidden VeraCrypt file container
Steps
When I plug and mount a USB drive containing a hidden VeraCrypt file container 27.125
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 10.763
And I open this VeraCrypt volume in GNOME Files 4.353
Then I see the expected contents in this VeraCrypt volume 0.507
When I lock the currently opened VeraCrypt file container 0.081
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/veracrypt.rb:330:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:43:in `When I lock the currently opened VeraCrypt file container'
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.728 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a hidden VeraCrypt file container' (at time 05:08:05)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:08:05_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:08:05_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:08:05_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:08:05_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:100 0.015
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
50.366
Scenario Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile
Steps
When I plug a USB drive containing a basic VeraCrypt volume with a keyfile 8.095
And I cancel the GNOME authentication prompt 3.218
And I unlock and mount this VeraCrypt volume with GNOME Disks 39.052
Failed 
Failed to mount the unlocked volume
Last ignored exception was: RuntimeError: Ponytail failed while pressing key combo: ValueError: Cannot find key 'down'
STDOUT:

STDERR:


./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/veracrypt.rb:284: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/veracrypt.rb:277: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/veracrypt.rb:277:in `/^I unlock and mount this VeraCrypt (volume|file container) with GNOME Disks$/'
features/veracrypt.feature:51:in `And I unlock and mount this VeraCrypt volume with GNOME Disks'
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 5.936 
SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile' (at time 05:09:10)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:09:10_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:09:10_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:09:10_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:09:10_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
49.484
Scenario Use GNOME Disks to unlock a USB drive that has a hidden VeraCrypt volume
Steps
When I plug a USB drive containing a hidden VeraCrypt volume 11.372
And I cancel the GNOME authentication prompt 2.827
And I unlock and mount this VeraCrypt volume with GNOME Disks 35.284
Failed 
Failed to mount the unlocked volume
Last ignored exception was: RuntimeError: Ponytail failed while pressing key combo: ValueError: Cannot find key 'down'
STDOUT:

STDERR:


./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/veracrypt.rb:284: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/veracrypt.rb:277: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/veracrypt.rb:277:in `/^I unlock and mount this VeraCrypt (volume|file container) with GNOME Disks$/'
features/veracrypt.feature:60:in `And I unlock and mount this VeraCrypt volume with GNOME Disks'
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.112 
SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a hidden VeraCrypt volume' (at time 05:10:14)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:10:14_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:10:14_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:10:14_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:10:14_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
1:14.282
Scenario Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile
Steps
When I plug and mount a USB drive containing a basic VeraCrypt file container with a keyfile 23.418
And I unlock and mount this VeraCrypt file container with GNOME Disks 50.863
Failed 
Failed to mount the unlocked volume
Last ignored exception was: RuntimeError: Ponytail failed while pressing key combo: ValueError: Cannot find key 'down'
STDOUT:

STDERR:


./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/veracrypt.rb:284: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/veracrypt.rb:277: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/veracrypt.rb:277:in `/^I unlock and mount this VeraCrypt (volume|file container) with GNOME Disks$/'
features/veracrypt.feature:68:in `And I unlock and mount this VeraCrypt file container with GNOME Disks'
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 file container 0.000
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 6.631 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile' (at time 05:11:44)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:11:44_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:11:44_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:11:44_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:11:44_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.journal
After features/support/hooks.rb:100 0.018
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
1:14.558
Scenario Use GNOME Disks to unlock a hidden VeraCrypt file container
Steps
When I plug and mount a USB drive containing a hidden VeraCrypt file container 26.581
And I unlock and mount this VeraCrypt file container with GNOME Disks 47.977
Failed 
Failed to mount the unlocked volume
Last ignored exception was: RuntimeError: Ponytail failed while pressing key combo: ValueError: Cannot find key 'down'
STDOUT:

STDERR:


./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/veracrypt.rb:284: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/veracrypt.rb:277: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/veracrypt.rb:277:in `/^I unlock and mount this VeraCrypt (volume|file container) with GNOME Disks$/'
features/veracrypt.feature:76:in `And I unlock and mount this VeraCrypt file container with GNOME Disks'
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 file container 0.000
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.976 
SCENARIO FAILED: 'Use GNOME Disks to unlock a hidden VeraCrypt file container' (at time 05:13:14)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:13:14_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:13:14_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:13:14_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:13:14_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:100 0.015
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
1:3.692
Scenario Use GNOME Disks to unlock a basic VeraCrypt file container with a PIM
Steps
When I plug and mount a USB drive containing a basic VeraCrypt file container with a PIM 16.938
And I unlock and mount this VeraCrypt file container with GNOME Disks 46.753
Failed 
Failed to mount the unlocked volume
Last ignored exception was: RuntimeError: Ponytail failed while pressing key combo: ValueError: Cannot find key 'down'
STDOUT:

STDERR:


./features/support/helpers/screen.rb:344:in `ponytail_press'
./features/support/helpers/screen.rb:352:in `press'
./features/step_definitions/veracrypt.rb:284: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/veracrypt.rb:277: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/veracrypt.rb:277:in `/^I unlock and mount this VeraCrypt (volume|file container) with GNOME Disks$/'
features/veracrypt.feature:84:in `And I unlock and mount this VeraCrypt file container with GNOME Disks'
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 file container 0.000
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 8.608 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a PIM' (at time 05:14:34)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:14:34_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:14:34_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21002-ponytail-keyboard-input/7/artifact/build-artifacts/05:14:34_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.journal
After features/support/hooks.rb:100 0.000