Bug 118807 - Full computer freeze in IMPRESS with creating an underlined great textline FORMATTING (GTK2)
Summary: Full computer freeze in IMPRESS with creating an underlined great textline FO...
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: GTK2
  Show dependency treegraph
Reported: 2018-07-17 16:51 UTC by Hardy Strobel
Modified: 2019-06-08 02:54 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:
Regression By:


Note You need to log in before you can comment on or make changes to this bug.
Description Hardy Strobel 2018-07-17 16:51:57 UTC
Error found - V5.4.x / V6.0.x
Any GMONE based Linux, e.g. LinuxMINT 18.x / XUBUNTU 16.04...
On CPU's INTEL i3-i7, AMD A06-10

Creating an great underlined text and leaving the text field will end in an full freeze of the complete computer.

Error solved (temp.) with:

sudo apt-get purge libreoffice-gtk libreoffice-gnome libreoffice-gtk2
sudo apt-get install libreoffice-gtk3


Steps to Reproduce:
1. create an great underline text and leave the text field

Actual Results:
full computer freeze

Expected Results:
you have to do an cold start

Reproducible: Always

User Profile Reset: Yes

Additional Info:
Comment 1 Xisco Faulí 2018-07-18 14:59:16 UTC
Thank you for reporting the bug. 
Could you please create and attach a screencast showing the steps?
There are various free screencast software available for use, including Camstudio (Windows), Jing (Mac), Simple Screen Recorder (Linux) or screencast-o-matic.com (Web).

I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested screencast is provided.
Comment 2 Hardy Strobel 2018-07-18 16:47:48 UTC
Hello Cisco Fauli,
in the video you can see the bug live.

It is not possible to use KAZAM or something else, because it is al full freeze.

First you can see the installed libreoffice-g*, after it I start the document. You can see the computer clock running.

Then I take the text (header) and underline ist. Leaving the text field the system freeze after few seconds. See the computer clock! Only a cold boot is possible.

Attachment not possible - size!

I send an WETRANSFER to your mail address xiscofauli@libreoffice.org .

Comment 3 Buovjaga 2018-09-01 13:20:49 UTC
No problem here. It does sound worrying that you are able to reproduce on multiple systems :(

Arch Linux 64-bit
Build ID: 1c59d021b3dd27c8c0255312bd0d53ad25965bab
CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk2; 
Locale: fi-FI (fi_FI.UTF-8); Calc: threaded
Built on September 1st 2018

Arch Linux 64-bit
Build ID: 6.1.0-2
CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk2; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group threaded
Comment 4 raal 2018-10-16 14:59:10 UTC
I can not confirm with Version:
Build ID: 49c87270f7176312806d1759967c247a312f0acf
CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk2;
Comment 5 Xisco Faulí 2018-10-16 15:06:39 UTC
> I send an WETRANSFER to your mail address xiscofauli@libreoffice.org .

I don't think I've received it.
Could you please send it again to me or record  the screencast with lower quality?
Comment 6 QA Administrators 2019-05-08 18:19:46 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2019-06-08 02:54:47 UTC
Dear Hardy Strobel,

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