Bug 78091

Summary:	"Apply colors to non-KDE applications" doesn't work with AbiWord 2.0.5
Product:	[Unmaintained] kcontrol	Reporter:	Mikey Cooper <mikey>
Component:	kcmcolors	Assignee:	Unassigned bugs <unassigned-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	RedHat Enterprise Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Mikey Cooper 2004-03-20 20:17:37 UTC

Version:            (using KDE KDE 3.2.1)
Installed from:    RedHat RPMs
OS:          Linux

If using the "Apply colors to non-KDE applications" option under kcontrol, KDE applies the "Standard Background" color to AbiWord 2.0.5 as the color for highlighted text.  As a result, with Plastik, Keramik or any other theme that uses a white "Standard Background", Abiword doesn't appear to highlight selected text (it's highlighting it in white).  This can be confirmed by changing the "Standard Background" color to blue and restarting AbiWord, in which case all selected text will have a blue background.

Comment 1 missive 2004-03-23 22:10:33 UTC

I see this also with AbiWord-2.0.5, FreeBSD-4.9-STABLE,
and KDE-3.2.1

Comment 2 jost ammon 2004-05-31 00:01:37 UTC

The same is true for mdk 10.0 offcial / kde 3.2 / abiword 2.0.3

Comment 3 Dominique Devriese 2004-06-24 13:54:06 UTC

Confirmed with abiword 2.0.7+cvs.2004.05.05-1 and libgtk-2.0-0 2.4.3-1 both from current Debian unstable.

This is also reported in the following Debian bug report:
http://bugs.debian.org/249999

thanks
domi

Comment 4 Waldo Bastian 2004-06-24 14:51:52 UTC

The file ~/.gtkrc-kde contains the color information set by KDE.

Can you find out which entry causes the highlighting problems?

I would expect abiword to use text[SELECTED] in combination with base[SELECTED] for selected text.

Comment 5 Waldo Bastian 2004-06-25 13:12:44 UTC

It seems to use base[ACTIVE] in combination with text[ACTIVE]

And this bugreport is a duplicate of http://bugs.kde.org/show_bug.cgi?id=79464

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