Bug 356852

Summary: Kate's printing schema prints white on white when Breeze Dark color setting is selected
Product: [Applications] kate Reporter: David L <david.lesicnik1>
Component: kwriteAssignee: KWrite Developers <kwrite-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: lnxusr
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
URL: https://i.imgur.com/agefT3J.png
Latest Commit: Version Fixed In:

Description David L 2015-12-17 21:09:13 UTC
I set the "Color" setting in the System Settings to Breeze Dark, launched Kate, wrote some text. Then I selected to print that file to PDF (made sure that the "Printing" schema was selected) and the output was near-white on white.

If I switch the Color setting back to normal Breeze Kate prints black on white normally.

Reproducible: Always

Steps to Reproduce:
1. Switch to Breeze Dark color option
2. Write some text in Kate
3. Print said text (to PDF, for example)

Actual Results:  
The output PDF contained near-white on white text, which was completely unreadable

Expected Results:  
The output PDF cointained black on white, as defined in the "Printing" schema

Even if I switch to the Printing schema in Kate itself while Breeze Dark is enable, it's displayed black on white (as show in the URL demonstration), so it makes me think that the printing thing doesn't "respect" the Printing schema's black normal text.
Comment 1 lnxusr 2016-01-01 21:11:35 UTC
This happens to me as well since the upgrade Kubuntu 15.10 with Plasma 5.  This also happens on actual printouts to paper..  The header and footer are both the proper black print, but the body of the printout is light grey.
Comment 2 Dominik Haumann 2016-04-06 11:05:58 UTC
This is fixed with commits:
- http://commits.kde.org/ktexteditor/7d824fd0b64a316e360243ab4641e1a8a47ee88e
- http://commits.kde.org/ktexteditor/c1cba0174025fe8f2779ed30ce859b05914eba4b

See bug #344976 and bug #356110.

If you update your KDE Frameworks to, say, 5.20 or better yet upcoming 5.21, this should work as expected.

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