Bug 141388 - Crash in: libswlo.so
Summary: Crash in: libswlo.so
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
Hardware: All All
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2021-03-31 13:49 UTC by j.a.swami
Modified: 2022-01-08 03:51 UTC (History)
1 user (show)

See Also:
Crash report or crash signature: ["libswlo.so"]

Writer file that crashes (16.25 KB, application/vnd.oasis.opendocument.text)
2021-03-31 14:50 UTC, j.a.swami
LO crash at 3:00 minutes, brought on by pressing backspace key. (3.65 MB, video/webm)
2021-04-01 15:24 UTC, j.a.swami
LO crash at 01:05 minutes, after pressing enter or backspace. (2.35 MB, video/webm)
2021-04-01 15:42 UTC, j.a.swami

Note You need to log in before you can comment on or make changes to this bug.
Description j.a.swami 2021-03-31 13:49:19 UTC
This bug was filed from the crash reporting server and is br-c07b04f6-e49f-44f4-bace-8843b4a9aae5.
With outline content visibility enabled, I placed my cursor to the left of a subhead that had text beneath it and hit "enter." LO crashed. 

In case it's relevant and not reported, I'm running under gnome-session (Gnome 3.36.8) with Wayland.

I've had frequent LO crashes similar to this one, sometimes after deleting text, sometimes after hitting "enter" after a subhead, and so on.
Comment 1 Xisco Faulí 2021-03-31 14:20:11 UTC
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. 
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
(Please note that the attachment will be public, remove any sensitive information before attaching it. 
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Comment 2 j.a.swami 2021-03-31 14:50:47 UTC
Created attachment 170865 [details]
Writer file that crashes

Uploaded document that crashes.
Comment 3 Xisco Faulí 2021-04-01 08:22:54 UTC
Thanks for providing the document.
Could you please explain the steps to reproduce the crash? where do you place the cursor when you press enter ?
Comment 4 j.a.swami 2021-04-01 15:24:59 UTC
Created attachment 170900 [details]
LO crash at 3:00 minutes, brought on by pressing backspace key.

I think the crashes may vary, occurring sometimes after I press <backspace>, sometimes after <enter>. 

In any case, here's a live one, at 3:00 minutes, brought on by my having pressed <backspace>.
Comment 5 j.a.swami 2021-04-01 15:42:11 UTC
Created attachment 170901 [details]
LO crash at 01:05 minutes, after pressing enter or backspace.

Here's another live one. I don't recall which key-press brought it on--<backspace> or <enter>.
Comment 6 QA Administrators 2021-04-02 03:48:17 UTC Comment hidden (obsolete)
Comment 7 j.a.swami 2021-04-16 13:57:09 UTC
I've several times found this crash occurring when I delete a blank line (using <backspace> or <delete>).
Comment 8 Timur 2021-06-10 10:53:27 UTC
This bug stays Unconfirmed because it needs exact steps.
Please try to find. 
I can't please mark duplicate of bug 142733, that's also a delete with Outline, but with steps. Please test that one and set New if you reproduce.
Comment 9 QA Administrators 2021-12-08 04:36:24 UTC Comment hidden (obsolete)
Comment 10 QA Administrators 2022-01-08 03:51:08 UTC
Dear j.a.swami,

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