Bug 132573 - PARAGRAPH STYLES: Writer process sleeping, won't save or exit
Summary: PARAGRAPH STYLES: Writer process sleeping, won't save or exit
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.4.2.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Writer-Styles-Paragraph
  Show dependency treegraph
 
Reported: 2020-05-01 08:41 UTC by Luke Kendall
Modified: 2021-07-01 04:05 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 Luke Kendall 2020-05-01 08:41:05 UTC
Version: 6.4.2.2
Build ID: 4e471d8c02c9c90f512f7f9ead8875b57fcb1ec3
CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: x11; 
Locale: en-GB (en_AU.UTF-8); UI-Language: en-US
Calc: threaded

I defined a new paragraph style.
When I added its definition, I could no longer interact with Lo in the specific document I had open.
 "ps" showed the process as sleeping.

I could not open any menu, and keyboard shortcuts did not operate.

Other document windows open were still working fine.  Using one of them I chose to Exit LibreOffice (hoping a "Do you want to save" panel would appear).
Instead, all the other documents closed, but the sleeping document did not.

Attaching to its process with gdb showed:

(gdb) where
#0  0x00007ff3835135d3 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007ff373663cd7 in ?? ()
   from /opt/libreoffice6.4/program/libvclplug_genlo.so
#2  0x00007ff386732dd2 in ?? () from /opt/libreoffice6.4/program/libmergedlo.so
#3  0x00007ff386734cd5 in Application::Execute() ()
   from /opt/libreoffice6.4/program/libmergedlo.so
#4  0x00007ff3856e4e29 in ?? () from /opt/libreoffice6.4/program/libmergedlo.so
#5  0x00007ff38673bd76 in ImplSVMain() ()
   from /opt/libreoffice6.4/program/libmergedlo.so
#6  0x00007ff385706445 in soffice_main ()
   from /opt/libreoffice6.4/program/libmergedlo.so
#7  0x000000000040069b in ?? ()
#8  0x00007ff383436830 in __libc_start_main (main=0x400690, argc=3, 
    argv=0x7ffca16e3e48, init=<optimised out>, fini=<optimised out>, 
    rtld_fini=<optimised out>, stack_end=0x7ffca16e3e38)
    at ../csu/libc-start.c:291
#9  0x00000000004006cf in ?? ()

All unsaved edits were lost.
Comment 1 Luke Kendall 2020-05-01 09:01:06 UTC
So after restarting, and remaking the edits I had, I started to create the new paragraph style.
I created the new paragraph style, but found I had to edit it because it had chosen the default font.
After changing the font style in the new paragraph style, the same bug occurred.
Comment 2 Stanislaus J. Pinasthika 2020-05-25 03:09:17 UTC
Thanks for reporting the issue. Could you specify the definition of the new paragraph style that you made? 

Version: 6.4.2.2
Build ID: 1:6.4.2-0ubuntu3
CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: kf5; 
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Calc: threaded

Version: 7.0.0.0.alpha1+
Build ID: 0677d46bcc56c1f6c27b9331662990b38fd452d6
CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: kf5; 
Locale: en-US (en_US.UTF-8); UI: en-US
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2020-05-21_12:54:11
Calc: CL

Change to needinfo
Comment 3 Luke Kendall 2020-05-25 04:59:37 UTC
I can't be certain, but because I don't often create new paragraph styles (trying to keep the document structure simple), I feel confident it was probably simply creating a new style based on an existing style called "Chapter Body".
The new style would have been titled "ChapterBdy1st" and the only change was setting the First line indent from 14.4 pt to zero, and making the Next style "Chapter Body".

Chapter Body definition:
Indent Before 0, After 0, First line 14.4
Not Automatic.
Spacing Above 0, Below 0, Don't add space unchecked.
Line Spacing Single
Register-true probably checked.

Alignment Justified
Las line Start
Snap to grid checked (not sure why)
Text-to-text Alignment Automatic
Properties "Use superordinate..." (Really? I should reset to LTR)

Text flow
Hyphenation
Automatically
2 chars at line end, at line begin, 0 Max no. of consecutive hyphens
Breaks, Options, all unchecked

The change in font style I refer to would have been a change from the default, to Family Georgia, Size 10.5pt.


(I would be surprised if paragraph settings required a call for user input after changing the font style.)
Comment 4 Dieter 2020-12-01 08:14:39 UTC
Hello Luke, a new major release of LibreOffice is available since this bug was reported. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Comment 5 QA Administrators 2021-05-31 04:12:43 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2021-07-01 04:05:37 UTC
Dear Luke Kendall,

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