Description of problem:Hello whitout sudo package, Veracrypt does not work properly, and when editing a disk, and after filling in the password area a "sudo" elevation error appears. https://fsociety-drive.mycozy.cloud/public?sharecode=jRQlRm76OLqC After installing the package sudo, and adding the user in wheel group, Veracrypt running smoothly. Version-Release number of selected component (if applicable): How reproducible: Install Veracrypt, mount a disk, after the password, the error message appear. Steps to Reproduce: 1.install veracrypt 2.mount a disk 3.typing the password
Thank you for reporting this. Certainly veracrypt does not currently require sudo. Looks like a packaging issue. Assigning to its registered maintainer neoclust.
Assignee: bugsquad => mageia
Why adding the user in the wheel group?
CC: (none) => geiger.david68210
(In reply to David GEIGER from comment #2) > Why adding the user in the wheel group? Hello David, I am at the origin of this package under Mageia. Nicolas had the kindness to integrate it to the distribution. However, Veracrypt has always needed either an entry in the sudoers file (which I believe is deprecated?), So the way around was to register the user in the group wheel. I admit to doing it more by reflex / habit.
So you can test upcoming veracrypt-1.23-1.1.mga7 in Core/Updates_testing! Make sure veracrypt and sudo are uninstalled and see when you install this new update if it pulls "sudo" and also if a note is showed to tell users to add themselves to the wheel group on new installs.
Hello David, Thank you very much for your investment in distribution, as well as to all other contributors. I try this tonight as soon as I have access to my machine.
(In reply to David GEIGER from comment #4) > So you can test upcoming veracrypt-1.23-1.1.mga7 in Core/Updates_testing! > > Make sure veracrypt and sudo are uninstalled and see when you install this > new update if it pulls "sudo" and also if a note is showed to tell users to > add themselves to the wheel group on new installs. Hello, After testing under a virtual machine created for the occasion, the notification to add to the user group appears correctly. After restarting the Veracrypt system works perfectly. However, is it possible to change the text of the notification, indicating that a restart / disconnection re-connection, will be necessary to take into account the addition of the user in the group Wheel? because a new user, when first using Veracrypt before rebooting, may end up in front of this message without knowing what to do. https://fsociety-drive.mycozy.cloud/public?sharecode=BY9SwgtaJFw0 Simple assumption, otherwise the package no longer requires the installation of sudo. Thank you all again for your availability.
hmmm! adding my user to the wheel group switched my polkit password from the root one to the user's one, so this is not a good fix for veracrypt!
I understand that leaving the keys of the house can cause problems. What workaround to use in this case? I believe the sudoers file is no longer using?
Can you ask upstream, please? to see what they think about https://github.com/veracrypt/VeraCrypt/issues
You might want to add to the discussion of this at https://github.com/veracrypt/VeraCrypt/issues/496
CC: (none) => rihoward1
(In reply to David GEIGER from comment #9) > Can you ask upstream, please? to see what they think about > > https://github.com/veracrypt/VeraCrypt/issues The question is asked ... :) https://github.com/veracrypt/VeraCrypt/issues/533
(In reply to r howard from comment #10) > You might want to add to the discussion of this at > https://github.com/veracrypt/VeraCrypt/issues/496 Sorry our messages are crossed. I did not see this thread, so I created a new one.
Mageia 7 is EOL since July 1st 2021. There will not have any further bugfix for this release. You are encouraged to upgrade to Mageia 8 as soon as possible. @reporter, if this bug still apply with Mageia 8, please let us know it. @packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead. This bug report will be closed OLD if there is no further notice within 1st September 2021.
Hi bug reporter and hi assignee and others involved, Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly. This report is being closed as OLD because it was filed against Mageia 7, for which support ended on June 30th 2021. Thanks, Marja
Status: NEW => RESOLVEDResolution: (none) => OLD