Bug 3982 - glxinfo disagrees xorg.log / too old libgl
Summary: glxinfo disagrees xorg.log / too old libgl
Status: RESOLVED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: libGL (show other bugs)
Version: XOrg git
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-05 04:34 UTC by Steffen Schwientek
Modified: 2008-01-11 11:25 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Steffen Schwientek 2005-08-05 04:34:09 UTC 
On my thinkpad t22 (savage chipset) glxinfo disagree the xorg.log.  
Xorg.log is telling, dri enabled, glxinfo is telling direct rendering  
disabled.  
xdriinfo is telling me, libGL is too old. Can't be, Mesa  is fresh (latest  
cvs). 
 
Steffen
Comment 1 Steffen Schwientek 2005-08-05 04:35:54 UTC 
Created attachment 3259 [details]
Xorg.0.log
Comment 2 Steffen Schwientek 2005-08-05 04:37:19 UTC 
Created attachment 3260 [details] [review]
BRANCH_1_0 patch 1/2: Fix locking in cairo_scaled_font_reference/destroy
Comment 3 Alex Deucher 2005-08-05 05:20:53 UTC 
(In reply to comment #0)
> On my thinkpad t22 (savage chipset) glxinfo disagree the xorg.log.  
> Xorg.log is telling, dri enabled, glxinfo is telling direct rendering  
> disabled.  
> xdriinfo is telling me, libGL is too old. Can't be, Mesa  is fresh (latest  
> cvs). 
>  

Are you sure you are using the latest libGL and not an old you may have floating
around?  Did you back up your old one with a name like libGL.so.1.2.bak?  if so,
ld will will symlink to that one since it has the longest extension.
Comment 4 Joachim Frieben 2005-08-05 05:30:34 UTC 
How about Mesa being too new? It just got updated to version 1.3.1 which should
conflict with your X.org revision 6.8.99.16 anyway. If you set
LIBGL_DEBUG=verbose and e.g. execute "glxgears", then OpenGL should complain
about missing symbols.
Comment 5 Ian Romanick 2005-10-12 08:20:54 UTC 
Is anyone still able to reproduce this problem?  If so, what does 'ldd $(which
glxinfo)' show?  Also, the attachments seem to be wrong.  #3259 is incomplete,
and #3260 is just wrong.  It looks like a patch, not a glxinfo log.  The output
of 'LIBGL_DEBUG_VERBOSE=y glxinfo' would be useful.

Thanks.
Comment 6 Koby 2006-02-02 05:31:44 UTC 
Created a new bug, since there's no library missing in my case, and I'm using
the i810 card, bug#: 5792. Have attached the libgl verbose output there.

Hopefully this shouldn't be a dupe. :p

Thanks!
 
(In reply to comment #5)
> Is anyone still able to reproduce this problem?  If so, what does 'ldd $(which
> glxinfo)' show?  Also, the attachments seem to be wrong.  #3259 is incomplete,
> and #3260 is just wrong.  It looks like a patch, not a glxinfo log.  The output
> of 'LIBGL_DEBUG_VERBOSE=y glxinfo' would be useful.
> 
> Thanks.
> 

(In reply to comment #5)
> Is anyone still able to reproduce this problem?  If so, what does 'ldd $(which
> glxinfo)' show?  Also, the attachments seem to be wrong.  #3259 is incomplete,
> and #3260 is just wrong.  It looks like a patch, not a glxinfo log.  The output
> of 'LIBGL_DEBUG_VERBOSE=y glxinfo' would be useful.
> 
> Thanks.
>
Comment 7 Benjamin Close 2008-01-11 02:36:39 UTC 
Bugzilla Upgrade Mass Bug Change

NEEDSINFO state was removed in Bugzilla 3.x, reopening any bugs previously listed as NEEDSINFO.

  - benjsc
    fd.o Wrangler
Comment 8 Alex Deucher 2008-01-11 11:25:18 UTC 
closing

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.