Bug 150611 - Fatal exception Signal 6 on startup after Ubuntu jammy upgrade
Summary: Fatal exception Signal 6 on startup after Ubuntu jammy upgrade
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) Linux (All)
: medium critical
Assignee: Not Assigned
Depends on:
Blocks: Crash
  Show dependency treegraph
Reported: 2022-08-25 15:50 UTC by yengst
Modified: 2023-05-01 03:19 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description yengst 2022-08-25 15:50:45 UTC
terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException'

Fatal exception: Signal 6

Steps to Reproduce:
1.launch libreoffice, even with --safe-mode

Actual Results:
will not start

Expected Results:

Reproducible: Always

User Profile Reset: No

Additional Info:
Comment 1 Julien Nabet 2022-08-25 16:14:54 UTC
just to know if it's specific to gtk3 could you try this:
- launch term/console
- type:
export SAL_USE_VCLPLUGIN=gen && soffice

If it crashes, it's not specific to gtk3.
Comment 2 yengst 2022-08-25 16:35:46 UTC
thanks for looking so quickly. Just as background I upgraded linuxmint from 20.3 to 21. There were several warnings and corrective actions related to libreoffice during the upgrade. I've since completed uninstalled and re-installed with no effect.

looks to be a general bug

% export SAL_USE_VCLPLUGIN=gen && soffice
terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException'
Unspecified Application Error
Comment 3 Julien Nabet 2022-08-25 16:40:27 UTC
Indeed it's not gtk specific.
Since you tested with  --safe, it's not profile related too.
I must recognize I'm stuck but certainly other people may help here.
Comment 4 Timur 2022-08-25 18:28:37 UTC
This seems like Ubuntu or Mint bug rather then LO. 
You say you reinstalled but didn't say how, maybe via Synaptic or some Software. 
I'd add remove LO, then add LO PPA and install 7.3.
Comment 5 Timur 2022-08-25 18:30:11 UTC
Just in case please remove LO profile folder and try again, before removing LO.
Comment 6 Stéphane Guillou (stragu) 2022-08-25 22:39:32 UTC
in addition to what Timur and Julien have said, please share with use the version information for the LibreOffice version(s) you have installed, and how you installed it.

As you can't open the GUI, maybe this can help:

apt list --installed | grep libreoffice[0-9]

And to see what's available in the repos:

apt-cache policy libreoffice
Comment 7 Alex Thurgood 2022-08-26 09:32:31 UTC
No repro for me with

Ubuntu Jammy 22.04.1 LTS
LibreOffice supplied by Canonical
UI render : default
VCL: gtk3
CPU Threads: 4
Locale: fr_FR.UTF-8

I can start any of the modules, and no crash.
Comment 8 Alex Thurgood 2022-08-26 09:34:40 UTC
Sounds like a Linux Mint specific bug to me.

I upgraded from Focal to Jammy (Ubuntu, not Mint) and see no such crashes.
Comment 9 Julien Nabet 2022-10-01 10:00:42 UTC
yengst: after a month, any update here following advices provided by last comments?
Comment 10 QA Administrators 2023-03-31 03:29:35 UTC Comment hidden (obsolete)
Comment 11 QA Administrators 2023-05-01 03:19:05 UTC
Dear yengst,

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