Bug 155423 - crashing
Summary: crashing
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-05-20 17:50 UTC by Gerald Sherman
Modified: 2023-12-19 03:11 UTC (History)
2 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 Gerald Sherman 2023-05-20 17:50:26 UTC
Libre Office crashes on Windows 11 Pro.  Version is the latest stable version.  The program locks up and does not respond to any input.  I can only clear it by shutting Office down & restarting it.  I usually use Calc & Writer.
Comment 1 m_a_riosv 2023-05-20 22:51:59 UTC
Please test with a clean profile, Menu/Help/Restart in Safe Mode
Comment 2 Julien Nabet 2023-05-21 07:57:28 UTC
You can try this:
https://wiki.documentfoundation.org/QA/FirstSteps.

Also, if it fails with LO 7.4.7, please try LO 7.5.3.
Indeed there won't be any new 7.4 version (see https://wiki.documentfoundation.org/ReleasePlan/7.4) so if the situation requires a fix, it won't be on 7.4 branch but only from 7.5 branch.
Comment 3 QA Administrators 2023-11-18 03:13:08 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2023-12-19 03:11:34 UTC
Dear Gerald Sherman,

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