Bug 963502 - Droid sans fonts not applied in GTK applications
Summary: Droid sans fonts not applied in GTK applications
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xsettings-kde
Version: 18
Hardware: All
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: 2013-05-16 01:35 UTC by cobra.the.joker
Modified: 2014-11-13 08:55 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 21:23:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description cobra.the.joker 2013-05-16 01:35:14 UTC
Description of problem:

In the systemsettings panel in kde , the droid sans font isnt applied to the GTK+ applications , although most of the other fonts are applied instantly .

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


How reproducible:

Always 

Steps to Reproduce:

1.Just select droid sans from system settings 
  
Actual results:

GTK+ applications fonts arent changed to droid sans 


Expected results:

GTK+ applications fonts should be changed to droid sans 

Additional info:

The droid sans font have [unknown] , [monotype] stuff besides it which somehow in later or earlier releases wasnt there and it worked

Comment 1 nucleo 2013-05-21 16:56:22 UTC
"Droid Sans" font from old package http://koji.fedoraproject.org/koji/buildinfo?buildID=78920 applied fine in gtk applications, no there [unknown] and [monotype] in fonts names.

"Droid Sans [unknown]" and "Droid Sans [monotype]" looks ad "Sans Serif" in gtk applications.

Comment 2 Fedora End Of Life 2013-12-21 13:33:38 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 3 Fedora End Of Life 2014-02-05 21:23:45 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.

Comment 4 carasin 2014-02-23 08:01:50 UTC
The problem is still actual for Fedora 19, 20 and perhaps rawhide.


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