[i865g] video playback fails with (EE) intel(0): Failed to pin xv buffer
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xserver-xorg-video-intel (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: xserver-
When attempting to play video files or streams, various video viewing program crash and I get this error in Xorg.0.log:
(EE) intel(0): Failed to pin xv buffer
this is a regression in jaunty - video playback worked fine on this PC in Intrepid. No dual-head or anything special in Xorg.conf.
tvtime TV capture also stopped working in Jaunty:
gug@gug-
Running tvtime 1.0.2.
Reading configuration from /etc/tvtime/
Reading configuration from /home/gug/
Cannot allocate enough off-screen video memory. This may be fixed by:
1. Closing or restarting large X applications.
2. Lowering the input width of tvtime (--inputwidth parameter).
3. Lowering your colour depth or highest configured resolution.
4. Increasing the amount of video memory in your X config file
(for example, if you are using the i810 XFree86 driver.)
See http://
ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: xserver-
ProcEnviron:
LANG=en_CA.UTF-8
SHELL=/bin/bash
ProcVersion: Linux version 2.6.28-11-generic (buildd@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009
SourcePackage: xserver-
Uname: Linux 2.6.28-11-generic i686
[lspci]
00:00.0 Host bridge [0600]: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface [8086:2570] (rev 02)
Subsystem: Hewlett-Packard Company Device [103c:12bc]
00:02.0 VGA compatible controller [0300]: Intel Corporation 82865G Integrated Graphics Controller [8086:2572] (rev 02)
Subsystem: Hewlett-Packard Company Device [103c:12bc]
description: | updated |
tags: | added: 865g intel jaunty video xorg |
totem error when attempting video playback:
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 103 error_code 11 request_code 132 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.)