Bug 376916 - Breeze GTK theme severely broken in Thunderbird
Summary: Breeze GTK theme severely broken in Thunderbird
Status: RESOLVED FIXED
Alias: None
Product: Breeze
Classification: Plasma
Component: gtk theme (show other bugs)
Version: 5.9.2
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: scionicspectre
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-25 14:30 UTC by Janek Bevendorff
Modified: 2019-08-10 21:54 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 5.17.0
Sentry Crash Report:

Attachments
Compose window (61.99 KB, image/png)
2017-02-25 14:30 UTC, Janek Bevendorff 		Details
Conversation, note the gray background around the white rectangle, the reply and forward buttons also used to have white background (78.21 KB, image/png)
2017-02-25 14:32 UTC, Janek Bevendorff 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Janek Bevendorff 2017-02-25 14:30:26 UTC 
Created attachment 104220 [details]
Compose window

With the latest update to 5.9.2, my Thunderbird started looking terrible.
I got solid black lines as widget separators and my conversations (Thunderbird Conversations plugin) got an ugly gray background with a white rectangle instead of a fully white background.

I attached screenshots to depict better what I mean.


Everything worked fine in 5.9.0 (and probably 5.9.1). Native GTK applications look fine. Firefox seems to work as well, but Thunderbird looks terrible.

Using Plasma 5.9.2 on Arch Linux.
Comment 1 Janek Bevendorff 2017-02-25 14:32:21 UTC 
Created attachment 104221 [details]
Conversation, note the gray background around the white rectangle, the reply and forward buttons also used to have white background
Comment 2 Antonio Rojas 2017-02-25 15:11:40 UTC 
This has nothing to do with the 5.9.2 update, this is because thunderbird is now compiled with gtk3 instead of gtk2
Comment 3 Janek Bevendorff 2017-02-25 15:29:21 UTC 
Possible that it got updated as well. Wasn't exactly sure what caused the problem. It's still an issue, though.
Comment 4 Nate Graham 2019-08-10 21:54:37 UTC 
Fixed now!