Project Number Date
test_Tails_ISO_feature-trixie 8 30 May 2025, 06:48

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:23.176 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.433
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.433
Tags: @product @not_release_blocker
19.664
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.034
And I cancel the GNOME authentication prompt 2.530
And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 5.633
And I open this VeraCrypt volume in GNOME Files 3.789
Then I see the expected contents in this VeraCrypt volume 0.596
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: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.322 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a USB drive that has a basic VeraCrypt volume' (at time 07:14:17)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:14:17_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/8/artifact/build-artifacts/07:14:17_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/8/artifact/build-artifacts/07:14:17_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/8/artifact/build-artifacts/07:14:17_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.journal
After features/support/hooks.rb:100 0.000
9.464
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.464
Tags: @product @not_release_blocker
23.551
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.347
And I cancel the GNOME authentication prompt 2.586
And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 6.112
And I open this VeraCrypt volume in GNOME Files 3.953
Then I see the expected contents in this VeraCrypt volume 0.465
When I lock the currently opened VeraCrypt volume 0.085
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.320 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a USB drive that has a hidden VeraCrypt volume' (at time 07:14:56)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:14:56_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/8/artifact/build-artifacts/07:14:56_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/8/artifact/build-artifacts/07:14:56_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/8/artifact/build-artifacts/07:14:56_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.350
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails from DVD without network and logged in 9.350
Tags: @product @not_release_blocker
28.790
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 15.954
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 8.776
And I open this VeraCrypt volume in GNOME Files 3.514
Then I see the expected contents in this VeraCrypt volume 0.467
When I lock the currently opened VeraCrypt file container 0.076
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.308 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a basic VeraCrypt file container with a PIM' (at time 07:15:39)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:15:39_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/8/artifact/build-artifacts/07:15:39_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/8/artifact/build-artifacts/07:15:39_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/8/artifact/build-artifacts/07:15:39_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.journal
After features/support/hooks.rb:100 0.000
8.912
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails from DVD without network and logged in 8.912
Tags: @product @not_release_blocker
39.330
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 26.376
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 8.603
And I open this VeraCrypt volume in GNOME Files 3.853
Then I see the expected contents in this VeraCrypt volume 0.424
When I lock the currently opened VeraCrypt file container 0.072
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 5.374 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a hidden VeraCrypt file container' (at time 07:16:33)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:16:33_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/8/artifact/build-artifacts/07:16:33_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:16:33_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/8/artifact/build-artifacts/07:16:33_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:100 0.016
9.016
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.016
Tags: @product @not_release_blocker
25.480
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 6.990
And I cancel the GNOME authentication prompt 2.852
And I unlock and mount this VeraCrypt volume with GNOME Disks 11.403
And I open this VeraCrypt volume in GNOME Files 3.730
Then I see the expected contents in this VeraCrypt volume 0.420
When I lock the currently opened VeraCrypt volume 0.082
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.412 
SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile' (at time 07:17:13)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:17:13_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/8/artifact/build-artifacts/07:17:13_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/8/artifact/build-artifacts/07:17:13_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/8/artifact/build-artifacts/07:17:13_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.027
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails from DVD without network and logged in 9.027
Tags: @product @not_release_blocker
25.839
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.329
And I cancel the GNOME authentication prompt 2.551
And I unlock and mount this VeraCrypt volume with GNOME Disks 8.668
And I open this VeraCrypt volume in GNOME Files 3.778
Then I see the expected contents in this VeraCrypt volume 0.433
When I lock the currently opened VeraCrypt volume 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: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.278 
SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a hidden VeraCrypt volume' (at time 07:17:53)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:17:53_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/8/artifact/build-artifacts/07:17:53_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/8/artifact/build-artifacts/07:17:53_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/8/artifact/build-artifacts/07:17:53_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.journal
After features/support/hooks.rb:100 0.000
8.904
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 8.904
Tags: @product @not_release_blocker
49.287
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 22.901
And I unlock and mount this VeraCrypt file container with GNOME Disks 21.983
And I open this VeraCrypt volume in GNOME Files 3.882
Then I see the expected contents in this VeraCrypt volume 0.431
When I lock the currently opened VeraCrypt file container 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: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.342 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile' (at time 07:18:57)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:18:57_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/8/artifact/build-artifacts/07:18:57_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/8/artifact/build-artifacts/07:18:57_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/8/artifact/build-artifacts/07:18:57_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.journal
After features/support/hooks.rb:100 0.014
8.903
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 8.903
Tags: @product @not_release_blocker
49.593
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 25.980
And I unlock and mount this VeraCrypt file container with GNOME Disks 19.286
And I open this VeraCrypt volume in GNOME Files 3.807
Then I see the expected contents in this VeraCrypt volume 0.434
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.286 
SCENARIO FAILED: 'Use GNOME Disks to unlock a hidden VeraCrypt file container' (at time 07:20:00)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:20:00_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/8/artifact/build-artifacts/07:20:00_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:20:00_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:20:00_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:100 0.014
8.981
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails from DVD without network and logged in 8.981
Tags: @product @not_release_blocker
39.643
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.507
And I unlock and mount this VeraCrypt file container with GNOME Disks 18.753
And I open this VeraCrypt volume in GNOME Files 4.076
Then I see the expected contents in this VeraCrypt volume 0.221
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: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.312 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a PIM' (at time 07:20:54)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:20:54_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/8/artifact/build-artifacts/07:20:54_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/8/artifact/build-artifacts/07:20:54_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/8/artifact/build-artifacts/07:20:54_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.journal
After features/support/hooks.rb:100 0.000