Plasma Vault in 5.11.0; wrong CryFS & fusermount.

English Applications
#1

Hello

I suspect the right answer is probably “wait til 5.11.1 or .2”, but i’ll ask anyway [TW Snapshot 20171018]:

  1. According to the KDE promo https://www.kde.org/announcements/plasma-5.11.0.php we’re supposed to get Plasma Vault in this version, but it’s not installed during the zypper dup
    that upgrades 5.10.5 to 5.11.0. 1. Doing
sudo zypper in plasma-vault

then logging out / in, creates the vault padlock widget in the System Tray.

  1. Clicking said widget & choosing to create a new vault, leads to this next fault:
cryfs: Wrong version installed. The required version is 0.9.6

fusermount: Wrong version installed. The required version is 2.9.7
  1. Instead:
gooeygirl@linux-sr0s:~> **zypper if fusermount**       Loading repository data...
Reading installed packages...
package 'fusermount' not found.


gooeygirl@linux-sr0s:~> **zypper if cryfs**
Loading repository data...
Reading installed packages...
package 'cryfs' not found.


gooeygirl@linux-sr0s:~> **sudo zypper in cryfs**     
[sudo] password for root: 
Loading repository data...
Reading installed packages...
'cryfs' not found in package names. Trying capabilities.
No provider of 'cryfs' found.
Resolving package dependencies...
Nothing to do.


gooeygirl@linux-sr0s:~> **sudo zypper in fusermount**
Loading repository data...
Reading installed packages...
'fusermount' not found in package names. Trying capabilities.
No provider of 'fusermount' found.
Resolving package dependencies...
Nothing to do.


gooeygirl@linux-sr0s:~> **cnf fusermount**
Program 'fusermount' is present in package 'fuse', which is installed on your system.
Absolute path to 'fusermount' is '/usr/bin/fusermount'. Please check your $PATH variable to see whether it contains the mentioned path.


gooeygirl@linux-sr0s:~> **cnf cryfs**
cryfs: command not found                      


gooeygirl@linux-sr0s:~> **zypper if fuse**
Loading repository data...
Reading installed packages...
Information for package fuse:
-----------------------------
Repository     : Main Repository (OSS) 
Name           : fuse                  
Version        : 2.9.5-2.2             
Arch           : x86_64                
Vendor         : openSUSE              
Installed Size : 223.4 KiB             
Installed      : Yes                   
Status         : up-to-date            
Source package : fuse-2.9.5-2.2.src    
Summary        : User space File System
Description    :                       
    With FUSE, a user space program can export a file system through the
    kernel-default (Linux kernel).


    User space file systems which are implemented using FUSE are provided
    by the following packages:


    - curlftpfs (mount FTP servers),


    - encfs (layered file encryption),


    - fuseiso (mount iso, img, bin, mdf and nrg CD-ROM images),


    - fusepod (mount iPods),


    - fusesmb (mount a fully browseable network neighborhood),


    - gphotofs (mount gphoto-supported cameras),
                                                                                                                                     
    - ntfs-3g (mount NTFS volumes read-write),                                                                                       
                                                                                                                                     
    - obexfs (mount of bluetooth devices),                                                                                           
                                                                                                                                     
    - sshfs (mount over ssh),


    - wdfs (mount of WebDAV shares)


    This package contains the mount binaries for fuse (might not be needed
    by some FUSE filesystems like ntfs-3g) and the documentation for FUSE.


    After installing fuse-devel, administrators can compile and install
    other user space file systems which can be found at
    http://fuse.sourceforge.net/wiki




gooeygirl@linux-sr0s:~>

Is resolving these problems practicable, in this installed Snapshot, or would it be better for me to forget about Vault now, & just wait for some future Snapshot?

#2

Take a look at comment 1 on this bug report: https://bugzilla.opensuse.org/show_bug.cgi?id=1062816

#3

Hi
The cryfs package is not even part of Tumbleweed?

If you look at the requires;
https://build.opensuse.org/package/binary/openSUSE:Factory/plasma-vault?arch=x86_64&filename=plasma-vault-5.11.1-1.1.x86_64.rpm&repository=standard

There is encfs, is this installed?

I suggest running the command to show additional options;


