Bug 151163 - LO segfault at startup (SIGSEGV)
Summary: LO segfault at startup (SIGSEGV)
Status: RESOLVED DUPLICATE of bug 149100
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.3.6.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-24 12:12 UTC by vvillenave
Modified: 2022-09-25 08:17 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description vvillenave 2022-09-24 12:12:20 UTC 
Description:
LibreOffice doesn’t launch since updating to 7.3.6. Here’s a gdb backtrace:

```
Thread 1 "soffice.bin" received signal SIGSEGV, Segmentation fault.
0x00007ffff7ab62d5 in cppu::_copyConstructAnyFromData (pDestAny=pDestAny@entry=0x7fffffffd3a0, pSource=0x7fffffffd380, pType=<optimized out>, pTypeDescr=<optimized out>, acquire=0x7ffff53404d0 <com::sun::star::uno::cpp_acquire(void*)>, mapping=<optimized out>) at /usr/src/debug/libreoffice-7.3.6.2-1.fc36.x86_64/cppu/source/uno/copy.hxx:211
211                pDestAny->pData = std::malloc( pTypeDescr->nSize );
```


Steps to Reproduce:
1. Launch LO or any of its components, either from a .desktop launcher or from the terminal.

Actual Results:
Program doesn’t launch.

Expected Results:
Program should launch.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
I have two Fedora 36 x86_64 machines with nearly the exact same software stack (latest Gnome, glibc 2.35.17, kernel 5.19), but this only happens on one of these.

Possibly a duplicate of #149100?
Comment 1 Julien Nabet 2022-09-24 14:10:37 UTC 
Could you give a try at https://wiki.documentfoundation.org/QA/FirstSteps ?
Comment 2 vvillenave 2022-09-24 15:41:46 UTC 
I did reproduce it with a clean user profile; however I wasn't able to reproduce it with LO 7.4.1.
Comment 3 Julien Nabet 2022-09-25 08:17:46 UTC 
I just noticed it's same Fedora version and same bt, let's put this one as dup.

*** This bug has been marked as a duplicate of bug 149100 ***