Bug 69007 - FORMATTING: Shadow for characters is black on Mac OS X
Summary: FORMATTING: Shadow for characters is black on Mac OS X
Status: RESOLVED DUPLICATE of bug 67863
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.1.0.0.beta2
Hardware: Other macOS (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords: regression
Depends on:
Blocks:
 
Reported: 2013-09-06 01:30 UTC by Matthew Carlin
Modified: 2013-10-08 12:25 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
Picture of phenomenon described. (89.34 KB, image/png)
2013-09-06 01:30 UTC, Matthew Carlin 		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 Matthew Carlin 2013-09-06 01:30:26 UTC 
Created attachment 85297 [details]
Picture of phenomenon described.

Problem description: 

Since the last release the use of the "Shadow" formatting effect when using it in a text document no longer appears as a shadow as the part that should be grey is now also black. 

Steps to reproduce:
Write text
Go to character and select shadow under font effects. 

Current behavior:

Text is double black

Expected behavior:

Double should be grey. 
              
Operating System: Mac OS X
Version: 4.1.0.4 release
Comment 1 Cor Nouws 2013-09-06 07:18:40 UTC 
Hi Matthew,

I do not see the problem on Ubuntu. So prolly a problem on Mac OS X?
thanks for reporting!
Cor
Comment 2 Thomas van der Meulen [retired] 2013-09-08 07:20:49 UTC 
Thank you for your bug report, I can reproduce this bug running Version: 4.1.2.1
Build ID: bf15ac65c2167fb1ef3daf3710609d4a4c369a9
on Mac osx 10.8.4. 

It was all oké in Version 4.0.5.2 (Build ID: 5464147a081647a250913f19c0715bca595af2f)
and Version: 4.1.0.0.beta1
Build ID: 3a2c2d2417101e45fe07cfd8358acf2204a98f3

It looks like the bug is there since Version: 4.1.0.0.beta2
Build ID: 33224f4f11a05cfad2249e812fcc2975fbb61f6
Comment 3 Maxim Monastirsky 2013-10-08 12:25:31 UTC 

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