winapps-org / winapps-org/winapps
Office temporary lock files not cleaned up & wrong modification date
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 16k
- Forks
- 508
- Avg merge
- 13h 35m
- Merged PRs (30d)
- 3
Description
I'm not sure if this is a Winapps bug or where else to ask.
When I edit a file in Office, it creates a file starting with "~$" at beginning which is a lock file ("this file is being edited") that's normally deleted after you close the file.
(also note that the modification date is in the future)
However, when I run Office in Winapps this is NOT deleted afterwards. It is deleted just fine when using Office running in Wine/Crossover and also when running Office in a "normal" Windows VM (e.g. in Virt-Manager or Boxes) with access to the /home folder. Hence I'm opening the bug here because it seems to be Winapps-specific, at least for me.
My suspicion would be that there's something wrong with the way the Linux drive is mounted in the Windows VM. I'm using the Docker image for the Windows VM.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Docker image configuration and the Linux drive mount used by the Windows VM. Reproduce the Office lock-file behavior and inspect the resulting file timestamps; done means temporary "~$" files are removed after closing Office and their modification dates are correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, linux, shell
- Domain
- desktop, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100