Bug 94021 - Writer EDITING: Crash on deleting text (GTK3)
Summary: Writer EDITING: Crash on deleting text (GTK3)
Status: RESOLVED DUPLICATE of bug 94013
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
5.0.1.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium critical
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-08 11:25 UTC by Tristan Miller
Modified: 2015-09-17 20:50 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Backtrace following crash (9.79 KB, text/plain)
2015-09-08 11:25 UTC, Tristan Miller
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tristan Miller 2015-09-08 11:25:50 UTC
Created attachment 118520 [details]
Backtrace following crash

When using LibreOffice Writer with the GTK3 interface, deleting text immediately after creating a selection crashes the program.

Reproducibility: Always

Steps to reproduce:

1) Launch LibreOffice using the GTK3 interface (e.g., via SAL_USE_VCLPLUGIN=gtk3) and begin a new Writer document.
2) Type some text.
3) Press the Home key to go to the beginning of the line.
4) Press Shift+End to select to the end of the line, then press Delete.

After Step 4, the following error message gets printed to the console:

** (soffice:27805): WARNING **: Unknown event notification 36

Also, if Delete was pressed immediately after pressing Shift+End, LibreOffice crashes without any further error message.  However, if I pause for a second or two between the two keystrokes, LibreOffice does not crash.

I am using LibreOffice 5.0.1.2 on openSUSE 13.2 (64-bit).

The problem does not occur with Impress or Calc.  The problem also doesn't occur if I force a different interface such as "kde4" or "gtk".
Comment 1 Maxim Monastirsky 2015-09-08 13:18:07 UTC
See my comment at Bug 94013.
Comment 2 Maxim Monastirsky 2015-09-17 20:50:05 UTC
Doesn't crash for me anymore with the patches in place. Please let us know if it will still crash in 5.0.3.

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