[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 150699] KPDF unable to save opened but deleted document
From:       <ko69859 () uta ! fi>
Date:       2008-08-20 15:02:08
Message-ID: 20080820150208.CB0B234EE () immanuel ! kde ! org
[Download RAW message or body]

http://bugs.kde.org/show_bug.cgi?id=150699





--- Comment #4 from ko69859 uta fi  2008-08-20 17:02:06 ---
Thank you for your response and the information.

"Given the uncomplete information of the original report of #114485, you cannot
say that they are the same."

I beg to differ. Of course, the original report of bug 114485 misses a complete
explanation, so we cannot be sure, but the symptoms are clear. What I am
reporting is that the same symptoms - from bug 114485 - are caused by the
procedure reported here, in bug 150699. That is, the error message "File could
not be saved in 'file:///home/me/abc.pdf'. Try to save it to another location."

However, it doesn't really matter in the end whether the issue be tracked here
or there.

*

Let me restate a reproducible case, or, more exactly, two parallel but
absolutely equal cases, 
1a. Open a local pdf file in kpdf, or
1b. Use Firefox to open a remote pdf file in kpdf - this causes a temporary
local file to be created by Firefox and opened by kpdf.

2a. Remove, move or rename the opened local file.
2b. Close Firefox, which causes the temporary local file to be removed. Or, to
get the same effect, remove, move or rename the temporary file manually.

3a and b. Try to save the file from kpdf. No-go, and you get the error message
quoted.

To add a parallel case, do the same with (for example) acroread, and the end
result is different:
3c. Try to save the file from acroread. Works as expected.

*

Now, whether this is a kpdf problem or a Firefox problem. From a user's point
of view, it is definitely a kpdf problem. It's a case where kpdf "has the
document", but simply can't save it.

Is this a kpdf problem from the application designer's point of view? I can not
tell, as I'm not that person.

A quote from the Okular report you referenced:
"Another way to solve it might be to keep opened files in swap or a cache..."

As mentioned, for example acroread manages to save a file it "currently has
open". Apparently they must keep the file cached somewhere or use other magic
to achieve what they do.

Is it a good policy to depend BOTH on other programs not tampering with the
file on the disk AND on the user not moving or removing the file while viewing
it in kpdf? I would say no. I would say it is better for the program to be
self-reliant, but it is not my decision to make.


-- 
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]