Project Number Date
test_Tails_ISO_17367-per-setting-dconf-persistence 6 06 Aug 2026, 22:57

Failures Overview

The following summary displays scenarios that failed.

Feature: Tails persistence
Tags: @product
32.483
Scenario Dconf persistence
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.809
When I change a persisted setting for every dconf feature 24.674
tails-dconf-monitor 
tails-dconf-monitor did not persist the change to 'KeyboardShortcuts (window manager)' (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/usb.rb:1286:in `change_persisted_dconf_setting'
./features/step_definitions/usb.rb:1310:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:1309:in `each_key'
./features/step_definitions/usb.rb:1309:in `/^I change a persisted setting for every dconf feature$/'
features/persistence.feature:151:in `When I change a persisted setting for every dconf feature'
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 persisted setting for every dconf feature is still set 0.000
After features/support/hooks.rb:339 4.707 
SCENARIO FAILED: 'Dconf persistence' (at time 02:33:47)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/02:33:47_Dconf_persistence.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/02:33:47_Dconf_persistence.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/02:33:47_Dconf_persistence.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/02:33:47_Dconf_persistence.journal
After features/support/hooks.rb:108 0.000
Feature: Thunderbird email client
Tags: @product @check_tor_leaks
2:7.970
Scenario I can send emails, and receive emails over IMAP
Steps
When I enter my email credentials into the autoconfiguration wizard 2:7.970
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendant of [frame | Account Setup - Mozilla Thunderbird]: 'Done' button
STDOUT:

STDERR:


./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:272:in `button'
./features/step_definitions/thunderbird.rb:106:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
<internal:kernel>:187: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/thunderbird.rb:106: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/thunderbird.rb:106:in `/^I enter my email credentials into the autoconfiguration wizard$/'
features/thunderbird.feature:21:in `When I enter my email credentials into the autoconfiguration wizard'
Then the autoconfiguration wizard's choice for the incoming server is secure IMAP 0.000
And the autoconfiguration wizard's choice for the outgoing server is secure SMTP 0.000
When I accept the autoconfiguration wizard's configuration 0.000
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
And the system only established connections with my email server 0.000
After features/support/hooks.rb:535 0.047
After features/support/hooks.rb:339 10.778 
SCENARIO FAILED: 'I can send emails, and receive emails over IMAP' (at time 02:55:29)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/02:55:29_I_can_send_emails,_and_receive_emails_over_IMAP.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/02:55:29_I_can_send_emails,_and_receive_emails_over_IMAP.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/02:55:29_I_can_send_emails,_and_receive_emails_over_IMAP.journal
After features/support/hooks.rb:108 0.009
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
7.234
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 7.234
Command 
Command exited with pid 95678 exit 22 (StandardError)
./features/support/env.rb:18:in `fatal_system'
./features/step_definitions/veracrypt.rb:51:in `prepare_veracrypt_volume'
./features/step_definitions/veracrypt.rb:125:in `/^I plug a USB drive containing a (.+) VeraCrypt volume( with a keyfile)?$/'
features/veracrypt.feature:13:in `When I plug a USB drive containing a basic VeraCrypt volume'
And I cancel the GNOME authentication prompt 0.000
And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 0.000
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt volume 0.000
Then the VeraCrypt volume has been unmounted and locked 0.000
After features/support/hooks.rb:339 5.319 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a USB drive that has a basic VeraCrypt volume' (at time 03:21:14)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/03:21:14_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_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/03:21:14_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_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/03:21:14_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_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/03:21:14_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.journal
After features/support/hooks.rb:108 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
15.029
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 15.029
tcplay 
tcplay --map=veracrypt --device='/dev/loop1' exited with 255 (RuntimeError)
./features/step_definitions/veracrypt.rb:108:in `block in map_veracrypt_volume'
./features/step_definitions/veracrypt.rb:91:in `spawn'
./features/step_definitions/veracrypt.rb:91:in `map_veracrypt_volume'
./features/step_definitions/veracrypt.rb:49:in `prepare_veracrypt_volume'
./features/step_definitions/veracrypt.rb:125:in `/^I plug a USB drive containing a (.+) VeraCrypt volume( with a keyfile)?$/'
features/veracrypt.feature:22:in `When I plug a USB drive containing a hidden VeraCrypt volume'
And I cancel the GNOME authentication prompt 0.000
And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 0.000
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt volume 0.000
Then the VeraCrypt volume has been unmounted and locked 0.000
After features/support/hooks.rb:339 5.228 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a USB drive that has a hidden VeraCrypt volume' (at time 03:21:41)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/03:21:41_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_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/03:21:41_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_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/03:21:41_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_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/03:21:41_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.journal
After features/support/hooks.rb:108 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
14.486
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 14.486
tcplay 
tcplay --map=veracrypt --device='/dev/loop2' exited with 255 (RuntimeError)
./features/step_definitions/veracrypt.rb:108:in `block in map_veracrypt_volume'
./features/step_definitions/veracrypt.rb:91:in `spawn'
./features/step_definitions/veracrypt.rb:91:in `map_veracrypt_volume'
./features/step_definitions/veracrypt.rb:49:in `prepare_veracrypt_volume'
./features/step_definitions/veracrypt.rb:145:in `/^I plug and mount a USB drive containing a (.+) VeraCrypt file container( with a keyfile| with a PIM)?$/'
features/veracrypt.feature:39:in `When I plug and mount a USB drive containing a hidden VeraCrypt file container'
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 0.000
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt file container 0.000
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:339 5.260 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a hidden VeraCrypt file container' (at time 03:22:30)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/03:22:30_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_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/03:22:30_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/03:22:30_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/03:22:30_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:108 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
14.265
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 14.265
tcplay 
tcplay --map=veracrypt --device='/dev/loop3' --keyfile='/tmp/TailsToaster/veracrypt-keyfile20260806-9414-ntamiy' exited with 255 (RuntimeError)
./features/step_definitions/veracrypt.rb:108:in `block in map_veracrypt_volume'
./features/step_definitions/veracrypt.rb:91:in `spawn'
./features/step_definitions/veracrypt.rb:91:in `map_veracrypt_volume'
./features/step_definitions/veracrypt.rb:49:in `prepare_veracrypt_volume'
./features/step_definitions/veracrypt.rb:125:in `/^I plug a USB drive containing a (.+) VeraCrypt volume( with a keyfile)?$/'
features/veracrypt.feature:49:in `When I plug a USB drive containing a basic VeraCrypt volume with a keyfile'
And I cancel the GNOME authentication prompt 0.000
And I unlock and mount this VeraCrypt volume with GNOME Disks 0.000
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt volume 0.000
Then the VeraCrypt volume has been unmounted and locked 0.000
After features/support/hooks.rb:339 5.114 
SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile' (at time 03:23:08)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/03:23:08_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_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/03:23:08_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_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/03:23:08_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_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/03:23:08_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.journal
After features/support/hooks.rb:108 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
14.775
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 14.775
tcplay 
tcplay --map=veracrypt --device='/dev/loop4' exited with 255 (RuntimeError)
./features/step_definitions/veracrypt.rb:108:in `block in map_veracrypt_volume'
./features/step_definitions/veracrypt.rb:91:in `spawn'
./features/step_definitions/veracrypt.rb:91:in `map_veracrypt_volume'
./features/step_definitions/veracrypt.rb:49:in `prepare_veracrypt_volume'
./features/step_definitions/veracrypt.rb:125:in `/^I plug a USB drive containing a (.+) VeraCrypt volume( with a keyfile)?$/'
features/veracrypt.feature:58:in `When I plug a USB drive containing a hidden VeraCrypt volume'
And I cancel the GNOME authentication prompt 0.000
And I unlock and mount this VeraCrypt volume with GNOME Disks 0.000
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt volume 0.000
Then the VeraCrypt volume has been unmounted and locked 0.000
After features/support/hooks.rb:339 4.920 
SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a hidden VeraCrypt volume' (at time 03:23:34)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/03:23:34_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_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/03:23:34_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_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/03:23:34_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_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/03:23:34_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.journal
After features/support/hooks.rb:108 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
14.243
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 14.243
tcplay 
tcplay --map=veracrypt --device='/dev/loop5' --keyfile='/tmp/TailsToaster/veracrypt-keyfile20260806-9414-jkrh1b' exited with 255 (RuntimeError)
./features/step_definitions/veracrypt.rb:108:in `block in map_veracrypt_volume'
./features/step_definitions/veracrypt.rb:91:in `spawn'
./features/step_definitions/veracrypt.rb:91:in `map_veracrypt_volume'
./features/step_definitions/veracrypt.rb:49:in `prepare_veracrypt_volume'
./features/step_definitions/veracrypt.rb:145:in `/^I plug and mount a USB drive containing a (.+) VeraCrypt file container( with a keyfile| with a PIM)?$/'
features/veracrypt.feature:67:in `When I plug and mount a USB drive containing a basic VeraCrypt file container with a keyfile'
And I unlock and mount this VeraCrypt file container with GNOME Disks 0.000
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt file container 0.000
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:339 5.337 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile' (at time 03:24:00)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/03:24:00_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_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/03:24:00_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/03:24:00_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_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/03:24:00_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.journal
After features/support/hooks.rb:108 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
14.656
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 14.656
tcplay 
tcplay --map=veracrypt --device='/dev/loop6' exited with 255 (RuntimeError)
./features/step_definitions/veracrypt.rb:108:in `block in map_veracrypt_volume'
./features/step_definitions/veracrypt.rb:91:in `spawn'
./features/step_definitions/veracrypt.rb:91:in `map_veracrypt_volume'
./features/step_definitions/veracrypt.rb:49:in `prepare_veracrypt_volume'
./features/step_definitions/veracrypt.rb:145:in `/^I plug and mount a USB drive containing a (.+) VeraCrypt file container( with a keyfile| with a PIM)?$/'
features/veracrypt.feature:75:in `When I plug and mount a USB drive containing a hidden VeraCrypt file container'
And I unlock and mount this VeraCrypt file container with GNOME Disks 0.000
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt file container 0.000
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:339 5.210 
SCENARIO FAILED: 'Use GNOME Disks to unlock a hidden VeraCrypt file container' (at time 03:24:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/03:24:26_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_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/03:24:26_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/03:24:26_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/6/artifact/build-artifacts/03:24:26_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:108 0.000