Project Number Date
test_Tails_ISO_feature-trixie 11 02 Jun 2025, 06:44

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Using VeraCrypt encrypted volumes 49 9 9 0 0 67 0 9 9 6:52.478 Failed
Tags: @product @not_release_blocker
Feature Using VeraCrypt encrypted volumes
In order to collaborate with non-Tails users As a Tails user I want to unlock VeraCrypt encrypted volumes
9.525
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails from DVD without network and logged in 9.525
Tags: @product @not_release_blocker
24.458
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.570
And I cancel the GNOME authentication prompt 4.578
And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 7.208
And I open this VeraCrypt volume in GNOME Files 4.507
Then I see the expected contents in this VeraCrypt volume 0.501
When I lock the currently opened VeraCrypt volume 0.092
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:332: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.307 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a USB drive that has a basic VeraCrypt volume' (at time 07:23:08)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/11/artifact/build-artifacts/07:23:08_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/11/artifact/build-artifacts/07:23:08_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/11/artifact/build-artifacts/07:23:08_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/11/artifact/build-artifacts/07:23:08_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.journal
After features/support/hooks.rb:100 0.000
10.261
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails from DVD without network and logged in 10.261
Tags: @product @not_release_blocker
24.884
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 10.280
And I cancel the GNOME authentication prompt 2.557
And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 6.000
And I open this VeraCrypt volume in GNOME Files 5.511
Then I see the expected contents in this VeraCrypt volume 0.464
When I lock the currently opened VeraCrypt volume 0.069
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:332: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.404 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a USB drive that has a hidden VeraCrypt volume' (at time 07:23:48)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/11/artifact/build-artifacts/07:23:48_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_feature-trixie/11/artifact/build-artifacts/07:23:48_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_feature-trixie/11/artifact/build-artifacts/07:23:48_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_feature-trixie/11/artifact/build-artifacts/07:23:48_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.journal
After features/support/hooks.rb:100 0.000
9.734
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails from DVD without network and logged in 9.734
Tags: @product @not_release_blocker
29.497
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.157
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 8.220
And I open this VeraCrypt volume in GNOME Files 4.599
Then I see the expected contents in this VeraCrypt volume 0.436
When I lock the currently opened VeraCrypt file container 0.084
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:332: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.339 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a basic VeraCrypt file container with a PIM' (at time 07:24:33)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/11/artifact/build-artifacts/07:24:33_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_feature-trixie/11/artifact/build-artifacts/07:24:33_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_feature-trixie/11/artifact/build-artifacts/07:24:33_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_feature-trixie/11/artifact/build-artifacts/07:24:33_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.journal
After features/support/hooks.rb:100 0.000
9.296
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails from DVD without network and logged in 9.296
Tags: @product @not_release_blocker
44.581
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.090
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 8.831
And I open this VeraCrypt volume in GNOME Files 8.117
Then I see the expected contents in this VeraCrypt volume 0.462
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:332: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 6.188 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a hidden VeraCrypt file container' (at time 07:25:32)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/11/artifact/build-artifacts/07:25:32_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_feature-trixie/11/artifact/build-artifacts/07:25:32_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/11/artifact/build-artifacts/07:25:32_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/11/artifact/build-artifacts/07:25:32_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:100 0.016
9.816
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails from DVD without network and logged in 9.816
Tags: @product @not_release_blocker
27.087
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.650
And I cancel the GNOME authentication prompt 3.056
And I unlock and mount this VeraCrypt volume with GNOME Disks 11.618
And I open this VeraCrypt volume in GNOME Files 4.236
Then I see the expected contents in this VeraCrypt volume 0.435
When I lock the currently opened VeraCrypt volume 0.089
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:332:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:54:in `When I lock the currently opened VeraCrypt volume'
Then the VeraCrypt volume has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.389 
SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile' (at time 07:26:15)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/11/artifact/build-artifacts/07:26:15_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_feature-trixie/11/artifact/build-artifacts/07:26:15_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_feature-trixie/11/artifact/build-artifacts/07:26:15_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_feature-trixie/11/artifact/build-artifacts/07:26:15_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
9.637
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails from DVD without network and logged in 9.637
Tags: @product @not_release_blocker
28.416
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 10.358
And I cancel the GNOME authentication prompt 2.365
And I unlock and mount this VeraCrypt volume with GNOME Disks 9.704
And I open this VeraCrypt volume in GNOME Files 5.413
Then I see the expected contents in this VeraCrypt volume 0.484
When I lock the currently opened VeraCrypt volume 0.090
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/veracrypt.rb:332:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:63:in `When I lock the currently opened VeraCrypt volume'
Then the VeraCrypt volume has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.403 
SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a hidden VeraCrypt volume' (at time 07:26:59)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/11/artifact/build-artifacts/07:26:59_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_feature-trixie/11/artifact/build-artifacts/07:26:59_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_feature-trixie/11/artifact/build-artifacts/07:26:59_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_feature-trixie/11/artifact/build-artifacts/07:26:59_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.journal
After features/support/hooks.rb:100 0.000
9.338
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails from DVD without network and logged in 9.338
Tags: @product @not_release_blocker
51.917
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.173
And I unlock and mount this VeraCrypt file container with GNOME Disks 23.966
And I open this VeraCrypt volume in GNOME Files 4.232
Then I see the expected contents in this VeraCrypt volume 0.460
When I lock the currently opened VeraCrypt file container 0.083
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/veracrypt.rb:332:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:71:in `When I lock the currently opened VeraCrypt file container'
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.387 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile' (at time 07:28:05)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/11/artifact/build-artifacts/07:28:05_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_feature-trixie/11/artifact/build-artifacts/07:28:05_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/11/artifact/build-artifacts/07:28:05_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_feature-trixie/11/artifact/build-artifacts/07:28:05_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.journal
After features/support/hooks.rb:100 0.015
10.135
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails from DVD without network and logged in 10.135
Tags: @product @not_release_blocker
52.744
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.333
And I unlock and mount this VeraCrypt file container with GNOME Disks 21.261
And I open this VeraCrypt volume in GNOME Files 4.601
Then I see the expected contents in this VeraCrypt volume 0.464
When I lock the currently opened VeraCrypt file container 0.083
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/veracrypt.rb:332:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:79:in `When I lock the currently opened VeraCrypt file container'
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.414 
SCENARIO FAILED: 'Use GNOME Disks to unlock a hidden VeraCrypt file container' (at time 07:29:14)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/11/artifact/build-artifacts/07:29: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_feature-trixie/11/artifact/build-artifacts/07:29:14_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/11/artifact/build-artifacts/07:29:14_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/11/artifact/build-artifacts/07:29:14_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:100 0.014
9.897
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails from DVD without network and logged in 9.897
Tags: @product @not_release_blocker
41.246
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.425
And I unlock and mount this VeraCrypt file container with GNOME Disks 19.657
And I open this VeraCrypt volume in GNOME Files 4.570
Then I see the expected contents in this VeraCrypt volume 0.515
When I lock the currently opened VeraCrypt file container 0.077
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/veracrypt.rb:332:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:87:in `When I lock the currently opened VeraCrypt file container'
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.623 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a PIM' (at time 07:30:10)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/11/artifact/build-artifacts/07:30:10_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/11/artifact/build-artifacts/07:30:10_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/11/artifact/build-artifacts/07:30:10_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_feature-trixie/11/artifact/build-artifacts/07:30:10_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.journal
After features/support/hooks.rb:100 0.000