Bug 137255 - Crash: when press Design button on sidebar , after writer document was imported from Calc. (experimental feature)
Summary: Crash: when press Design button on sidebar , after writer document was import...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.3.0.0.beta1+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: haveBacktrace
Depends on:
Blocks: Crash
  Show dependency treegraph
 
Reported: 2020-10-05 05:16 UTC by sawakaze
Modified: 2022-10-19 15:30 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
ScreenCast (1.55 MB, video/x-matroska)
2020-10-05 05:17 UTC, sawakaze
Details
backtrace from segfault (11.82 KB, text/plain)
2020-10-16 23:53 UTC, Terrence Enger
Details

Note You need to log in before you can comment on or make changes to this bug.
Description sawakaze 2020-10-05 05:16:08 UTC
Description:
On experimental feature is "Enable", after following steps, application crashed.

if my description is uncleared, please see screencast.

Steps to Reproduce:
1. Enable experimental feature to ON (Tools > Options > Advanced > Optional Features)
--> restart libreoffice.

2.open Calc
3.Insert > Object > OLE Object
--> Popup Insert OLE Object Window

4. Select Create new and Libreoffice Text 
5. Press OK
--> Insert writer document.
6. Double click inserted object
--> Change writer UI
7. press Design button on sidebar

Actual Results:
after step7, application crash
not open Design property widget

Note: after press "Manege change" button on sidebar, I confirmed application crash, too.  

Expected Results:
not crash
open property


Reproducible: Always


User Profile Reset: Yes



Additional Info:
I confirm this version

Version: 7.0.2.1
Build ID: ede20268f3f8777cdf69e0281835d320c41213fc
CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: en-US (C); UI: en-US
Calc: threaded

OS Ubuntu Mate 20.04
Comment 1 sawakaze 2020-10-05 05:17:27 UTC
Created attachment 166075 [details]
ScreenCast

if my description is uncleared on report, please see screencast.
Comment 2 Xisco Faulí 2020-10-12 17:54:08 UTC
Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ?
You can install it alongside the standard version.
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build
Comment 3 Terrence Enger 2020-10-16 23:53:35 UTC
Created attachment 166448 [details]
backtrace from segfault

I observe in sfx2::StyleManager::Search that this = 0x0; the calling
routine is sw::sidebar::(anonymous namespace)::renderPreview.

This is in a local build of commit f9050075 (2020-10-04), built and
running on debian buster, configured:

    --with-vendor=Terrence Enger
    --with-jdk-home=/usr/lib/jvm/default-java
    --enable-split-debug
    --enable-gdb-index
    --enable-ld=gold
    --enable-option-checking=fatal
    #--enable-dbgutil
    --enable-debug
    --without-system-postgresql
    --without-myspell-dicts
    --with-extra-buildid
    --without-doxygen
    --with-external-tar=/home/terry/lo_hacking/git/src
    --without-package-format

running with SAL_USE_VCLPLUGIN=gtk3.  LibreOffice also crashes with
SAL_USE_VCLPLUGIN=gen.


I am setting status NEW and keyword haveBacktrace.
Comment 4 Terrence Enger 2020-10-17 01:27:29 UTC
Working on debian-buster in various
bibisect-linux-64-... repositories, I find:

(*) 64-6.2 master: no crash

(*) 64-6.3 oldest: crash after insert object, #13 = SwXMLWriter::Write_

(*) 64-6.3 master and oldest and master in 64-6.4, 64-7.0, 64-7.1:
    crash after <Design> button, #13 = sfx2::StyleManager::Search

(*) localbuild master from 2020-10-04: crash after <Design> button,
    #14 = sfx2::StyleManager::Search

I am setting version to 6.3.0.0.beta1+.
Comment 5 QA Administrators 2022-10-18 03:34:18 UTC
Dear sawakaze,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug