Bug 260943

Summary:	kwin don't obey to custom font anti-aliasing settings during login
Product:	[Plasma] kwin	Reporter:	Law, Cheuk-wing <jhnpwa>
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED UPSTREAM
Severity:	normal	CC:	cfeck, mefoster
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Law, Cheuk-wing 2010-12-22 08:40:58 UTC

Version:           unspecified (using KDE 4.5.4) 
OS:                Linux

When using a LCD monitor and disabled sub-pixel in systemsettings, kwin still use the system default font rendering settings during login.

Reproducible: Always

Steps to Reproduce:
1) Go to System Settings > Common Appearance and Behavior > Application Appearance > Fonts
2) Enable Use anti-aliasing
3) Click "Configure..."
4) Change the sub-pixel order to what you like
5) Save all changes
6) Logout and login again
7) Open a kwin decorated window and take a look on the decoration.

Actual Results:  
kwin is still using the system default settings.

Expected Results:  
kwin is running with user's settings.

Running "kwin --replace" AFTER login can temporary fix the problem.

Comment 1 Christoph Feck 2010-12-23 01:50:46 UTC

> Running "kwin --replace" AFTER login can temporary fix the problem.

This is a clear indication that the problem is not in kwin, but in the fontconfig caching. There are several bug reports about early-start applications not respecting fonts sizes or anti-aliasing settings, because fontconfig fails to update the cache in time.

Comment 2 Thomas Lübking 2012-03-17 23:22:16 UTC

Denying upstream (and likely resolved) by Christoph's reasonable comment #1
KWin doesn't do any particular font loading (and fwiw - i've never seen such)

Comment 3 Thomas Lübking 2012-03-18 13:50:40 UTC

*** Bug 179962 has been marked as a duplicate of this bug. ***