Bug 111487 - HELPAUTHORING: Cannot save file
Summary: HELPAUTHORING: Cannot save file
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Documentation (show other bugs)
Version:
(earliest affected)
5.3.0.3 release
Hardware: All Windows (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-08 11:04 UTC by beimaginativeegroup
Modified: 2017-08-17 14:22 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description beimaginativeegroup 2017-08-08 11:04:21 UTC
Description:
When trying to save a new Help file, I am getting an error dialog with the following text

Error: 
An exception occurred 
Type: com.sun.star.task.ErrorCodeIOException
Message: SfxBaseModel::impl_store <filepath> failed: 0xc10.
Cannot save file.

Unfortunately, I'm not that experienced to understand what the codes so can't really help with that. If I can help in some other way, please tell me. Regarding the dialogs that open (to set the Title, paragraph, id), I am leaving everything empty (so the default text gets written). 

Steps to Reproduce:
1. Click on New Writer Document in the Start Center
2. Click the Create new help file button on the HelpAuthoring toolbar
3. Enter the file name without changing the folder, in my case it's My Documents
4. Click Save and Yes when asked to automatically generate a help file
5. Leave empty the Help Title, Help Description, HelpID (this happened also when I put actual content in those dialogs)

Actual Results:  
I get the dialog with the code referenced above and then the Wrtier document closes. 

Expected Results:
File is saved. 


Reproducible: Always

User Profile Reset: No

Additional Info:


User-Agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36
Comment 1 beimaginativeegroup 2017-08-10 14:24:40 UTC
When resetting the user profile and reinstalling the extension, this seems to work. However, the extension is still quite unstable and comes up with some errors sometimes.
Comment 2 Olivier Hallot 2017-08-17 14:22:56 UTC
I'm closing this one since it looks like it works now. On the instability (which I agree it exist), we need better qualification of the issues.
Feel free to disagree and reopen the bug, but with more data.