Bug 132170 - LO 7.0A0 does not save
Summary: LO 7.0A0 does not save
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.0.0.0.alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-17 03:05 UTC by morvan
Modified: 2020-04-19 19:53 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
Error Message (Ptg_Br) (60.15 KB, image/png)
2020-04-17 03:05 UTC, morvan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description morvan 2020-04-17 03:05:21 UTC
Created attachment 159647 [details]
Error Message (Ptg_Br)

When I try t save, I receive a message of error.
How to reproduce:
Open a tool (Writer, in this case, where I see the error. Tried over calc and it saves flawlessly);
Put a text (copy, paste or shortcut to autotext);
invoke saving;
a message of error pops up!
Comment 1 ian 2020-04-19 15:02:06 UTC
Thank you for reporting the bug.

I could not reproduce the bug using a recent master build on Windows.

Could you please clarify what you mean by "Put a text (copy, paste or shortcut to autotext);"?
I interpreted this to mean that you inserted AutoText into the document.
(I inserted AutoText and experienced no problems with saving a document.)

Using:
Version: 7.0.0.0.alpha0+ (x64)
Build ID: b0b9d736fb9ed73e849f80800916466868dbce28
CPU threads: 2; OS: Windows 10.0 Build 17763; UI render: Skia/Raster; VCL: win; 
Locale: en-US (en_US); UI-Language: en-US
Calc: CL
Comment 2 morvan 2020-04-19 19:53:48 UTC
(In reply to ian from comment #1)
> Thank you for reporting the bug.
> 
> I could not reproduce the bug using a recent master build on Windows.
> 
> Could you please clarify what you mean by "Put a text (copy, paste or
> shortcut to autotext);"?
...
Ya, I was trying to put a Dummy Text and saving it.
Unhappily, I could not reproduce today, either because I entered right extension, or because I said no to "Recoverig", which warned me twice about file to recover (from last bad experience). Today it worked out, hence I can beg you to remove this or treat as resolved.
And sorry for the time taken for verifying.