Bug 15918

Summary: X error when run gl-117
Product: xorg Reporter: liuhaien <haien.liu>
Component: Driver/intelAssignee: Wang Zhenyu <zhenyu.z.wang>
Status: VERIFIED FIXED QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium    
Version: git   
Hardware: Other   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Xorg.0.log none

Description liuhaien 2008-05-12 23:28:55 UTC
Created attachment 16501 [details]
Xorg.0.log

when run 
#xinit&
# gl-117

 then gl117 cannot run normally and X output below info:

Info: Found gl-117 data directory /usr/local/share/gl-117
Info: Startup gl-117, V1.3 ...
Info: Loading /root/.gl-117/conf
Info: Saving /root/.gl-117/conf
Info: Loading /root/.gl-117/conf.interface
Info: Saving /root/.gl-117/conf.interface
Info: Using SDL and GLUT
*** PULSEAUDIO: Unable to connect: Connection refused
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  133 (XFree86-VidModeExtension)
  Minor opcode of failed request:  10 (XF86VidModeSwitchToMode)
  Value in failed request:  0x73
  Serial number of failed request:  123
  Current serial number in output stream:  125
Comment 1 Wang Zhenyu 2008-05-13 18:45:50 UTC
It looks gl-117 wants to set full screen mode according to its ~/.gl-117/conf file setting, it suspects it's gl-117's bug to not correctly set modes, change in that conf file according with current mode can resolve this.
Comment 2 Wang Zhenyu 2008-06-18 00:18:08 UTC
It looks I can't produce this on 915G with xserver-1.5 and mesa-7.1 rc1. Is this 965 specific problem?
Comment 3 Wang Zhenyu 2008-06-18 18:49:30 UTC
Can't produce with upstream stable (mesa-7.0.4, xserver-1.4.1, x-v-i 2.3.2) on 965GM too.

Could you specify which versions you're using and might be good to retest with current updates.
Comment 4 liuhaien 2008-06-18 21:44:16 UTC
I try to run it using the latest commit,and it works well on q965 now.

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.