[frameworks-kdoctools] [Bug 443364] Meinproc5 issues multiple "I/O error" messages

[David C. Bryant]

https://bugs.kde.org/show_bug.cgi?id=443364

David C. Bryant <davidbryant at gvtc.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
         Resolution|WORKSFORME                  |---
             Status|RESOLVED                    |REOPENED

--- Comment #3 from David C. Bryant <davidbryant at gvtc.com> ---
OK, I dug into this one some more. Here's what's going on.

1. Because of other problems (with Dolphin / Konqueror --
https://bugs.kde.org/show_bug.cgi?id=443259),  I devised a workaround that
involved the creation of a second user account. I set up the working directory
so that both User1 and User2 have read/write permissions.

2. This bug can be reproduced as follows: 
-- Set up a second user account.
-- Create a working directory that allows any user to have read/write access
(use chmod, or Dolphin).
-- Clone a /docs directory into that working directory. The app doesn't matter,
but I've been working on KOrganizer.
-- Log in as User1 and run meinproc5 index.docbook in the working directory.
-- Log out, then log in as User2. Run meinproc5 index.docbook against the
working directory again. You will get the I/O errors.

I can work around this. And it only happens in the context of two users, both
with r/w access to the directory in which the index.docbook file resides. If
the existing .html files were created by the user who is currently logged in,
meinproc5 overwrites the .html files with nary a whimper. But if the existing
.html files were created by the other user, meinproc5 will not overwrite them,
even though the file permissions say it's OK to do so.

I suspect the existing code implicitly assumes that only one user will ever be
running meinproc5 in a particular working directory. The error message that is
issued ("QIODevice::write (QFile, "index.html"): device not open") is not very
informative. If there must be an error message in this context, it really ought
to say something about file ownership. Better yet, meinproc5 should recognize
that it has write access in the working directory, and overwrite the old files.

-- 
You are receiving this mail because:
You are the assignee for the bug.