Hello Marco, or anyone else affected, Accepted gnome-shell into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- shell/46.0-0ubuntu6~24.04.6 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-noble -- 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
