Bug 395015 - Manual Partitioning - Unable to Create Physical Volume for Encryption
Summary: Manual Partitioning - Unable to Create Physical Volume for Encryption
Status: RESOLVED WORKSFORME
Alias: None
Product: neon
Classification: KDE Neon
Component: Live/Install images (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-03 22:53 UTC by jason.s.m
Modified: 2022-12-26 05:21 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jason.s.m 2018-06-03 22:53:28 UTC
In the latest stable release of KDE Neon, I am unable to add a physical volume for encryption in the manual partitioning menu.  When a partition is selected and the "physical volume for encryption" option is selected in the drop down box, it does not prompt me to input an encryption password like Ubuntu based installers always have.  Even when I click "Create", it still does not prompt me for anything, and a crypto partition is made with (seemingly) no assigned password.

At this point the newly created crypto partition also does not show up in the partitioning menu as a separate volume in which I can edit the filesystem and mount point, as it always has in other Ubuntu based installers.

At this point when I press the back button to go to the previous step of the installer, a message comes up saying "An error occurred while creating a keyfile", followed by one that says "An error occurred while configuring encrypted volumes.  The configuration has been aborted."
Comment 1 jason.s.m 2018-06-03 22:56:03 UTC
**Additional note, No logs were attached because I did not know where to look.  I checked /var/log/installer/debug but I couldn't find any relevant information reading through it.
Comment 2 Justin Zobel 2022-11-26 00:13:55 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 3 Bug Janitor Service 2022-12-11 05:07:21 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2022-12-26 05:21:13 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!