Bug 136898 - Crash when after changing the font in the chart, and changing the palette and setting the color
Summary: Crash when after changing the font in the chart, and changing the palette and...
Status: RESOLVED DUPLICATE of bug 133630
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
7.0.1.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, haveBacktrace, regression
Depends on:
Blocks:
 
Reported: 2020-09-20 05:10 UTC by Jun Nogata
Modified: 2020-11-10 10:31 UTC (History)
2 users (show)

See Also:
Crash report or crash signature: https://crashreport.libreoffice.org/stats/crash_details/528a3d06-d8a8-4e49-a2d9-bd8949280bd8

Attachments
Reproduction screencast (8.71 MB, video/mp4)
2020-09-20 05:11 UTC, Jun Nogata 		Details
ScreenCast On Sawakaze Env (1.36 MB, video/x-matroska)
2020-09-20 23:59 UTC, sawakaze 		Details
backtrace (7.83 KB, text/plain)
2020-09-24 15:55 UTC, Terrence Enger 		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 Jun Nogata 2020-09-20 05:10:22 UTC 
Description:
Crash when setting the chart area color by changing the color palette after setting the chart Y axis font.

Steps to Reproduce:
1. Launch the Impress.
2. Push [Insert Chart] button on tool bar.
3. Select "Y Axis" in [Select Chart Element] list and Push [Format Selection] button.
4. Change "Font Family" at Western Text Font in [Font] tab then [OK] button.
5. Select "Data series 'Column 1'" in [Select Chart Element] list and Push [Format Selection] button.
6. Select Palette at "Colors" in [Area] tab.
7. Select Colors then [OK] button.


Actual Results:
Impress Crashes.

Expected Results:
The chart area color is Changed.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Version: 7.0.1.2
Build ID: 7cbcfc562f6eb6708b5ff7d7397325de9e764452
CPU threads: 8; OS: Linux 5.8; UI render: default; VCL: gtk3
Locale: en-US (C); UI: en-US
Calc: threaded
Comment 1 Jun Nogata 2020-09-20 05:11:41 UTC 
Created attachment 165695 [details]
Reproduction screencast
Comment 2 sawakaze 2020-09-20 23:53:48 UTC 
I could reproduce it.

Version: 7.1.0.0.alpha0+
Build ID: 6d7a72ab1c044f7e1f30f7c4133dafdb214dfcbf
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3
Locale: en-US (C); UI: en-US
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2020-09-19_14:41:13
Calc: threaded


-------

I could not reproduce it.

Version: 6.4.6.1
Build ID: 985dd72ca280d5c6da2e9f90f7ff9286cafe7ff8
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: en-US (C); UI-Language: en-US
Calc: threaded
Comment 3 sawakaze 2020-09-20 23:59:54 UTC 
Created attachment 165701 [details]
ScreenCast On Sawakaze Env

ScreenCast On sawakaze env.

crash report about this bug on Libreoffice 7.0 is here

https://crashreport.libreoffice.org/stats/crash_details/528a3d06-d8a8-4e49-a2d9-bd8949280bd8
Comment 4 Terrence Enger 2020-09-24 15:55:56 UTC 
Created attachment 165819 [details]
backtrace

Backtrace is of commit b42d5557 (2020-09-10) built and running on
debian-buster, configured:

    --with-vendor=Terrence Enger
    --with-jdk-home=/usr/lib/jvm/default-java
    --enable-split-debug
    --enable-gdb-index
    --enable-ld=gold
    --enable-option-checking=fatal
    #--enable-dbgutil
    --enable-debug
    --without-system-postgresql
    --without-myspell-dicts
    --with-extra-buildid
    --without-doxygen
    --with-external-tar=/home/terry/lo_hacking/git/src
    --without-package-format


Late in the terminal output (rewrapped):

    terminate called after throwing an instance of 
    'com::sun::star::lang::IndexOutOfBoundsException'


I am adding keyword have_backtrace.
Comment 5 Xisco Faulí 2020-11-10 10:31:01 UTC 
This started to crash after https://cgit.freedesktop.org/libreoffice/core/commit/?id=2d01ed9e8be543460e41e009fa992103a7c8d4c0
Closing as dupe of bug 133630

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