Bug 1969875 - plasma-vault unusable because no backend installed by default.
Summary: plasma-vault unusable because no backend installed by default.
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-vault
Version: 35
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Martin Kyral
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-09 11:30 UTC by Lukas Ruzicka
Modified: 2022-12-13 15:24 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-12-13 15:24:56 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Lukas Ruzicka 2021-06-09 11:30:32 UTC
Description of problem:

Plasma Vault application was recently added to the standard KDE installation, but it is unusable as there are no backends installed that would allow to create a vault after fresh installation.

There are three different backends selectable by a dropdown menu:

* CryFS
* EncFS
* gocryptfs

CryFS cannot be installed at all, as it seems not to be packaged for Fedora (see `dnf search cryfs`), the other two can be installed using the `fuse-encfs` and `gocryptfs` packages before a new vault can be created.

I believe that if plasma-vault is part of KDE, the corresponding backend should be installed, too. This is not a problem for power users, but for normal users this one might be a nasty kick.

Version-Release number of selected component (if applicable):

KDE 5.82.0
QT: 5.15.2


How reproducible:

Always

Steps to Reproduce:
1. Click on Vaults
2. Try to add a new vault.
3. See the error messages "Unable to detect the version"

Actual results:

No backend available.

Expected results:

At least one backend should be available.

Comment 2 Ben Cotton 2021-08-10 13:41:20 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle.
Changing version to 35.

Comment 3 Ben Cotton 2022-11-29 16:58:38 UTC
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
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
'version' of '35'.

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

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 Ben Cotton 2022-12-13 15:24:56 UTC
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

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.