Bug 438361

Summary: compositing manager breaks totem (Xv, presumably)
Product: [Fedora] Fedora Reporter: Bill Nottingham <notting>
Component: xorg-x11-drv-i810Assignee: Søren Sandmann Pedersen <sandmann>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: rawhideCC: fedora, kem, mcepl, rvokal, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-04-08 05:29:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
X log none

Description Bill Nottingham 2008-03-20 15:32:42 UTC 
Description of problem:

If the CM is active, any time totem wants to display a video/visualization, it
receives:

The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 783 error_code 11 request_code 140 minor_code 19)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Turning off the CM 'fixes' it. Filing initially against metacity, I suppose this
bug could be in anywhere from the intel driver up to the gstreamer stack.

Version-Release number of selected component (if applicable):

totem-2.23.0-5.fc9.x86_64
xorg-x11-server-Xorg-1.4.99.901-10.20080314.fc9.x86_64
xorg-x11-drv-i810-2.2.1-14.fc9.x86_64
metacity-2.22.0-2.fc9.x86_64
gstreamer-0.10.17.2-1.fc9.x86_64

How reproducible:

Every time
Comment 1 Thorsten Leemhuis 2008-03-28 17:08:49 UTC 
Confirmed. The error I got as soon Metacity's CM is enabled is:
----
The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 59 error_code 11 request_code 140 minor_code 19)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
----
Hardware: GM965 with xorg-x11-drv-i810-2.2.1-15.fc9.x86_64 (and rawhide up2date
as of 20080328)

/me wonders if we should CC xgl-maint, as it might be a bug/feature
of the driver...
Comment 2 Sindre Pedersen Bjørdal 2008-04-02 13:44:44 UTC 
I believe this is a bug in the driver. Using the intel driver, switching to EXA
instead of XAA works around this bug. I added the following to my
/etc/X11/xorg.conf Device section:

Option "AccelMethod" "EXA"

Now both Xv and compositing works.
Comment 3 Thorsten Leemhuis 2008-04-03 15:25:22 UTC 
(In reply to comment #2)
> I believe this is a bug in the driver.

CCing xgl-maint, to get their opinion if this is a bug in metacity or the intel
driver

> Using the intel driver, switching to EXA
> instead of XAA works around this bug. I added the following to my
> /etc/X11/xorg.conf Device section:
> Option "AccelMethod" "EXA"
> Now both Xv and compositing works.
Comment 4 Matěj Cepl 2008-04-03 20:55:39 UTC 
Can we get /var/log/Xorg.*.log please?
Comment 5 Bill Nottingham 2008-04-03 21:33:04 UTC 
Created attachment 300348 [details]
X log

Here you go. Doesn't look like anything of value is in there.
Comment 6 Bill Nottingham 2008-04-08 05:29:32 UTC 

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