Question / Help Fedora 20 x64/Gnome 3, red box on Xcomposite window capture

windcask

New Member
Hello, all. I get solid red boxes on all windows I attempt to capture with Xcomposite.

Here's the terminal output:

error: xcompcap: glXCreatePixmap failed: BadMatch (invalid parameter attributes)
info: source 'Window Capture (Xcomposite)' (xcomposite_input) created
error: xcompcap: glXCreatePixmap failed: BadMatch (invalid parameter attributes)
error: xcompcap: glXCreatePixmap failed: BadMatch (invalid parameter attributes)
error: xcompcap: XCompositeRedirectWindow failed: BadWindow (invalid Window parameter)
error: xcompcap: glXCreatePixmap failed: BadMatch (invalid parameter attributes)
error: xcompcap: glXCreatePixmap failed: BadMatch (invalid parameter attributes)
error: xcompcap: glXCreatePixmap failed: BadAlloc (insufficient resources for operation)
error: xcompcap: glXCreatePixmap failed: BadAlloc (insufficient resources for operation)
error: xcompcap: glXCreatePixmap failed: BadAlloc (insufficient resources for operation)
error: xcompcap: glXCreatePixmap failed: BadAlloc (insufficient resources for operation)
error: xcompcap: glXCreatePixmap failed: BadAlloc (insufficient resources for operation)
error: xcompcap: XCompositeRedirectWindow failed: BadWindow (invalid Window parameter)
info: source 'Window Capture (Xcomposite)' destroyed


Thanks for any help you can provide.
 

windcask

New Member
Also, when I closed the program, this came up:

(obs:4410): Gdk-ERROR **: The program 'obs' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 1190 error_code 3 request_code 141 minor_code 3)
 

Lain

Forum Admin
Lain
Forum Moderator
Developer
I've seen people reporting this, but I have fedora myself and haven't been able to replicate. Might need a full log file, ideally.
 

mangopuncher

New Member
I've seen people reporting this, but I have fedora myself and haven't been able to replicate. Might need a full log file, ideally.

I'll be generating a log file today with my set up. I encounter this bug every time while using Gnome 3, sometimes with KDE, and never with MATE. I'll generate respective log files for each situation if that'll help.

Here's the Gnome 3 log file: https://gist.github.com/c1e2f806458024800f74.git
Here's the MATE log file: https://gist.github.com/00fcc4ecb1381ea20320.git

The end of the log file for both is me adding a window from Google Chrome, with Gnome 3 giving the "red square" bug, and MATE capturing it just fine. Hope it helps!
 
Last edited:

Lain

Forum Admin
Lain
Forum Moderator
Developer
I use GNOME 3 myself, not entirely sure what's going on here. Does it only happen with chrome? Any other windows? I'll have to see if I can test chrome later.
 

mangopuncher

New Member
Here's a list of applications I've tried to replicate the red square bug with (all in gnome 3):

  1. Google Chrome = Red Square
  2. Gnome Terminal = Correctly Rendered
  3. Steam = Red Square
  4. Google Earth = Correctly Rendered
  5. TF2 = correctly rendered
  6. Binding of Issac = Correctly rendered
  7. Nautilus = Red Square
Log file here: https://gist.github.com/7f5003246e301ece3568
 

Lucki

New Member
I can confirm this for Steam and Nautilus. Others are fine, on which desktop they are doesn't matter.
 
Top