Bug 869479 - GTK2/3 fonts don't match the KDE4 settings
Summary: GTK2/3 fonts don't match the KDE4 settings
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kcm-gtk
Version: 18
Hardware: i686
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-24 03:46 UTC by carasin
Modified: 2014-02-05 12:41 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 12:41:33 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
KDE4 fonts settings (141.83 KB, image/png)
2012-10-24 03:46 UTC, carasin
no flags Details
KDE4 GTK+ settings (123.39 KB, image/png)
2012-10-24 03:48 UTC, carasin
no flags Details
GTK2 application example (34.35 KB, image/png)
2012-10-24 03:49 UTC, carasin
no flags Details
GTK3 application example (93.46 KB, image/png)
2012-10-24 03:50 UTC, carasin
no flags Details

Description carasin 2012-10-24 03:46:53 UTC
Created attachment 632531 [details]
KDE4 fonts settings

Description of problem:

I use Google-Droid fonts in KDE. The radiobutton "Use my KDE fonts in GTK+ applications" is set. But GTK2/3 applications use other fonts.
___________________________________

Version-Release number of selected component (if applicable):

kcm-gtk-0.5.3-11.fc18.i686
kde-baseapps-4.9.2-2.fc18.i686
___________________________________

How reproducible:

allways
___________________________________

Steps to Reproduce:

1. Set Google-Droid fonts in system settings
2. Set radiobutton "Use my KDE fonts in GTK+ applications"
___________________________________
  
Actual results:

GTK2/3 applications use other fonts
___________________________________

Expected results:

GTK2/3 applications use Google-Droid fonts
___________________________________

Additional info:

Comment 1 carasin 2012-10-24 03:48:39 UTC
Created attachment 632532 [details]
KDE4 GTK+ settings

Comment 2 carasin 2012-10-24 03:49:51 UTC
Created attachment 632533 [details]
GTK2 application example

Comment 3 carasin 2012-10-24 03:50:23 UTC
Created attachment 632534 [details]
GTK3 application example

Comment 4 Fedora End Of Life 2013-12-21 09:11:05 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2014-02-05 12:41:35 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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