Bug 63288 - CONFIGURATION: CRASH if user profile sub folder "extensions" is write protected.
Summary: CONFIGURATION: CRASH if user profile sub folder "extensions" is write protected.
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
(earliest affected) release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
Keywords: haveBacktrace
Depends on:
Blocks: User-Profile
  Show dependency treegraph
Reported: 2013-04-09 04:40 UTC by Rainer Bielefeld Retired
Modified: 2019-02-18 08:49 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Bug 63288 - WinDbg session with FAILED_SOURCE_CODE (12.71 KB, text/plain)
2013-05-15 07:02 UTC, bfoman (inactive)

Note You need to log in before you can comment on or make changes to this bug.
Description Rainer Bielefeld Retired 2013-04-09 04:40:53 UTC
Steps how to reproduce [Reproducible] with  "LibreOffice rc " German UI/ German Locale [Build-ID: f969faf] {pull date 2013-04-03} on German WIN7 Home Premium (64bit):
1. In WIN Files Explorer go to <C:\Users\user\AppData\Roaming\LibreOffice\3\user>
   (or similar on your PC)
2. 'Rightclick folder extensions -> Properties - Check "Write Protected"' <ok>
3. In appearing message select 'Apply here, for subfolders and all files' <ok>
   > Chenages will be applied
4. Launch LibO
5. From Start Center open new empty Writer Document
6. Menu 'Tools -> Options -> Extension Manager'
   Bug: Runtime Error   (for soffice.bin)

files with contents will crash after a while without any action, may be even an empty one.

Of course these test conditions are quite a stretch, But there might be more sophisticated and hidden situations causing crashes like in "Bug 63240 - CRASH in Tools->Extension manager->Check for updates'. 

LibO should not crash, but contribute a useful error message.
Comment 1 bfoman (inactive) 2013-05-15 07:02:14 UTC
Created attachment 79324 [details]
Bug 63288 - WinDbg session with FAILED_SOURCE_CODE

Confirmed with:
Build ID: own W7 debug build
Windows 7 Professional SP1 64 bit

Attached full WinDbg session with FAILED_SOURCE_CODE.
Comment 2 bfoman (inactive) 2013-05-15 07:02:41 UTC
NEW as bug confirmed and bt attached.
Comment 3 Caolán McNamara 2014-10-09 13:45:49 UTC
caolanm->sberg: I got no crash with 4.2 onwards on linux if i chmod -R -w my user dir. Worth a look-see under windows ?
Comment 4 Stephan Bergmann 2014-10-10 08:50:57 UTC
I guess I cannot properly reproduce ths setup from comment 0, as when I go to the Properties of C:\Users\sbergman\AppData\Roaming\LibreOffice\4\user\extensions of a fresh LO master installation on Win 7, "Attributes: Read-only (Only applies to files in folder)" is already checked (as it is for the user directory and all its other sub-dirs, too).
Comment 5 QA Administrators 2015-10-14 19:58:08 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2016-11-08 11:38:17 UTC Comment hidden (obsolete)
Comment 7 Thomas Lendo 2018-09-25 22:08:18 UTC
Like comment 3, on Linux I got no crash but I can't see any installed extension anymore.
Comment 8 Julien Nabet 2019-02-15 16:33:49 UTC
On Win7, I got the same as Stephan's comment (comment 4).
May we close this one?
Comment 9 Stephan Bergmann 2019-02-18 08:49:07 UTC
Then lets close as WORKSFORME.  (And one isn't supposed to mess with LO's internal file storage, as done in comment 0, in the first place.)