| Summary: | creating lock file failed when FILEOPEN on exFAT-drive | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | davero |
| Component: | Calc | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | davero, serval2412, telesto, xiscofauli |
| Priority: | medium | ||
| Version: | 6.2.0.3 release | ||
| Hardware: | All | ||
| OS: | Windows (All) | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Bug Depends on: | |||
| Bug Blocks: | 114300 | ||
|
Description
davero
2019-03-05 23:05:35 UTC
On Win10 + LO 6.1.5 + exFat key, I don't reproduce this. I created a brand odt file containing just "test", saved file, closed LO. Then I opened the file, no error. I did the same test with master sources (future 6.3.0) updated today. Thank you for reporting the bug. To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and re-test? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present Dear davero, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping Sorry for the late answer as I'm seldom in Windows. Good news, the problem is gone without any needed action. But I recall having troubles writing to that drive. Maybe Windows mounted it wrong... So no lock file could be created, which lead to the described problem. Thanks Julien and Xisco for your engagement! Thanks for the feedback, let's adjust status to WORKSFORME, as it's unknown what actually fixed the problem. |