Bug 22349 - encfs refuses to close after opening one text-file inside it with kwrite or kate
Summary: encfs refuses to close after opening one text-file inside it with kwrite or kate
Status: RESOLVED DUPLICATE of bug 22351
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Guillaume Rousse
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-08 12:43 CET by peter lawford
Modified: 2018-01-08 20:42 CET (History)
1 user (show)

See Also:
Source RPM: encfs-1.8.1-6.mga6
CVE:
Status comment:


Attachments

Description peter lawford 2018-01-08 12:43:45 CET
Description of problem:I have made an electronic safe on my mageia6 with encfs,
mysafecrypt and mysafeuncrypt being respectively the crypted and uncrypted directories
I open it to access to the files in clear with the command:
[alain4@mag6 ~]$ encfs mysafecrypt mysafeuncrypt
suppose that mysafeuncrypt contains a textfile: toto.txt  
I open it with kwrite or kate:
[alain4@mag6 ~]$ kwrite mysafeuncrypt/toto.txt  or the same replacing kwrite by kate
I close it with the keys combination Ctrl+Q
when I want to close my safe by the command
[alain4@mag6 ~]$ fusermount -u mysafeuncrypt 
I get the return:
fusermount: failed to unmount mysafeuncrypt: Device or resource busy

that doesn't happen with mageia5





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


How reproducible:


Steps to Reproduce:
1.
2.
3.
Comment 1 peter lawford 2018-01-08 17:52:16 CET
the same happens if I close the textfile with the key combination Alt+F4
Comment 2 Marja Van Waes 2018-01-08 20:39:39 CET
Assigning to the registered encfs maintainer.

CC: (none) => marja11
Assignee: bugsquad => guillomovitch

Comment 3 Marja Van Waes 2018-01-08 20:42:24 CET
22351 is the same bug, but better worded.

*** This bug has been marked as a duplicate of bug 22351 ***

Resolution: (none) => DUPLICATE
Status: NEW => RESOLVED


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