Bug 467339 - xmode2 says "couldn't load font" and exits
xmode2 says "couldn't load font" and exits
Product: Fedora
Classification: Fedora
Component: lirc (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jarod Wilson
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-10-16 17:54 EDT by Till Maas
Modified: 2010-01-22 15:52 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-12-18 01:35:36 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Till Maas 2008-10-16 17:54:58 EDT
Description of problem:
I booted F10 Snap1 i686 Live and installed lirc. I followed
to setup lircd and it somehow got started. I then tried to run xmode2 and it showed a window for a very short time (less than a second) and printed "couldn't load font". Then it exited.

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

How reproducible:

Steps to Reproduce:
1. run F10 Snap1 i686 Live
2. install lirc and get lircd to run
3. run xmode2
Actual results:
prints "couldn't load font"

Expected results:
I guess it should show what my ir receiver is receiving.
Comment 1 Bug Zapper 2008-11-25 22:56:30 EST
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
Comment 2 Jarod Wilson 2009-07-21 22:41:42 EDT
Wow, took me a while to get around to this... The problem is that xmode2 is trying to load up a Courier font, which isn't on most systems. A simple enough fix is to build it to use the 'misc-fixed' font instead. Pushing that change into rawhide now...
Comment 3 Bug Zapper 2009-11-18 03:35:18 EST
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  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 '10'.

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 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
Comment 4 Bug Zapper 2009-12-18 01:35:36 EST
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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.

Thank you for reporting this bug and we are sorry it could not be fixed.
Comment 5 Jarod Wilson 2010-01-22 15:52:07 EST
Was actually fixed in rawhide, altering state slightly to reflect that.

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