Bug 128271 - Smooth transition allowed on polygon but fails to save
Summary: Smooth transition allowed on polygon but fails to save
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
6.1.6.3 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-20 11:03 UTC by Gerry Garvey
Modified: 2020-04-17 15:57 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Error message (140.52 KB, image/png)
2019-10-20 15:29 UTC, Gerry Garvey
Details
Sample file saved just before applying smooth point (8.01 KB, application/vnd.oasis.opendocument.graphics)
2019-10-25 09:40 UTC, Gerry Garvey
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gerry Garvey 2019-10-20 11:03:54 UTC
It is possible to apply a "smooth transition" to an individual point on a polygon, but then LO is unable to save the drawing (presumably because object is a mixture of curve and polygon). Converting whole object from polygon to curve first, then applying smooth transition to point, saves successfully.
Comment 1 Regina Henschel 2019-10-20 13:59:34 UTC
You have selected Version 6.1.6.3. If that is indeed your version, please try with a current version 6.3.2 or at least 6.2.8.

Please describe in more details, what happens in "LO is unable to save the drawing".
Comment 2 Gerry Garvey 2019-10-20 15:29:24 UTC
Created attachment 155163 [details]
Error message

Yes 6.1.6.3 is the only version I have.

- new drawing
- add shape
- convert shape to polygon
- enable points
- smooth transition on one point
- File Save As...

get the attached error message
Comment 3 Regina Henschel 2019-10-20 15:57:14 UTC
I cannot confirm the problem. Tested with
Version: 6.1.5.2 (x64)
Build ID: 90f8dcf33c87b3705e78202e3df5142b201bd805
CPU threads: 8; OS: Windows 10.0; UI render: default; 
Locale: en-US (en_US); Calc: CL

Version: 6.3.2.2 (x64)
Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c
CPU threads: 8; OS: Windows 10.0; UI render: default; VCL: win; 
Locale: de-DE (en_US); UI-Language: en-US
Calc: CL

Version: 6.2.5.2 (x64)
Build ID: 1ec314fa52f458adc18c4f025c545a4e8b22c159
CPU threads: 8; OS: Windows 10.0; UI render: default; VCL: win; 
Locale: de-DE (en_US); UI-Language: en-US
Calc: threaded
Comment 4 Xisco Faulí 2019-10-22 09:48:03 UTC
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
Comment 5 Gerry Garvey 2019-10-24 17:09:32 UTC
(In reply to Xisco Faulí from comment #4)
> 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

Tried same steps in safe-mode - still get same error message. Thanks.
Comment 6 Gerry Garvey 2019-10-25 09:40:04 UTC
Created attachment 155299 [details]
Sample file saved just before applying smooth point

I'm not sure this will be any use as it's taken before the issue occurs. But maybe something in it might help.
Comment 7 Julien Nabet 2020-04-05 18:36:00 UTC
On pc Debian x86-64 with master sources updated today, I don't reproduce this.

On which Linux distrib are you? 6.1.6 is quite old.
Even, if I installed this version and would reproduce this, so what? 6.1 branch is EOL and won't be fixed (at least officially).
Comment 8 Gerry Garvey 2020-04-17 15:51:09 UTC
In 6.3.5.2 the Polygon gets converted to Curve when you do this, so the issue seems to have been fixed already.
Comment 9 Xisco Faulí 2020-04-17 15:57:46 UTC
Thanks for retesting the issue with the latest version.
Setting to RESOLVED WORKSFORME since the commit fixing this issue hasn't been
identified.