Bug 137061 - There is often a bug where when I try to indent a new paragraph, no indent shows up.
Summary: There is often a bug where when I try to indent a new paragraph, no indent sh...
Status: RESOLVED DUPLICATE of bug 111932
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.4.5.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-26 19:05 UTC by Jeff Melton
Modified: 2020-10-28 15:03 UTC (History)
0 users

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 Jeff Melton 2020-09-26 19:05:12 UTC
Description:
LibreOffice is often not properly displaying indented lines at the beginning of paragraphs. This can happen either in documents from another source that I open or when I'm beginning new paragraphs in documents that I'm editing. It most often happens below headings. I know from opening the documents in other programs that the indents are there, but I am unable to make them display in LibreOffice.  

Steps to Reproduce:
1.Hit carriage return and start a new paragraph.
2.Hit tab key. 
3.Indent does not display, although I can tell from the fact that backspacing once does not take me to the previous line that LibreOffice has recorded my input.

Actual Results:
no indent displayed

Expected Results:
indent displays


Reproducible: Always


User Profile Reset: No



Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: TextDocument
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes
Comment 1 Timur 2020-09-29 09:09:41 UTC
Often in title and always in Reproducible are not the same. 
1. Did you search for existing bugs?
2. You need to attach a sample file. 
If you are not sure it's bug, you should first use http://ask.libreoffice.org/.
Comment 2 Timur 2020-10-28 15:03:50 UTC
Since there's no reply, I'll just guess this is a duplicate.

*** This bug has been marked as a duplicate of bug 111932 ***