Bug 139659 - Fails with message "Application Error" ~ 2 seconds after starting.
Summary: Fails with message "Application Error" ~ 2 seconds after starting.
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: x86-64 (AMD64) OpenBSD
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-01-16 01:29 UTC by Edward Ahlsen-Girard
Modified: 2021-08-16 03:50 UTC (History)
1 user (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 Edward Ahlsen-Girard 2021-01-16 01:29:12 UTC
Running the OpenBSD snapshot of January 13, Libreoffice crashes immediately after displaying the splash screen. "Application Error" is the only mess displayed. Bothing is logged to /var/log/messages, and the there is no core file generated.
Comment 1 Julien Nabet 2021-01-16 09:02:55 UTC
On which LO version are you and how did you install it? (from OpenBSD repo or did you use TDF official website?)

Also, you can give a try at https://wiki.documentfoundation.org/QA/FirstSteps
Comment 2 QA Administrators 2021-07-16 03:48:57 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2021-08-16 03:50:31 UTC
Dear Edward Ahlsen-Girard,

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