Bug 136020 - Crash when try to move data label in a chart with arrow key
Summary: Crash when try to move data label in a chart with arrow key
Status: RESOLVED DUPLICATE of bug 136430
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Chart (show other bugs)
Version:
(earliest affected)
7.1.0.0.alpha0+
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-22 20:22 UTC by Regina Henschel
Modified: 2020-09-08 03:59 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
File to reproduce crash (16.07 KB, application/vnd.oasis.opendocument.presentation)
2020-08-22 20:22 UTC, Regina Henschel 		Details
Error message (22.72 KB, image/png)
2020-08-22 20:32 UTC, Regina Henschel 		Details
Call Stack VS2019 (1.01 KB, text/plain)
2020-08-22 20:34 UTC, Regina Henschel 		Details
View All 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 Regina Henschel 2020-08-22 20:22:41 UTC 
Created attachment 164571 [details]
File to reproduce crash

Open attached file. It has a chart with two data labels. Activate the chart. Activate the data label "Tom" so that it has move handles. Use key "arrow left" to move it => Crash.

I have used Version: 7.0.0.2 (x64)
Build ID: c01aa64b6c3d89ebe5fe69c28c7adb24eb85249c
CPU threads: 8; OS: Windows 10.0 Build 18362; UI render: Skia/Raster; VCL: win
Locale: de-DE (en_US); UI: en-US
Calc: CL

To be able to move objects with arrow keys is necessary for accessibility. So disabling arrow key to solve the crash is no solution.
Comment 1 Regina Henschel 2020-08-22 20:32:39 UTC 
Created attachment 164572 [details]
Error message
Comment 2 Regina Henschel 2020-08-22 20:34:50 UTC 
Created attachment 164573 [details]
Call Stack VS2019

Call Stack after clicking OK button in the error message.
Comment 3 Xisco Faulí 2020-09-07 08:49:16 UTC 
it looks like a duplicate of bug 136430

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