zypper se --help
zypper se --file-list fusermount
#4

Thanks Paul & Malcolm. Given the Bug Report, i think it’s best i just sit this one out, in the hope / assumption that the magicians upstream from me will sooner or later solve it.

Wrt encfs, yes it is installed, but i don’t like to use it, given it is apparently well known to be insecure [kinda defeating the basic point, IMO]. In any event, even if i did choose it, Vault is still currently not a goer here in TW [albeit it works fine in [i]KDE Neon, btw]:

encfs: Correct version found
encfsctl: Correct version found

fusermount: Wrong version installed. The required version is 2.9.7
#5

Hi
So you need to install cryfs then… it’s not in the default distribution though… but given it’s built in home user projects on OBS…? You will need to wait for fuse to be fixed…

#6

If you want to give it a try…

fuse 2.9.7 is in the “filesystem” repository:
http://download.opensuse.org/repositories/filesystems/openSUSE_Tumbleweed/

and as Malcolm pointed out, cryFS 0.9.7 is available from a couple of home repositories:

home:hgraeber
http://download.opensuse.org/repositories/home:/hgraeber/openSUSE_Tumbleweed/

home:gasinvein
http://download.opensuse.org/repositories/home:/gasinvein/openSUSE_Tumbleweed/

#7

On Sat 21 Oct 2017 01:16:01 PM CDT, tannington wrote:

If you want to give it a try…

fuse 2.9.7 is in the “filesystem” repository:
http://tinyurl.com/yawvpewv

and as Malcolm pointed out, cryFS 0.9.7 is available from a couple of
home repositories:

home:hgraeber
http://tinyurl.com/y8lqaaem

home:gasinvein
http://tinyurl.com/ycqwbzhr

Hi
Also here :wink:
https://build.opensuse.org/package/show/home:malcolmlewis:TESTING/cryfs

Not hard required to fuse 2.9.7, only requirement is for fuse to be >=
2.8.6.

–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.2|GNOME 3.20.2|4.4.87-18.29-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

#8

Sorry, didn’t find your build when I searched… You only just built that :)…

#9

Hi
Yes, just for Tumbleweed… :wink:

#10

“nothing provides libcryfs-cli.so()(64bit) needed by cryfs-0.9.7-2.1.x86_64”

possibly the answer lies here (last few posts)
https://github.com/cryfs/cryfs/issues/159
but I’ve only very briefly skimmed through, about to go out :slight_smile:

#11

On Sat 21 Oct 2017 05:36:01 PM CDT, tannington wrote:

malcolmlewis;2842505 Wrote:
> Hi
> Yes, just for Tumbleweed… :wink:

“nothing provides libcryfs-cli.so()(64bit) needed by
cryfs-0.9.7-2.1.x86_64”

possibly the answer lies here (last few posts)
https://github.com/cryfs/cryfs/issues/159
but I’ve only very briefly skimmed through, about to go out :slight_smile:

Hi
Ahhh, so I use the OBS %cmake macro, looks like I need to drop back to
standard cmake routine, might look at the CMakeLists a bit further…

–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.2|GNOME 3.20.2|4.4.87-18.29-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

#12

Thanks Paul & Malcolm, once again. Gosh, you blokes are awesome. Yes i would be happy to give it a go, but will hold off a bit longer in anticipation of Malcolm’s next build version, heehee.

#13

Hi
It’s fixed and built now…

#14

Excellent, thanks. Vault now works a treat, heehee.

[Mind you, there was initially a [i]very rude bit of misbehaviour. Once the repo was added & i’d upgraded Fuse, then installed CryFS via your built RPM, i was adjusting my Plasma SystemTray setting to make Vault’s widget visible, when plasmashell died an ugly death. Kudos though, it did a really thorough job. My Panel vanished, keyboard stopped responding [but mouse pointer still moved though clicking was dead]. Could not toggle to TTY, could not restart desktop session with Ctrl-Alt-Backspace. Only the usual REISUB method worked. Sigh. Yet again my desire to achieve Uptimes of a week or more was defeated].

What is the correct / advised management strategy now for my newly-added-to-my-repos-list obs://build.opensuse.org/filesystems repo? At first, after getting Vault working & recovering from the crash], i thought it best to disable this repo, so as to avoid future possible headaches during later dups. However, trying an exploratory dup then gave this unpleasant output:

