On Thu, Jul 01, 2010 at 02:33:04PM +1000, Norman Gaywood wrote: > $ glxgears > X Error of failed request: BadRequest (invalid request code or no such > operation) > Major opcode of failed request: 136 (DRI2) > Minor opcode of failed request: 1 (DRI2Connect) > Serial number of failed request: 18 > Current serial number in output stream: 18
This RedHat bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=601773 (BadRequest from DRI2_Connect) has a note (from Owen Taylor at redhat) saying: > ... DRI2Connect giving a BadRequest. This seems to be triggered in > the normal case if DRI2Connect is called on a remote server; I don't > immediately see what is supposed to prevent that from happening. If I'm reading that correctly, he is saying that DRI2Connect will always fail. So are programs like glxgears on a remote X server working for anyone? Note, that from my standard F12 laptop (not an LTSP terminal), I can "ssh -Y server glxgears" and glxgears will run fine (but slow). -- Norman Gaywood, Computer Systems Officer University of New England, Armidale, NSW 2351, Australia ngayw...@une.edu.au Phone: +61 (0)2 6773 3337 http://mcs.une.edu.au/~norm Fax: +61 (0)2 6773 3312 Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
