Bug 16559 - clients running indirect GLX fail under Xephyr
Summary: clients running indirect GLX fail under Xephyr
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/DDX/Xephyr (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Matthew Allum
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-29 06:51 UTC by Andy Wingo
Modified: 2018-06-12 18:43 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andy Wingo 2008-06-29 06:51:36 UTC
Hi,

Running GLX clients under Xephyr fails with indirect contexts. To reproduce:

1. Run Xephyr: Xephyr :1 -ac -screen 800x600 &
2. Run gears with direct rendering: DISPLAY=:1 glxgears
   -- runs fine
3. Control-C the direct gears, then run it indirectly: DISPLAY=:1 LIBGL_ALWAYS_INDIRECT=1 glxgears
   -- gets the following error:

$ LIBGL_ALWAYS_INDIRECT=1 DISPLAY=:1 glxgears
X Error of failed request:  BadImplementation (server does not implement operation)
  Major opcode of failed request:  152 (GLX)
  Minor opcode of failed request:  5 (X_GLXMakeCurrent)
  Serial number of failed request:  22
  Current serial number in output stream:  22
X Error of failed request:  GLXBadDrawable
  Major opcode of failed request:  152 (GLX)
  Minor opcode of failed request:  11 (X_GLXSwapBuffers)
  Serial number of failed request:  23
  Current serial number in output stream:  111


My xephyr is from Fedora, but appears to be quite recent:
  xorg-x11-server-Xephyr-1.4.99.902-3.20080612.fc9.i386

I run intel drivers.
Comment 1 Adam Jackson 2018-06-12 18:43:28 UTC
Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please file a new report if you continue to experience issues with a current server.


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.