sudo zypper -vvv dup
[sudo] password for root: 
Verbosity: 3
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Initialising Target
Checking whether to refresh metadata for My_openSUSE_Repo
Checking whether to refresh metadata for Vivaldi
Checking whether to refresh metadata for Main Repository (NON-OSS)
Checking whether to refresh metadata for Main Repository (OSS)
Checking whether to refresh metadata for Main Update Repository
Checking whether to refresh metadata for Packman Repository
Loading repository data...
Reading installed packages...
Computing distribution upgrade...
Force resolution: No
Computing upgrade...


Problem: problem with installed package fuse-2.9.7-80.4.x86_64
 Solution 1: install fuse-2.9.5-2.2.x86_64 (with vendor change)
  obs://build.opensuse.org/filesystems  -->  openSUSE


Choose the above solution using '1' or cancel using 'c' [1/c] (c): c

I re-enabled said repo, after which dup was happy… but am i setting myself up for some future headaches with this repo active? Would it be better to again disable it, then lock my Fuse version, then some time in the future when the new Fuse version lands in the standard repos, remove the lock & let dup then change it to the standard repo?

Btw, as i write this a dup is underway in one of my test TW VMs [in which i’d tested the above methodology to get Vault working, before then doing it in Tower’s real TW]. Said VM will end up at TW 20171019, & i noticed this interesting thing in the zypper verbose info at the beginning:


The following application is going to be REMOVED:                                                                                                                              
  Vaults    noarch                                                                                                                                                             


The following 1033 packages are going to be upgraded:


plasma-vault                            5.11.0-1.1 -> 5.11.1-1.1                                          x86_64  openSUSE-Tumbleweed-Oss      openSUSE
plasma-vault-lang                       5.11.0-1.1 -> 5.11.1-1.1                                          noarch  openSUSE-Tumbleweed-Oss      openSUSE

So even though Plasma 5.11.1 itself has not landed in TW yet, Vault does already get the upgrade.

#15

Hi
The version I built didn’t need the updated fuse, so you could use the default Tumbleweed version… I would suggest removing the repo and dup back to the defaults and see how it goes.

#16

You’re way ahead of me now ;)… just about to install Vault and take a look.

This bug report (it’s OK, nothing to panic about) https://bugs.kde.org/show_bug.cgi?id=385444 regarding deleting vaults might be worth a quick read.

@Malcolm

Thanks… :slight_smile:

#17

It seems that Vault itself wants fuse 2.9.7

http://paste.opensuse.org/view/raw/71c44519

As an aside, is there a procedure for requesting a package (in this case cryFS) to be added to the “official” TW repositories?

#18

Hi
Ahh well that’s a vault issue then… :wink:

Yes, find a package and maintainer (no thanks :wink: ), then push to filesystems development repo and then submit to Factory.
https://en.opensuse.org/openSUSE:Factory_submissions
https://en.opensuse.org/openSUSE:Factory_development_model

Then it will wind up in the next stable release (eg Leap 15), then you also need to maintain there as well;
https://en.opensuse.org/openSUSE:Package_maintenance
https://en.opensuse.org/openSUSE:Maintenance_update_process

#19

Yes, sorry, I wasn’t suggesting otherwise. (More as a comment in relation to being able to remove the “filesystems” repo).

Yes, find a package and maintainer (no thanks :wink: ), then push to filesystems development repo and then submit to Factory.
https://en.opensuse.org/openSUSE:Factory_submissions
https://en.opensuse.org/openSUSE:Factory_development_model

Then it will wind up in the next stable release (eg Leap 15), then you also need to maintain there as well;
https://en.opensuse.org/openSUSE:Package_maintenance
https://en.opensuse.org/openSUSE:Maintenance_update_process

Thanks for the info… Something for me to think about :\

#20

No, it’s not CryFS that wants that new Fuse, it’s Vault. See my original post, in which i included:

  1. Clicking said <<Vault>> widget & choosing to create a new vault, leads to this next fault:
cryfs: Wrong version installed. The required version is 0.9.6
fusermount: Wrong version installed. The required version is 2.9.7