Bug 130789 - Writer crashes, if I attempt to align text in the text box
Summary: Writer crashes, if I attempt to align text in the text box
Status: RESOLVED DUPLICATE of bug 130286
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.4.0.3 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-20 01:52 UTC by Dmitry
Modified: 2020-06-18 10:58 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dmitry 2020-02-20 01:52:21 UTC 
Description:
I created new document with text box and wrote some text. Then, I attempted to center it horizontally, but Writer crashed. Vertical alignment works properly.

Steps to Reproduce:
1.Create Writer document.
2.Add the text box, then type some text in.
3.Align it horizontally.

Actual Results:
Writer crash.

Expected Results:
Writer should just align text and continue working.


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Версия: 6.4.0.3 (x64)
ID сборки: b0a288ab3d2d4774cb44b62f04d5d28733ac6df8
Потоков ЦП: 2; ОС: Windows 10.0 Build 17763; Отрисовка ИП: GL; VCL: win; 
Локаль: ru-RU (ru_RU); Язык интерфейса: ru-RU
Calc: threaded

Memory dump is 02614dce-33bf-4f96-9848-d98ea9a250e5
Comment 1 Dieter 2020-02-20 08:11:23 UTC 
Dmitry, there is indeed a problem with textboxes in LO 6.4.0.3 But it should be fixed in 6.4.1.1 (see bug 130286). 

So could you lease test with 6.4.1.1 from https://www.libreoffice.org/download/download/?type=win-x86_64&version=6.4.1 to be sure, that it is not a duplicate of bug 130286?

=> NEEDINFO
Comment 2 Maxim Monastirsky 2020-02-20 11:13:38 UTC 
The crash was fixed in Bug 130286 (towards 6.4.1), but that didn't make alignment actually work. There's a follow-up Bug 130482 that fixes the problem completely (6.4.2 only for now).

*** This bug has been marked as a duplicate of bug 130286 ***
Comment 3 Dmitry 2020-02-20 17:31:03 UTC 
Thanks.