I added some more steps to the test plan to make sure that this actually describes the desired outcome.
** Description changed: [ Impact ] 1. Ensure that udisks2 supports unlocking TCRYPT devices: - sudo touch /etc/udisks2/tcrypt.conf && sudo systemctl restart udisks2 + sudo touch /etc/udisks2/tcrypt.conf && sudo systemctl restart udisks2 2. Ensure that auto-mounting is enabled: - dconf write /org/gnome/desktop/media-handling/automount true + dconf write /org/gnome/desktop/media-handling/automount true 3. Attach a VeraCrypt file container: - udisksctl loop-setup --file veracrypt-container.hc + udisksctl loop-setup --file veracrypt-container.hc 4. GNOME Shell opens the unlock dialog. Enter an incorrect password and try to unlock. 5. The unlock dialog just closes. + The password should have been asked again. + Coming from https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7631 - [ Test case ] - 1. Create a VeraCrypt volume in a file - DISK=/tmp/veracrypt.img - dd if=/dev/zero of="$DISK" bs=1M count=10 - DEV=$(sudo losetup --find --show "$DISK") - sudo zuluCrypt-cli -c -t vcrypt -p test -d "$DEV" - sudo losetup --detach "$DEV" + DISK=/tmp/veracrypt.img + dd if=/dev/zero of="$DISK" bs=1M count=10 + DEV=$(sudo losetup --find --show "$DISK") + sudo zuluCrypt-cli -c -t vcrypt -p test -d "$DEV" + sudo losetup --detach "$DEV" 2. Ensure that udisks2 supports unlocking TCRYPT devices: - sudo touch /etc/udisks2/tcrypt.conf && sudo systemctl restart udisks2 + sudo touch /etc/udisks2/tcrypt.conf && sudo systemctl restart udisks2 3. Ensure that auto-mounting is enabled: - dconf write /org/gnome/desktop/media-handling/automount true + dconf write /org/gnome/desktop/media-handling/automount true 4. Attach the VeraCrypt file container: - udisksctl loop-setup --file "$DISK" + udisksctl loop-setup --file "$DISK" 5. GNOME Shell opens the unlock dialog. Enter an incorrect password and try to unlock. + + 6. See that the password gets asked again. + + 7. Enter the correct password + + 8. See that the volume is correctly automounted and the password is not + prompted for again. [ Regression potential ] Password is not asked again when trying to unlock other kind of encrypted devices. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2084281 Title: Unlock dialog for VeraCrypt volumes closes without error message when wrong password entered Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Noble: Fix Committed Bug description: [ Impact ] 1. Ensure that udisks2 supports unlocking TCRYPT devices: sudo touch /etc/udisks2/tcrypt.conf && sudo systemctl restart udisks2 2. Ensure that auto-mounting is enabled: dconf write /org/gnome/desktop/media-handling/automount true 3. Attach a VeraCrypt file container: udisksctl loop-setup --file veracrypt-container.hc 4. GNOME Shell opens the unlock dialog. Enter an incorrect password and try to unlock. 5. The unlock dialog just closes. The password should have been asked again. Coming from https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7631 [ Test case ] 1. Create a VeraCrypt volume in a file DISK=/tmp/veracrypt.img dd if=/dev/zero of="$DISK" bs=1M count=10 DEV=$(sudo losetup --find --show "$DISK") sudo zuluCrypt-cli -c -t vcrypt -p test -d "$DEV" sudo losetup --detach "$DEV" 2. Ensure that udisks2 supports unlocking TCRYPT devices: sudo touch /etc/udisks2/tcrypt.conf && sudo systemctl restart udisks2 3. Ensure that auto-mounting is enabled: dconf write /org/gnome/desktop/media-handling/automount true 4. Attach the VeraCrypt file container: udisksctl loop-setup --file "$DISK" 5. GNOME Shell opens the unlock dialog. Enter an incorrect password and try to unlock. 6. See that the password gets asked again. 7. Enter the correct password 8. See that the volume is correctly automounted and the password is not prompted for again. [ Regression potential ] Password is not asked again when trying to unlock other kind of encrypted devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2084281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
