Bug 130818 - Segfault (crash) when changing alignment of text in a Text box
Summary: Segfault (crash) when changing alignment of text in a 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: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-20 18:11 UTC by Tommaso Fonda
Modified: 2020-02-20 19:51 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Backtrace (9.29 KB, text/x-log)
2020-02-20 18:11 UTC, Tommaso Fonda
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tommaso Fonda 2020-02-20 18:11:06 UTC
Description:
Affects Libreoffice Writer 6.4.0.3 on both Windows and openSUSE Tumbleweed (LO installed from the distribution's official repos).

I've captured a backtrace by following the official tutorial for Linux. There seems to be a segmentation fault. Should you need any other log, do let me know and I'll provide it.

Steps to Reproduce:
1. Open any document in Writer
2. Insert a new text box (click on Insert > Text box)
3. Drag a Text box of any size on the page
4. Release the text box so that the blinking cursor appears (i.e. you're ready to start typing in the box)
5. Click on either "Centered", "Align to right", or "Justified". Even re-clicking on the default "Align to left" will do.

Actual Results:
LibreOffice Writer crashed.

Expected Results:
The cursor should have moved to the right position, depending on the chosen alignment.


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
Version: 6.4.0.3
Build ID: 40(Build:3)
CPU threads: 4; OS: Linux 5.5; UI render: default; VCL: kf5; 
Locale: it-IT (it_IT.UTF-8); UI-Language: en-US
Calc: threaded
Comment 1 Tommaso Fonda 2020-02-20 18:11:47 UTC
Created attachment 158058 [details]
Backtrace
Comment 2 Xisco Faulí 2020-02-20 19:51:59 UTC
Thanks for reporting this issue. This is a duplicate of bug 130286

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