Bug 109193 - FILESAVE crashes when saving to subdir that was recently changed from read-only to R/W
Summary: FILESAVE crashes when saving to subdir that was recently changed from read-on...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.3.4.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-18 16:16 UTC by jamesmknott
Modified: 2017-11-29 09:44 UTC (History)
2 users (show)

See Also:
Crash report or crash signature: ["svt::DocumentLockFile::OverwriteOwnLockFile()"]


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jamesmknott 2017-07-18 16:16:01 UTC
I was saving a file to a subdirectory that (unknown to me) was read-only, so of course CALC (correctly..) gave me an error (I am using the LibreOffice, not Windows FILESAVE dialog boxes).  After changing the file to read/write, and trying again a few times, I (incorrectly, I believe) still got CALC save errors.  I tried again, and it crashed.  So perhaps if the ReadOnly bit is changed after the dialog box starts, then the correct pointers/etc aren't being updated???  

LibreOffice created the following dump.

http://crashreport.libreoffice.org/stats/crash_details/dda15d00-29c6-4d95-92a0-9dbaa8a32137

It is my interest to simply be helpful here in reporting this bug.  I can certainly work around it.  You can close this bug for any reason you desire.  FYI.
Comment 1 Buovjaga 2017-08-14 18:13:31 UTC
I cannot reproduce.
Which Windows version are you using?

This is how I did it.
I set the LibO dialogs in Tools - Options - General.
I created a directory, right-clicked it, selected Properties.
Then, in the Security tab I clicked Edit.
I selected my user and ticked Write in the Deny column (Ok, Ok).

I got the warning when trying to save from Calc and the warning was more clearly worded in the master build (insufficient rights..).

I understand this might be a hard-to-reproduce issue as you got the crash only after several tries. It is good that we have the crash report.

Win 10
Version: 5.4.0.3 (x64)
Build ID: 7556cbc6811c9d992f4064ab9287069087d7f62c
CPU threads: 4; OS: Windows 6.19; UI render: default; 
Locale: fi-FI (fi_FI); Calc: group

Version: 6.0.0.0.alpha0+ (x64)
Build ID: 4e2b44860c2c304ea728c512b47ca07aaf1cd452
CPU threads: 4; OS: Windows 6.19; UI render: default; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2017-08-10_23:20:23
Locale: fi-FI (fi_FI); Calc: group
Comment 2 Xisco Faulí 2017-11-20 16:20:28 UTC Comment hidden (obsolete)
Comment 3 jamesmknott 2017-11-20 18:27:42 UTC
I was running Windows 10 Home (fully patched  at the time of the bug report).

I cannot re-create the bug (either).  Sorry. You probably should simply close this bug report.

Thank you for attempting to resolve this problem, and for your contributions to LibreOffice!!.  I have just made a $20 donation to LibreOffice (Confirmation number: 6RV71866PW236460U).
Comment 4 Buovjaga 2017-11-29 09:44:51 UTC
Yeah, I guess we should close. I tried to offer the crash trace to developers, but got no response.