Bug 182969

Summary:	No bold condensed fonts in message list
Product:	[Unmaintained] kmail	Reporter:	Marc de Bruijn <mensch>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	0x101010, itsjustarumour.tech
Priority:	NOR
Version:	1.11.0
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Marc de Bruijn 2009-02-03 11:11:02 UTC

Version:           1.11.0 (using KDE 4.2.0)
OS:                Linux
Installed from:    Debian testing/unstable Packages

I use the DejaVu Condensed as my overall system font. In previous versions of Kmail I had the DejaVu Bold Condensed assigned to denote new or unread email. Due to another Qt related bug (150522) I always did this by editing my kmailrc file directly.

In the latest versions of Kmail, starting from the included versions in KDE 4.2, the application doesn't respect my font settings any longer. I can assign a colour to the new or unread message status or another font (bold or regular), but not the DejaVu Bold Condensed.

Comment 1 Gorka 2009-02-05 16:48:11 UTC

Confirmed exactly the same problem in kubuntu intrepid using the lastest KDE 4.2.0 build and kmail version 1.11.0.

Comment 2 itsjustarumour 2009-02-06 15:19:48 UTC

Also confirming same problem - Kubuntu Intrepid using KDE 4.2.00  and KMail 1.11.0.

Comment 3 itsjustarumour 2009-02-06 16:13:05 UTC

Following on from my comment above, it appears that all font settings for "Message List - New Messages" don't work.  I can assign a colour to the new/unread messages OK, but selecting a different font name/style/size has no effect - everything is stuck at the default "DejaVu Sans/Regular/9"

Comment 4 Jaime Torres 2009-02-07 13:20:33 UTC

Thank you for taking the time to report this bug and helping to make KDE
better. This particular bug has already been reported and is a duplicate of bug
178402, so it is being marked as such. Please look at the other bug report to
see if there is any missing information that you can provide, or to see if
there is a workaround for the bug. Additionally any further discussion
regarding the bug should occur in the other report. Feel free to continue to
report any other bugs you may find.

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