1. Open attached document
Observed behaviour: Wordart is imported as white
Build ID: 757a60d01dd152aadab2ba3c8224252481ce8a88
CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk3; Layout
Locale: ca-ES (ca_ES.UTF-8); Calc: group
but not in
Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e
Created attachment 129066 [details]
Version: 22.214.171.124.alpha0+ (x64)
Build ID: 7aa2b5a041df8e71a435cccbc79ee13799ec9138
CPU Threads: 4; OS Version: Windows 6.19; UI Render: GL; Layout Engine: new;
TinderBox: Win-x86_64@62-TDF, Branch:MASTER, Time: 2016-11-24_11:40:27
Locale: nl-NL (nl_NL); Calc: CL
but not in:
Build ID: 5e3e00a007d9b3b6efb6797a8b8e57b51ab1f737
CPU Threads: 4; OS Version: Windows 6.2; UI Render: default;
Locale: nl-NL (nl_NL)
Note: text-layout is wrong
Yes, looks okay in 126.96.36.199, but white in 188.8.131.52 / Windows 7.
Adjusting version field.
This seems to have begun at the below commit.
Adding Cc: to Matus Uzak; Could you possibly take a look at this one? Thanks
author Matus Uzak <email@example.com> 2016-03-07 11:04:01 (GMT)
committer Katarina Behrens <Katarina.Behrens@cib.de> 2016-03-10 10:20:46 (GMT)
commit 6802f760a69f3b1f203d70399f0d73764f9159d5 (patch)
parent a076feda8e6541ce611866e3f20f65648ec2b50b (diff)
tdf#89927: PPTX import: Incorrect inheritance of text run fill properties
Make use of FillProperties in TextCharacterProperties. DrawingML:
Fill related elements in Text Run Properties are in sync with Table
Cell Properties and all of Line Properties.
51f9111c56a3f0fb531f0ae7ee718a10d6339df5 is the first bad commit
Author: Norbert Thiebaud <firstname.lastname@example.org>
Date: Fri Mar 18 14:03:17 2016 -0700
git bisect log
# bad: [6380ca07b05f68dedcaa379302cfe1fa478571c4] source sha:60b74fe1775e647545d2da1fcc58a4c63ec18aa5
# good: [1f670510f08cb800cbae2a1dd6ea70d3542e4721] source sha:49c2b9808df8a6b197dec666dfc0cda6321a4306
git bisect start 'origin/master' 'oldest'
# good: [38f37b8ec1a2d199bb957cfd2581df7d1b273b74] source sha:c0da1080b61a1d51654fc34fdaeba373226065ff
git bisect good 38f37b8ec1a2d199bb957cfd2581df7d1b273b74
# bad: [11ae494d8c566f23e0ef84ba0cc25fb1388b67f7] source sha:470cfa9860232ab70e017e6084d80f80d469555c
git bisect bad 11ae494d8c566f23e0ef84ba0cc25fb1388b67f7
# bad: [d247d25062e6cc4afccdc3c4be84a2b98523b36a] source sha:150c1dcab007dd8acc1551791f42eef692f9e531
git bisect bad d247d25062e6cc4afccdc3c4be84a2b98523b36a
# good: [dc23450cfb87b61fcbd905a7079d8a0d32759e6b] source sha:5c1234eac2b9f3a3ea032e4828a15bedca6b9ebe
git bisect good dc23450cfb87b61fcbd905a7079d8a0d32759e6b
# bad: [3c06b49a11643ee6e22d8184f65dcc129ceb586d] source sha:42d6a165b053ebdccbd6979eb849b1abe305d2ba
git bisect bad 3c06b49a11643ee6e22d8184f65dcc129ceb586d
# good: [ae20ff1c2de6ecec64f34a839a82f6dfd00f5ac5] source sha:70fca3e901e41fa52589eb3f06e6839c4a8582de
git bisect good ae20ff1c2de6ecec64f34a839a82f6dfd00f5ac5
# bad: [6d7499abfffe460a5f7013564141cc51dbc39e87] source sha:127fbac23afa1fc94dd7f8aae390e1ff55ed5d64
git bisect bad 6d7499abfffe460a5f7013564141cc51dbc39e87
# bad: [ead1e6d2162bca106369cec08b6bac34610626dc] source sha:a3fcf5a3b8ea26c289b12216d7f8fdb7e07814b7
git bisect bad ead1e6d2162bca106369cec08b6bac34610626dc
# good: [76ec908f8aa5824caac5af760b0b866e1bb0720b] source sha:3d82b08bcea45408b1998934558e2e28721125df
git bisect good 76ec908f8aa5824caac5af760b0b866e1bb0720b
# bad: [d644a4e4923dfa3b358bbb64eeb77baab7defeb4] source sha:51d1fca2041ba4478c5abae59b1ed4fee37ea1ee
git bisect bad d644a4e4923dfa3b358bbb64eeb77baab7defeb4
# good: [e9331335bf8aa1bad7e9846fc91393f07d3648ef] source sha:5c4717416b7eeaf99765725785278a7437fdaf8a
git bisect good e9331335bf8aa1bad7e9846fc91393f07d3648ef
# good: [d386da0740f30ba035d5dc2e2db7552c26a5e6ec] source sha:a076feda8e6541ce611866e3f20f65648ec2b50b
git bisect good d386da0740f30ba035d5dc2e2db7552c26a5e6ec
# bad: [51f9111c56a3f0fb531f0ae7ee718a10d6339df5] source sha:6802f760a69f3b1f203d70399f0d73764f9159d5
git bisect bad 51f9111c56a3f0fb531f0ae7ee718a10d6339df5
# first bad commit: [51f9111c56a3f0fb531f0ae7ee718a10d6339df5] source sha:6802f760a69f3b1f203d70399f0d73764f9159d5
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
Still in 184.108.40.206 / Windows 7.
*** Bug 119674 has been marked as a duplicate of this bug. ***
Raised priority as this is an orphaned regression.
@Mark Hung, I thought you could be interested in this issue...