Bug 72446 - ERROR:couldn't find RGB GLX visual or fbconfig on xorg-server-1.14.99.903 (1.15.0 RC 3)
Summary: ERROR:couldn't find RGB GLX visual or fbconfig on xorg-server-1.14.99.903 (1....
Status: RESOLVED DUPLICATE of bug 70706
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/Ext/GLX (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-07 18:36 UTC by Dieter Nützel
Modified: 2013-12-07 21:29 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Xorg.0.log (45.09 KB, text/plain)
2013-12-07 18:36 UTC, Dieter Nützel
no flags Details
dmesg.log (49.89 KB, text/plain)
2013-12-07 18:37 UTC, Dieter Nützel
no flags Details

Description Dieter Nützel 2013-12-07 18:36:14 UTC
Created attachment 90422 [details]
Xorg.0.log

Run glxinfo,report couldn't find RGB GLX visual or fbconfig. It happens on xorg-server-1.14.99.903 (1.15.0 RC 3). It works well on xorg-server- 1.14.4.901 and 1.14.3.xx (before).
Have a look at this
https://bugs.freedesktop.org/show_bug.cgi?id=72295, too.

All versions are compiled for openSUSE 12.3/13.1.

/home/dieter> glxinfo 
name of display: :0
Error: couldn't find RGB GLX visual or fbconfig
Error: couldn't find RGB GLX visual or fbconfig

240 GLX Visuals
    visual  x   bf lv rg d st  colorbuffer  sr ax dp st accumbuffer  ms  cav
  id dep cl sp  sz l  ci b ro  r  g  b  a F gb bf th cl  r  g  b  a ns b eat
----------------------------------------------------------------------------
0x021 24 tc  0  32  0 r  y .   8  8  8  8 .  .  0 24  8  0  0  0  0  0 0 None
[-]
Comment 1 Dieter Nützel 2013-12-07 18:37:27 UTC
Created attachment 90423 [details]
dmesg.log
Comment 2 Dennis Schridde 2013-12-07 21:29:12 UTC

*** This bug has been marked as a duplicate of bug 70706 ***


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.