Bug 142804 - General I/O error when attempting to export soft edge rectangles to SVG
Summary: General I/O error when attempting to export soft edge rectangles to SVG
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
7.0.6.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-06-11 19:13 UTC by Bogdan Stăncescu
Modified: 2022-07-06 03:37 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Silly sample (it's just a default rectangle) (8.13 KB, application/vnd.oasis.opendocument.graphics)
2021-06-11 19:14 UTC, Bogdan Stăncescu
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bogdan Stăncescu 2021-06-11 19:13:31 UTC
Description:
Blocking error when attempting to export an ODG as SVG if the drawing contains any rectangles with non-zero setting for Soft Edge.

Steps to Reproduce:
1. Create a rectangle shape
2. Increase its Radius property in the Soft Edge section
3. Attempt to export the file as SVG

Actual Results:
Error message.

Expected Results:
SVG file exported successfully (good), SVG file exported without rounded rectangles (bad), or error message explaining why the export failed (ugly).


Reproducible: Always


User Profile Reset: No



Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: DrawingDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: yes
Comment 1 Bogdan Stăncescu 2021-06-11 19:14:16 UTC
Created attachment 172826 [details]
Silly sample (it's just a default rectangle)
Comment 2 Julien Nabet 2021-06-11 20:24:39 UTC
On pc Debian x86-64 with master sources updated today, I don't reproduce this.
However, I can reproduce this with LO Debian package 7.0.4.2.

Could you give a try to brand new 7.1.4?
Comment 3 Bogdan Stăncescu 2021-06-11 21:07:21 UTC
To be honest, I'm not sure if I can install 7.1.x while still retaining 7.0.x; I'm actually using LibreOffice for business purposes, I don't have an isolated Windows VM to test on, and I'm a bit concerned installing a version not deemed stable. I'm open to suggestions, however.
Comment 4 QA Administrators 2021-06-12 03:50:48 UTC Comment hidden (obsolete)
Comment 5 Julien Nabet 2021-06-12 11:21:25 UTC
You can indeed wait for 7.1.5 or even 7.1.6 if you're not confident about 7.1.4 but according to https://wiki.documentfoundation.org/ReleasePlan/7.0, there won't be any newer version than 7.0.6 for 7.0 branch.

In all cases, having a recent backup of your important files is always useful (whatever the software you want to use).
Comment 6 raal 2021-12-06 20:25:31 UTC
No repro Version: 7.4.0.0.alpha0+ / LibreOffice Community
Build ID: ba7db98cca3d8516697c94ef0d6af27db9e1655e
CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: gtk3
Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US
Calc: threaded

@Bogdan, please test with newer version. Thank you.
Comment 7 QA Administrators 2022-06-05 03:41:22 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2022-07-06 03:37:16 UTC
Dear Bogdan Stăncescu,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp