Bug 127274 - Insert Field crashes LO
Summary: Insert Field crashes LO
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.3.0.4 release
Hardware: x86-64 (AMD64) macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-02 06:30 UTC by laurens
Modified: 2019-09-04 07:36 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
field bug test document (14.08 KB, application/vnd.oasis.opendocument.text)
2019-09-02 06:33 UTC, laurens
Details

Note You need to log in before you can comment on or make changes to this bug.
Description laurens 2019-09-02 06:30:45 UTC
Description:
Adding a user field crashes LO

Steps to Reproduce:
1.Open attached doc
2.Insert -> Field -> More Fields...


Actual Results:
Crash LO

Expected Results:
Add field dialog


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 6.3.0.4
Build ID: 057fc023c990d676a43019934386b85b21a9ee99
CPU threads: 12; OS: Mac OS X 10.14.6; UI render: default; VCL: osx; 
Locale: nb-NO (en_NO.UTF-8); UI-Language: en-US
Calc: threaded
Comment 1 laurens 2019-09-02 06:33:35 UTC
Created attachment 153808 [details]
field bug test document
Comment 2 Xisco Faulí 2019-09-02 06:44:51 UTC
I can't reproduce it in

Version: 6.4.0.0.alpha0+
Build ID: 41cd3e8e817c8c33a13608e62eeb06ce2c6977e4
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: x11; 
Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US
Calc: threaded

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 3 laurens 2019-09-02 07:01:27 UTC
Ok, it works (no crash) when I start in safe mode.

Still crashes with my user profile.

The user profile is only a few months old / annoying that I have to make a new one again, and set my settings (especially turning off all the auto-correct stuff) again again :/...
Comment 4 Xisco Faulí 2019-09-02 08:16:30 UTC
Do you have any ddbb registered in the current profile ?
Comment 5 laurens 2019-09-02 08:20:07 UTC
> Do you have any ddbb registered in the current profile ?

I'm afraid I don't know what that is - what field in LO-> Preferences should I look for?
Comment 6 laurens 2019-09-02 11:57:33 UTC
(In reply to laurens from comment #5)
> > Do you have any ddbb registered in the current profile ?
> 
> I'm afraid I don't know what that is - what field in LO-> Preferences should
> I look for?

For some reason Preferences "Use a Java runtime environment" is checked and every time I uncheck it, it comes back. Unsure if this is related.

Been through LO bugs this week after 6.3.0.4 has the left and right scrolling reversed (https://bugs.documentfoundation.org/show_bug.cgi?id=126680 - waiting for fix release)
Comment 7 QA Administrators 2019-09-03 16:13:36 UTC Comment hidden (obsolete)
Comment 8 Alex Thurgood 2019-09-04 06:03:36 UTC
(In reply to laurens from comment #6)

No crash for me either with the test document and

Version: 6.4.0.0.alpha0+
Build ID: e04b6f3c0cdacf2a3cdcd3f34bad54c8764ff1ed
CPU threads: 4; OS: Mac OS X 10.14.6; UI render: default; VCL: osx; 
Locale: fr-FR (fr_FR.UTF-8); UI-Language: en-US
Calc: threaded
Comment 9 laurens 2019-09-04 06:18:50 UTC
I've reset the user profile and can no longer reproduce myself, so I guess it was a corruption somewhere.
Comment 10 laurens 2019-09-04 06:20:08 UTC
(In reply to laurens from comment #9)
> I've reset the user profile and can no longer reproduce myself, so I guess
> it was a corruption somewhere.

NB I Also changed LO version to RC at the same time, as I needed the fixed for the scrolling bug.

Version: 6.3.1.2
Build ID: b79626edf0065ac373bd1df5c28bd630b4424273
CPU threads: 12; OS: Mac OS X 10.14.6; UI render: default; VCL: osx; 
Locale: nb-NO (en_NO.UTF-8); UI-Language: en-US
Calc: threaded
Comment 11 Alex Thurgood 2019-09-04 06:25:47 UTC
No repro either with

Version: 6.3.0.4
Build ID: 057fc023c990d676a43019934386b85b21a9ee99
Threads CPU : 4; OS : Mac OS X 10.14.6; UI Render : par défaut; VCL: osx; 
Locale : fr-FR (fr_FR.UTF-8); Langue IHM : fr-FR
Calc: threaded

however, the problem you are experiencing is probably due to having a registered database in your user profile. There was bug 119419, now fixed, that read all of the registered databases from the user profile and then attempted to connect to each one in turn when the user tried inserting a field into a document via the Insert Fields menu. If you had deactivated the use of the JRE, then almost certainly any attempt to attempt to load a connection to a previously registered database from the user profile would have caused a crash.
Comment 12 Alex Thurgood 2019-09-04 06:29:57 UTC
And bug 119419 was linked to bug 112634, which is where the fix went in.
Comment 13 laurens 2019-09-04 06:31:22 UTC
(In reply to Alex Thurgood from comment #11)
> No repro either with
> 
> Version: 6.3.0.4
> Build ID: 057fc023c990d676a43019934386b85b21a9ee99
> Threads CPU : 4; OS : Mac OS X 10.14.6; UI Render : par défaut; VCL: osx; 
> Locale : fr-FR (fr_FR.UTF-8); Langue IHM : fr-FR
> Calc: threaded
> 
> however, the problem you are experiencing is probably due to having a
> registered database in your user profile. There was bug 119419, now fixed,
> that read all of the registered databases from the user profile and then
> attempted to connect to each one in turn when the user tried inserting a
> field into a document via the Insert Fields menu. If you had deactivated the
> use of the JRE, then almost certainly any attempt to attempt to load a
> connection to a previously registered database from the user profile would
> have caused a crash.

I wonder if that was also the reason that I could not *disable* the JRE on that Profile / LO version (it kept coming back on). I have to admit that I find the JRE setting very confusing as a non LO expert, but that is a different issue. All I know is that I try to avoid Java :)
Comment 14 Xisco Faulí 2019-09-04 07:36:04 UTC
let's close it as RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.