Bug 1582532 - Issues with encrypted volumes with EXT4 file-system type
Summary: Issues with encrypted volumes with EXT4 file-system type
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 28
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-25 13:52 UTC by ricky.tigg
Modified: 2019-05-28 20:23 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-05-28 20:23:07 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Samples associated to encrypted volume by Nautilus. (40.00 KB, application/x-tar)
2018-05-25 13:52 UTC, ricky.tigg
no flags Details

Description ricky.tigg 2018-05-25 13:52:43 UTC
Created attachment 1441570 [details]
Samples associated to encrypted volume by Nautilus.

Description of problem: Issues associated to encrypted volumes by Nautilus.
Version-Release number of component: nautilus.x86_64 3.28.1-1.fc28 @anaconda

How reproducible: In Nautilus format USB-media partition to EXT4, and password protect the volume with disk encryption LUKS.

Actual results: Last step previous to the execution of the operation, window lacks an entry related to encryption (Nautilus_Format_Confirm_Details.png).

– As expected USB-device entry disappears during the formatting process then reappears once accomplished; then it unexpectedly disappears durably if key F5 is not pressed.
– After volume has been encrypted and is in mounted state, no entry related to encryption is present in Properties.

Enhancement request: Presence of an entry related to encryption in last step previous to the execution of the operation.

Expected results: USB-device entry to remain visible after it reappears first.
– entry related to encryption to be present after volume has been encrypted and is in mounted state.

Additional info: By comparison while encrypted volume is mounted Gparted GUI tool displays it (Gparted_Mounted_encrypted_EXT4_partition.png).

– While encrypted volume is in mounted state:
$ sudo parted -l
...
Partition Table: msdos
...
Number  Start   End     Size    Type     File system  Flags
 1      1049kB  8006MB  8005MB  primary               boot

– While encrypted volume is in unmounted state:
$ sudo parted -l
...
Partition Table: msdos
...
Number  Start   End     Size    Type     File system  Flags
 1      1049kB  3875MB  3874MB  primary  fat32        boot, lba

Comment 1 Ben Cotton 2019-05-02 21:42:29 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Ben Cotton 2019-05-28 20:23:07 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.