Bug 149060 - CONFIGURATION: View > Toolbars > Customize... causes crash, initiates document recovery
Summary: CONFIGURATION: View > Toolbars > Customize... causes crash, initiates documen...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.4.7.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-05-12 18:25 UTC by bugzilla.irg220228
Modified: 2023-08-20 03:18 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bugzilla.irg220228 2022-05-12 18:25:15 UTC
Description:
When trying to customize the toolbars, Libroffice Calc crashes every time, initiating the document recovery process. I am using Xubuntu 20.04.

Steps to Reproduce:
1.Select 'View' from menu;
2.Open 'Toolbars' sub-menu;
3.Select 'Customise...'

Actual Results:
'Libreoffice 6.4 Document Recovery' dialog opens. "Due to an error, Libreoffice crashed".

Documents are restored successfully by following the recovery procedure.

Expected Results:
I should be able to edit/configure the Calc toolbars.


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Version: 6.4.7.2
Build ID: 1:6.4.7-0ubuntu0.20.04.4
CPU threads: 8; OS: Linux 5.13; UI render: default; VCL: gtk3; 
Locale: en-GB (en_GB.UTF-8); UI-Language: en-US
Calc: threaded
Comment 1 Julien Nabet 2022-05-14 09:58:08 UTC
On pc Debian x86-64 with LO Debian package 7.3.3.2 + gtk3, I don't reproduce this.

6.4 version is quite old, could you give a try with a recent LO version,, 7.2.7 or brand new 7.3.3

You can find updated version in LO ppa (see https://launchpad.net/~libreoffice/+archive/ubuntu/ppa).
You may also upgrade Xubuntu to 22.04 LTS which will automatically bring newer LO version and gtk libs.
Comment 2 bugzilla.irg220228 2022-05-16 08:40:44 UTC
(In reply to Julien Nabet from comment #1)
> On pc Debian x86-64 with LO Debian package 7.3.3.2 + gtk3, I don't reproduce
> this.
> 
> 6.4 version is quite old, could you give a try with a recent LO version,,
> 7.2.7 or brand new 7.3.3
> 
> You can find updated version in LO ppa (see
> https://launchpad.net/~libreoffice/+archive/ubuntu/ppa).
> You may also upgrade Xubuntu to 22.04 LTS which will automatically bring
> newer LO version and gtk libs.


Thanks Julien,

I've upgraded to 7.2.7: 

Version: 7.2.7.2 / LibreOffice Community
Build ID: 8d71d29d553c0f7dcbfa38fbfda25ee34cce99a2
CPU threads: 8; OS: Linux 5.13; UI render: default; VCL: gtk3
Locale: en-GB (en_GB.UTF-8); UI: en-US
Calc: threaded


Calc now takes a good while longer to crash, instead hanging and making me wait for the, "This window might be busy and is not responding. Do you want to terminate the application?" window to appear.

The same crash occurs on every LO product whenever I try to use the 'Customize' option. Trying safe-mode results in LO trying to open any document or templates as a chart.

Unfortunately I'm stuck with the Xubuntu 20.04 LTS for now due to MySQL not yet having been packaged for 22.04.
Comment 3 Roman Kuznetsov 2022-05-27 14:47:37 UTC
No problem in

Version: 7.4.0.0.alpha1+ (x64) / LibreOffice Community
Build ID: b6266207b55a7633dc82b02142215757512adfb7
CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Vulkan; VCL: win
Locale: ru-RU (ru_RU); UI: en-US
Calc: threaded

Linux only?
Comment 4 Xisco Faulí 2022-06-24 08:46:17 UTC
Does it crash if you launch LibreOffice from commandline with 'SAL_USE_VCLPLUGIN=gen soffice' ?
Comment 5 bugzilla.irg220228 2022-06-25 12:26:58 UTC
(In reply to Roman Kuznetsov from comment #3)
> No problem in
> 
> Version: 7.4.0.0.alpha1+ (x64) / LibreOffice Community
> Build ID: b6266207b55a7633dc82b02142215757512adfb7
> CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Vulkan; VCL:
> win
> Locale: ru-RU (ru_RU); UI: en-US
> Calc: threaded
> 
> Linux only?

Yes, in as far as I don't use LO on anything other than Linux.
Comment 6 bugzilla.irg220228 2022-06-25 12:31:29 UTC
(In reply to Xisco Faulí from comment #4)
> Does it crash if you launch LibreOffice from commandline with
> 'SAL_USE_VCLPLUGIN=gen soffice' ?

This returns, 'SAL_USE_VCLPLUGIN: command not found'.
Comment 7 Julien Nabet 2022-06-26 07:31:16 UTC
(In reply to bugzilla.irg220228 from comment #6)
> (In reply to Xisco Faulí from comment #4)
> > Does it crash if you launch LibreOffice from commandline with
> > 'SAL_USE_VCLPLUGIN=gen soffice' ?
> 
> This returns, 'SAL_USE_VCLPLUGIN: command not found'.

You must type this without simple quotes, so just:
SAL_USE_VCLPLUGIN=gen soffice

(It works for me on pc Debian x86-64)
Comment 8 Buovjaga 2023-01-20 08:12:54 UTC
NEEDINFO while we wait for test results.
Comment 9 QA Administrators 2023-07-20 03:17:47 UTC Comment hidden (obsolete)
Comment 10 QA Administrators 2023-08-20 03:18:25 UTC
Dear bugzilla.irg220228,

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