Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 66 06 May 2024, 06:53

Failures Overview

The following summary displays scenarios that failed.

Feature: Additional software
Tags: @product @check_tor_leaks @slow
4:26.341
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:259 0.010
Before features/support/hooks.rb:456 0.008
Steps
Given a computer 0.232
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 3:44.349
When I uninstall "popularity-contest" using apt 21.866
And I accept removing "popularity-contest" from Additional Software 0.571
Then "popularity-contest" is not in the list of Additional Software 0.715
When I start Synaptic 18.605
The 
The Dogtail init script raised: Python process exited unexpectedly with -5
STDOUT:

STDERR:

(-c:13131): dbind-ERROR **: 03:33:12.629: AT-SPI: Couldn't connect to accessibility bus. Is at-spi-bus-launcher running?

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:85:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/apt.rb:159:in `new'
./features/step_definitions/apt.rb:159:in `/^I start Synaptic$/'
features/additional_software_packages.feature:59:in `When I start Synaptic'
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:464 0.046
After features/support/hooks.rb:305 5.850 
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:19:29)
Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/66/artifact/build-artifacts/01:19:29_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.file_content_run_live-additional-software_log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/66/artifact/build-artifacts/01:19:29_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_20268-more-early-patch-functionality/66/artifact/build-artifacts/01:19:29_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_20268-more-early-patch-functionality/66/artifact/build-artifacts/01:19:29_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_20268-more-early-patch-functionality/66/artifact/build-artifacts/01:19:29_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_20268-more-early-patch-functionality/66/artifact/build-artifacts/01:19:29_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_20268-more-early-patch-functionality/66/artifact/build-artifacts/01:19:29_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/66/artifact/build-artifacts/01:19:29_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/66/artifact/build-artifacts/01:19:29_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:89 0.010
Feature: Tails-related cryptographic keys are up-to-date
Tags: @product
21.124
Scenario The included APT repository keys are up-to-date
Before features/support/hooks.rb:259 0.007
Steps
Given I have started Tails from DVD without network and logged in 8.024
Then the keys trusted by APT are valid for the next 3 months 13.099
The 
The following APT key(s) will not be valid in 3 months: A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89, 2265EB4CB2BF88D900AE8D1B74A941BA219EC810.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/checks.rb:29: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:305 4.402 
SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 02:15:56)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/66/artifact/build-artifacts/02:15:56_The_included_APT_repository_keys_are_up-to-date.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/66/artifact/build-artifacts/02:15:56_The_included_APT_repository_keys_are_up-to-date.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/66/artifact/build-artifacts/02:15:56_The_included_APT_repository_keys_are_up-to-date.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/66/artifact/build-artifacts/02:15:56_The_included_APT_repository_keys_are_up-to-date.journal
After features/support/hooks.rb:89 0.000
Feature: Tails persistence
Tags: @product
3:8.776
Scenario Changing the Persistent Storage passphrase
Before features/support/hooks.rb:259 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.967
# 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 36.106
And I shutdown Tails and wait for the computer to power off 12.895
Then I start Tails from USB drive "__internal" with network unplugged and I login with the changed persistence passphrase 2:9.806
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: "gnome-shell" application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:711:in `new'
./features/step_definitions/common_steps.rb:711:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:295: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:123:in `Then I start Tails from USB drive "__internal" with network unplugged and I login with the changed persistence passphrase'
And I change the passphrase of the Persistent Storage back to the original 0.000
After features/support/hooks.rb:305 4.252 
SCENARIO FAILED: 'Changing the Persistent Storage passphrase' (at time 03:20:08)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/66/artifact/build-artifacts/03:20:08_Changing_the_Persistent_Storage_passphrase.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/66/artifact/build-artifacts/03:20:08_Changing_the_Persistent_Storage_passphrase.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/66/artifact/build-artifacts/03:20:08_Changing_the_Persistent_Storage_passphrase.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/66/artifact/build-artifacts/03:20:08_Changing_the_Persistent_Storage_passphrase.journal
After features/support/hooks.rb:89 0.010
Feature: Tails persistence
Tags: @product
1:40.088
Scenario Feature activation fails
Before features/support/hooks.rb:259 0.004
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.157
And I create a symlink "/home/amnesia/Persistent" to "/etc" 0.079
When I try to enable persistence 0.317
Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated 34.868
When I log in to a new session after having activated the Persistent Storage 44.473
And all notifications have disappeared 11.192
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: "gnome-shell" application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:711:in `new'
./features/step_definitions/common_steps.rb:711:in `/^all notifications have disappeared$/'
features/persistence.feature:148:in `And all notifications have disappeared'
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:305 4.885 
SCENARIO FAILED: 'Feature activation fails' (at time 03:25:42)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/66/artifact/build-artifacts/03:25:42_Feature_activation_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/66/artifact/build-artifacts/03:25:42_Feature_activation_fails.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/66/artifact/build-artifacts/03:25:42_Feature_activation_fails.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/66/artifact/build-artifacts/03:25:42_Feature_activation_fails.journal
After features/support/hooks.rb:89 0.000
Feature: Thunderbird email client
Tags: @product @check_tor_leaks
6:11.296
Scenario I can send emails, and receive emails over IMAP
Steps
When I enter my email credentials into the autoconfiguration wizard 10.434
Then the autoconfiguration wizard's choice for the incoming server is secure IMAP 0.311
And the autoconfiguration wizard's choice for the outgoing server is secure SMTP 0.390
When I accept the autoconfiguration wizard's configuration 6:0.159
The 
The Dogtail init script raised: SearchError: descendent of [frame | Account Setup - Mozilla Thunderbird]: "Get Messages" button
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:335:in `initialize'
./features/support/helpers/dogtail.rb:264:in `new'
./features/support/helpers/dogtail.rb:264:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:268:in `button'
./features/step_definitions/thunderbird.rb:128:in `/^I fetch my email$/'
./features/step_definitions/thunderbird.rb:160:in `/^I accept the (?:autoconfiguration wizard's|manual) configuration$/'
features/thunderbird.feature:22:in `When I accept the autoconfiguration wizard's configuration'
And I send an email to myself 0.000
And I fetch my email 0.000
Then I can find the email I sent to myself in my inbox 0.000
After features/support/hooks.rb:464 0.046
After features/support/hooks.rb:305 4.465 
SCENARIO FAILED: 'I can send emails, and receive emails over IMAP' (at time 03:53:19)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/66/artifact/build-artifacts/03:53:19_I_can_send_emails,_and_receive_emails_over_IMAP.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/66/artifact/build-artifacts/03:53:19_I_can_send_emails,_and_receive_emails_over_IMAP.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/66/artifact/build-artifacts/03:53:19_I_can_send_emails,_and_receive_emails_over_IMAP.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/66/artifact/build-artifacts/03:53:19_I_can_send_emails,_and_receive_emails_over_IMAP.journal
After features/support/hooks.rb:89 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
33.741
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 7.434
And I cancel the GNOME authentication prompt 2.545
And I unlock and mount this VeraCrypt volume with GNOME Disks 23.761
The 
The Dogtail init script raised: SearchError: descendent of [application | gnome-disks]: child with name="Select a Keyfile" roleName='file chooser'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:335:in `initialize'
./features/support/helpers/dogtail.rb:264:in `new'
./features/support/helpers/dogtail.rb:264:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:272:in `child'
./features/step_definitions/veracrypt.rb:280: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:305 6.510 
SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile' (at time 04:34:57)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/66/artifact/build-artifacts/04:34:57_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_20268-more-early-patch-functionality/66/artifact/build-artifacts/04:34:57_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/66/artifact/build-artifacts/04:34:57_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/66/artifact/build-artifacts/04:34:57_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.journal
After features/support/hooks.rb:89 0.000