Bug 444479 - exa gives undefined symbol: fbGlyph8
Summary: exa gives undefined symbol: fbGlyph8
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 8
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-04-28 15:49 UTC by udo
Modified: 2008-05-05 18:26 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-05-05 18:26:57 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description udo 2008-04-28 15:49:56 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.14) Gecko/20080416 Fedora/2.0.0.14-1.fc8 Firefox/2.0.0.14

Description of problem:
When I try to use EXA on my EN12000 I get:

(II) LoadModule: "exa"
(II) Loading /usr/lib/xorg/modules//libexa.so
dlopen: /usr/lib/xorg/modules//libexa.so: undefined symbol: fbGlyph8
(EE) Failed to load /usr/lib/xorg/modules//libexa.so
(II) UnloadModule: "exa"
(EE) Failed to load module "exa" (loader failed, 7)

Version-Release number of selected component (if applicable):
xorg-x11-server-Xorg-1.3.0.0-44.fc8

How reproducible:
Always


Steps to Reproduce:
1. edit xorg.conf to load exa
2. startx
3. bingo

Actual Results:
(II) LoadModule: "exa"
(II) Loading /usr/lib/xorg/modules//libexa.so
dlopen: /usr/lib/xorg/modules//libexa.so: undefined symbol: fbGlyph8
(EE) Failed to load /usr/lib/xorg/modules//libexa.so
(II) UnloadModule: "exa"
(EE) Failed to load module "exa" (loader failed, 7)

Expected Results:
functioning EXA

Additional info:
VIA Epia EN12000 with Fedora 8, openchrome video driver

Comment 1 udo 2008-04-28 15:58:28 UTC
xorg-x11-drv-openchrome-0.2.901-2.fc8
is the videodriver I use.

Comment 2 Adam Jackson 2008-05-05 18:26:57 UTC
You're doing it wrong.  Don't Load "exa".  Say Option "AccelMethod" "EXA" in the
Device section for the video card.


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