Issue 8899 - Will not write to Cryptographic File System
Summary: Will not write to Cryptographic File System
Status: CLOSED DUPLICATE of issue 5108
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.1
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: stefan.baltzer
QA Contact: issues@sw
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2002-11-01 20:14 UTC by Unknown
Modified: 2003-09-08 16:56 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2002-11-01 20:14:11 UTC
Able to open a file from a Cryptographic File System (cfs).  But when I try to
save the file or use "save as", the following error appears...

Error saving the document [old document name]
Nonexistent object.
nonexistent file. 

Where I say "old document name" I note that the new name I specified in "save
as" is not the one that shows up, rather the old name.  For new documents this
is "Untitled1" etc...

Otherwise, I'm able to save test files in that directory using a myriad of other
programs including AbiWord, Mozilla, Evolution and a UNIX pipe.

Also to note, that CFS is very paranoid about who it lets read a directory.  Not
even root can determine the contents of a file that has been mounted.  I saw
some speculation that this might be the cause in the mailing list for a BSD
install, but was unable to confirm that it had anything to do with this problem.

Information on CFS can be found at...

http://www.crypto.com/software/
Comment 1 prgmgr 2002-11-20 19:08:50 UTC
Thank you for using and supporting OOo.

While this issue is not exactly the same as issue 5108, I suspect the
root cause is the same.

Marking as a duplicate of issue 5108 for now.

*** This issue has been marked as a duplicate of 5108 ***
Comment 2 michael.bemmer 2003-03-11 17:20:29 UTC
As mentioned on the qa dev list on March 5th I will close all resolved duplicate
issues. Please see this posting for details. First step in IssueZilla is
unfortunately to set them to verified.
Comment 3 michael.bemmer 2003-03-11 17:24:18 UTC
As mentioned on the qa dev list on March 5th I will close all resolved duplicate
issues. Please see this posting for details. First step in IssueZilla is
unfortunately to set them to verified.
Comment 4 michael.bemmer 2003-03-11 17:30:09 UTC
As mentioned on the qa dev list on March 5th I will close all resolved duplicate
issues. Please see this posting for details. First step in IssueZilla is
unfortunately to set them to verified.
Comment 5 michael.bemmer 2003-03-11 17:41:38 UTC
As mentioned on the qa dev list on March 5th I will close all resolved duplicate
issues. Please see this posting for details.