Bug 18173 - thunderbird tooltips are black on black, unless .gtkrc-2.0-kde gets renamed or applying colors to non-Qt applications gets disabled
Summary: thunderbird tooltips are black on black, unless .gtkrc-2.0-kde gets renamed o...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-10 17:53 CEST by Barry Jackson
Modified: 2020-10-05 18:16 CEST (History)
4 users (show)

See Also:
Source RPM: thunderbird-38.7.2-1.mga6
CVE:
Status comment:


Attachments
screenshot (12.81 KB, image/png)
2016-04-10 18:00 CEST, Barry Jackson
Details

Description Barry Jackson 2016-04-10 17:53:02 CEST
All tooltips in Thunderbird are black (guessing that there is black text on a black background).
Comment 1 Barry Jackson 2016-04-10 18:00:29 CEST
Created attachment 7648 [details]
screenshot
Comment 2 Barry Jackson 2016-04-10 18:27:15 CEST
I have found the culprit but not sure how to deal with it.

The effect is not there in a new user.

Re-naming the file .gtkrc-2.0-kde in my own user cures the problem, but I am not sure what else this may break.

The file contains:
#---------------------------------------------

# File created by KDE Gtk Config
# Configs for GTK2 programs 

include "/usr/share/themes/oxygen-gtk/gtk-2.0/gtkrc"
style "user-font" 
{
	font_name="Sans Serif "
}
widget_class "*" style "user-font"
gtk-font-name="Sans Serif  9"
gtk-theme-name="oxygen-gtk"
gtk-icon-theme-name="oxygen"
gtk-fallback-icon-theme="hicolor"
gtk-toolbar-style=GTK_TOOLBAR_ICONS
gtk-menu-images=0
gtk-button-images=0

#-------------------------------------------

I use the same /home/me folder for Mga5 and Mga6 and it was used previously for earlier versions.
Comment 3 Marja Van Waes 2016-04-10 23:59:30 CEST
(In reply to Barry Jackson from comment #2)
> I have found the culprit but not sure how to deal with it.
> 
> The effect is not there in a new user.
> 
> Re-naming the file .gtkrc-2.0-kde in my own user cures the problem, but I am
> not sure what else this may break.
> 

Thanks,  Barry. I have the issue, too, also using an "old" /home, but kept forgetting to check whether the issue exists only in Plasma5, or in XFCE (my fallback), too... so I kept postponing to file a bug report. I hadn't thought of testing with a new user.

I don't have a .gtkrc-2.0-kde, though, but do have 2 gtkrc-2.0 files

[marja@cldrn_64 ~]$ find | grep gtkrc-2.0
./.kde4/share/config/gtkrc-2.0
./.config/gtkrc-2.0
[marja@cldrn_64 ~]$ 

At the top of those files it says:

# If you do not want KDE to override your GTK settings, select
# Appearance -> Colors in the System Settings and disable the checkbox
# "Apply colors to non-KDE4 applications"

That checkbox did not exist, but there was a similar checkbox for applying colors to non-Qt applications. Unchecking it fixed the problem for me: the tooltip texts are white on black now

Summary: thunderbird tooltips are black on black => thunderbird tooltips are black on black, unless .gtkrc-2.0-kde gets renamed or applying colors to non-Qt applications gets disabled
Source RPM: (none) => thunderbird-38.7.2-1.mga6
CC: (none) => doktor5000, marja11
Assignee: bugsquad => mageia

Samuel Verschelde 2016-08-25 16:24:50 CEST

Assignee: mageia => kde

Comment 4 Nicolas Lécureuil 2017-03-18 01:43:37 CET
is it still valid with current cauldron ?

CC: (none) => mageia

Comment 5 Barry Jackson 2017-03-18 16:33:27 CET
Can't easily test now as I run thunderbird over ssh on a Mga5 server.
I suppose it would require a working Thunderbird install on Mga5 updated to Mga6 to test and I won't be updating my server any time soon ;)
Comment 6 Aurelien Oudelet 2020-10-05 18:16:14 CEST
Can't reproduce this inside M7, Cauldron and even a M7 32 bits on a VM. 

We are sorry, but we no longer maintains this version of Mageia. Please upgrade to the latest version and reopen this bug against that version if this bug exists there.
As a result we are setting this bug to RESOLVED:OLD

Resolution: (none) => OLD
Status: NEW => RESOLVED
CC: (none) => ouaurelien


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