Bug 159393 - Writer shutdown after a Ctrl-Enter for new page in document
Summary: Writer shutdown after a Ctrl-Enter for new page in document
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.5.7.1 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-01-26 19:39 UTC by Roland Faulhaber
Modified: 2024-11-07 03:15 UTC (History)
3 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 Roland Faulhaber 2024-01-26 19:39:15 UTC
Description:
While working in a Writer document and attempting to press Ctrl-Enter to create a page break, Libre Office presents a screen stating it encountered an error and would I like to Debug or Close Program. This happens regularly. I will try to use a menu option next time to see if the problem continues.

Steps to Reproduce:
1.Create document using Writer
2.Type some dummy words. I happen to be one line below a Bulleted list
3.Press Ctrl-Enter to create page break. My assumption is Writer has same Microsoft functionality

Actual Results:
On my other monitor I receive a message box stating Libre Office has encountered an error. I am to choose whether to Debug or Close Program.  Libre Office does not respond to me trying to click on Save or other menu options - total lockup.

Expected Results:
New page with items below where my cursor is located to be moved to the top of a new page.


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.5.7.1 (X86_64) / LibreOffice Community
Build ID: 47eb0cf7efbacdee9b19ae25d6752381ede23126
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded
Comment 1 BogdanB 2024-01-26 20:57:42 UTC
When trying to bibisect another bug but with a similar task (Ctrl+Enter), I notice the same behavior.

In my case on linux, with 24.2
linux-64-24.2

See: https://bugs.documentfoundation.org/show_bug.cgi?id=159294 comment 2.
Comment 2 Telesto 2024-01-30 19:03:57 UTC
Something to try:
Tools -> Options -> View -> Check Force Skia Software rendering. Does the crash still occur?


Another question: Does also happen in single monitor setup?
Comment 3 Stéphane Guillou (stragu) 2024-02-01 02:35:13 UTC
If the issue is related to Skia, it reminds me of bug 149527 - which seems to be fixed in recent versions.
In any case, please test LO 7.6 and let us know (and also test Skia Raster like Telesto recommended).
Thank you.
Comment 4 John 2024-04-09 01:22:54 UTC
This issue does not seem to be present in this version of LibreOffice Writer:
Version: 24.2.0.3 (X86_64) / LibreOffice Community
Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1
CPU threads: 24; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_DE); UI: en-US
Calc: CL threaded

I was not able to reproduce the bugs and page breaks were inserted as expected.
Comment 5 QA Administrators 2024-10-07 03:17:20 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2024-11-07 03:15:20 UTC
Dear Roland Faulhaber,

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