Bug 1116145 - Background of message composition pane is black on GTK+ 3.13.3
Summary: Background of message composition pane is black on GTK+ 3.13.3
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: rawhide
Hardware: All
OS: All
unspecified
high
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-03 21:02 UTC by Adam Williamson
Modified: 2014-07-15 14:50 UTC (History)
5 users (show)

Fixed In Version: gtkhtml3-4.8.3
Clone Of:
Environment:
Last Closed: 2014-07-07 13:26:07 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screenshot illustrating the issue (60.48 KB, image/png)
2014-07-03 21:03 UTC, Adam Williamson
no flags Details


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 732499 0 None None None Never

Description Adam Williamson 2014-07-03 21:02:56 UTC
Filing in RHBZ is this is to do with Evo 3.12.3 on GTK+ 3.13.3, which is a slightly unusual configuration probably most commonly found in Rawhide.

So, yeah, in current Rawhide, with evolution-3.12.3-3.fc21.x86_64 and gtk3-3.13.3-2.fc21.x86_64 , there's still a theming/color issue remaining in Evolution: when composing a message (either a new message or a reply), the pane that contains the new message text has a black background.

I know someone is aware of this issue at some level, but wanted to make sure there was a bug report to track progress and make sure the fix makes it down to Rawhide.

Comment 1 Adam Williamson 2014-07-03 21:03:24 UTC
Created attachment 914589 [details]
screenshot illustrating the issue

Comment 2 Milan Crha 2014-07-07 13:26:07 UTC
Thanks for a bug report. This is for gtkhtml3, which was fixed only recently and will reach rawhide the next week, when the release will be done. It as reported as [1] upstream.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=732499

Comment 3 Adam Williamson 2014-07-15 14:50:57 UTC
Confirmed working when I woke up today, thanks.


Note You need to log in before you can comment on or make changes to this bug.