Bug 136201 - Base report builder: position is invalid error message crashes program.
Summary: Base report builder: position is invalid error message crashes program.
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-27 17:40 UTC by twisterddfsl83823
Modified: 2021-04-14 03:38 UTC (History)
0 users

See Also:
Crash report or crash signature: br-b7abb2a3-40f9-42ce-9158-7fdd798a4050


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description twisterddfsl83823 2020-08-27 17:40:26 UTC
This bug was filed from the crash reporting server and is br-b7abb2a3-40f9-42ce-9158-7fdd798a4050.
=========================================
Was moving labels around in the report builder, saw the "position is invalid" error message.  Instead of recovering or reverting, libreoffice crashes... (and has a zombie process that you have to manually kill in the background before you can restart.)
Comment 1 Alex Thurgood 2020-09-14 07:59:45 UTC
@OP : please provide step-by-step detailed instructions on how to reproduce with an example ODB file.
Comment 2 QA Administrators 2021-03-14 04:18:40 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2021-04-14 03:38:15 UTC
Dear twisterddfsl83823,

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