Bug 121643 - Pressing on the "Reset" button when the focus is on the "Type" drop-down field causes LibreOffice to crash, on Properties - Custom Properties
Summary: Pressing on the "Reset" button when the focus is on the "Type" drop-down fiel...
Status: RESOLVED DUPLICATE of bug 121644
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-22 22:00 UTC by Liad Skiva
Modified: 2018-11-22 23:11 UTC (History)
1 user (show)

See Also:
Crash report or crash signature: ["ListBox::GetSelectedEntryPos(long)"]

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 Liad Skiva 2018-11-22 22:00:02 UTC 
Description:
Unsaved changes are not lost after crash

Steps to Reproduce:
1. Go to File->Properties.
2. Go to the "Custom Properties" tab.
3. Press the "Add Property" button.
4. Press "Tab" until the focus is on the "Type" drop-down field of that property.
5. Press the "Reset" button.

Actual Results:
When pressing the "Reset" button the property is being deleted and LibreOffice crashes.

Expected Results:
When pressing the "Reset" button the property should just get deleted without anything else happening.


Reproducible: Always


User Profile Reset: No



Additional Info:
- Bringing the focus to the "Type" field of an already existing (not new) property causes the same problem.

LibreOffice about info:
Version: 6.1.3.2 (x64)
Build ID: 86daf60bf00efa86ad547e59e09d6bb77c699acb
CPU threads: 4; OS: Windows 10.0; UI render: default; 
Locale: en-US (en_US); Calc: CL
Comment 1 Xisco Faulí 2018-11-22 23:11:55 UTC 
Reproduced in

LibreOffice 3.3.0 
OOO330m19 (Build:6)
tag libreoffice-3.3.0.4

Since the crash signature is the same as in bug 121644, I believe the root cause is the same.
Anyway, thank you very much for reporting it!!

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