Bug 131893 - Document .odg crashed
Summary: Document .odg crashed
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
5.3.7.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-04 17:56 UTC by BRISSOT ALAIN
Modified: 2020-11-04 04:05 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
The document which is crashed (10.26 KB, application/vnd.oasis.opendocument.graphics)
2020-04-04 17:57 UTC, BRISSOT ALAIN
Details

Note You need to log in before you can comment on or make changes to this bug.
Description BRISSOT ALAIN 2020-04-04 17:56:40 UTC
Description:
Hello
I find myself facing an unusable odg document following the following sequence;
. 1) Beginning of writing the document with version 6.3
. 2) installation on April 1 of the package (LibreOffice_6.4.2_Win_x64.msi)
. 3) Modification of the document
. 4) Installation on April 4 of the LibreOffice_6.4.2_Win_x64_helppack_fr.msi help package
On the attached document I lost all my work and I can no longer make a single change.
As I start I manipulated the layers before installing them.
I have my work redone, but I wanted to submit this problem to the community
Thank you for your help

Steps to Reproduce:
I have once with this sequence
1) Beginning of writing the document with version 6.3
2) installation on April 1 of the package (LibreOffice_6.4.2_Win_x64.msi)
3) Modification of the document
4) Installation on April 4 of the LibreOffice_6.4.2_Win_x64_helppack_fr.msi help package

Actual Results:
Document is not exploitable

Expected Results:
Document is not exploitable


Reproducible: Always


User Profile Reset: No



Additional Info:
No other information
Comment 1 BRISSOT ALAIN 2020-04-04 17:57:50 UTC
Created attachment 159333 [details]
The document which is crashed
Comment 2 Julien Nabet 2020-04-04 18:20:24 UTC
On pc Debian x86-64 with master sources updated today or with LO Debian package 6.4.2, I don't reproduce the crash.

I got an error popup indicated "/../aaa doesn't exist" with both versions.
Comment 3 Xisco Faulí 2020-04-06 15:46:14 UTC
No crash in

Version: 7.0.0.0.alpha0+
Build ID: 6c7d51643634a4a4111f673760567e10e48467d0
CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3; 
Locale: ja-JP (en_US.UTF-8); UI-Language: en-US
Calc: threaded
Comment 4 Xisco Faulí 2020-04-06 15:47:57 UTC
Doesn't crash in

Versión: 6.4.2.2 (x86)
Id. de compilación: 4e471d8c02c9c90f512f7f9ead8875b57fcb1ec3
Subprocs. CPU: 2; SO: Windows 6.1 Service Pack 1 Build 7601; Repres. IU: predet.; VCL: win; 
Configuración regional: es-ES (es_ES); Idioma de IU: es-ES
Calc: threaded

but it breaks the layout
Comment 5 Xisco Faulí 2020-04-06 15:49:14 UTC
Same in

Versión: 5.3.7.2
Id. de compilación: 6b8ed514a9f8b44d37a1b96673cbbdd077e24059
Subprocs. CPU: 2; SO: Windows 6.1; Repres. IU: predet.; Motor de trazado: HarfBuzz; 
Configuración regional: es-ES (es_ES); Calc: group
Comment 6 Xisco Faulí 2020-04-06 15:49:30 UTC
@Alain, how was the document created ?
Comment 7 QA Administrators 2020-10-04 03:50:33 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2020-11-04 04:05:18 UTC
Dear BRISSOT ALAIN,

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