Bug 135919 - Crash on selection of subsubform during form edit
Summary: Crash on selection of subsubform during form edit
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
6.4.2.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Crash
  Show dependency treegraph
 
Reported: 2020-08-19 12:17 UTC by Leo Potjewijd
Modified: 2020-09-16 05:42 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
simple inventory database for electronic parts (56.79 KB, application/octet-stream)
2020-08-19 12:23 UTC, Leo Potjewijd
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Leo Potjewijd 2020-08-19 12:17:31 UTC
Description:
While editing a form containing a subform (with navigation bar) and a subsubform (without navigation bar) LibreOffice crashes completely upon selecting the subsubform with the message "object has already been disposed".


Steps to Reproduce:
1. open a form containing a subform and subsubform for editing
2. close the navigation toolbar
3. ctrl-click on the subform and change something
4. click on the subsubform

Actual Results:
LibreOffice crashes with a fatal error "object has already been disposed", closing all components.

Expected Results:
edit the subsubform


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
The form has a dedicated navigation bar, the subform is grouped with a dedicated navigation bar, the subsubform has no navigation bar.

Version: 6.4.4.2
Build ID: 1:6.4.4-0ubuntu0.20.04.1
CPU threads: 6; OS: Linux 5.4; UI render: default; VCL: gtk3; 
Locale: en-GB (en_US.UTF-8); UI-Language: en-US
Calc: threaded

leo@ws06$ glxinfo | grep OpenGL
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) UHD Graphics 630 (CFL GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 20.0.8
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.0.8
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 20.0.8
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:
Comment 1 Leo Potjewijd 2020-08-19 12:23:45 UTC
Created attachment 164469 [details]
simple inventory database for electronic parts

Not all intended functionality is there yet, just a framework with some data.
Comment 2 Robert Großkopf 2020-08-20 05:39:42 UTC
Tested this behavior with LO 6.4.6.2 on OpenSUSE 15.1 64bit rpm Linux. Couldn't confirm the bug.

You are using LO_Version from Ubuntu. Please try to install a version from LibreOffice directly and try to reproduce the behavior.
Comment 3 Alex Thurgood 2020-09-14 08:18:24 UTC
@Leo

I opened the Parts form, but from there wasn't really sure what your instructions meant.

What do you mean by close the Navigation Toolbar ? When opening the form in form edit mode, I see two record navigation toolbars, but you can't close any of them, only delete them.

Do you mean the Form Navigator instead ? This doesn't display for me when opening the form.

I'm a little confused. No matter what I did, I couldn't seem to get a crash.
Please be a little more precise.
Comment 4 Leo Potjewijd 2020-09-14 09:35:00 UTC
Well, the issue seems to have resolved itself with an update from anywhere in the last three weeks (was away and did all updates in bulk).

I am now running
Kernel: 5.4.0-47-generic x86_64
Desktop: Cinnamon 4.6.7
Distro: Linux Mint 20 Ulyana
base: Ubuntu 20.04 focal 
with LO 6.4.5.2, build ID 1:6.4.5-0ubuntu0.20.04.1

and could not reproduce the issue myself in the new surroundings.
On a side note: an issue with non-working cascades has also magically been resolved...

I consider the issue solved.
Comment 5 QA Administrators 2020-09-15 03:59:56 UTC Comment hidden (obsolete)