Bug 212199 - ftview could not allocate display surface
ftview could not allocate display surface
Status: CLOSED ERRATA
Product: Fedora
Classification: Fedora
Component: freetype (Show other bugs)
6
All Linux
medium Severity medium
: ---
: ---
Assigned To: Behdad Esfahbod
Brock Organ
:
Depends On:
Blocks: 216222 217193
  Show dependency treegraph
 
Reported: 2006-10-25 12:37 EDT by Alexei Podtelezhnikov
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version: 2.2.1-14
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-12-02 13:42:02 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Alexei Podtelezhnikov 2006-10-25 12:37:43 EDT
Description of problem:
I can't  seem to get ftview to work 

[apodtele@prosha dejavu-lgc]$ ftview 12 DejaVuLGCSans-Bold.ttf
could not allocate display surface
  error = 0x0000


Version-Release number of selected component (if applicable):
freetype-demos-2.2.1-10

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Alexei Podtelezhnikov 2006-11-17 10:44:04 EST
Could this be a solution?
http://lists.nongnu.org/archive/html/freetype/2006-11/msg00025.html

ftview seem to look for X under /usr/X11R6. So old-fashioned!
Comment 2 Matthias Clasen 2006-11-17 16:25:55 EST
Sounds likely. Thanks for the pointer
Comment 3 Behdad Esfahbod 2006-11-21 16:15:32 EST
Thanks for the pointer.  Seems like it.  Last time I looked into it, I was
surprised to find that ftview is not linked to xlib at all.  This explains it.
Comment 4 Alexei Podtelezhnikov 2006-11-21 18:43:22 EST
I look forward to seeing an update. ;) 
Comment 5 Behdad Esfahbod 2006-11-24 18:20:59 EST
Fixed in freetype-2.2.1-14.fc6 submitted for Update Testing.
Comment 6 Alexei Podtelezhnikov 2006-12-02 13:42:02 EST
marking as fixed by the official update >2.2.1-14

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