Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 81793 - i810 Xv cursor problem.
Summary: i810 Xv cursor problem.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: XFree86
Version: phoebe
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks: 82787
TreeView+ depends on / blocked
 
Reported: 2003-01-14 01:54 UTC by David Woodhouse
Modified: 2007-04-18 16:49 UTC (History)
0 users

Fixed In Version: 4.3.0-2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-04-25 10:10:05 UTC


Attachments (Terms of Use)

Description David Woodhouse 2003-01-14 01:54:05 UTC
Use xawtv to display a TV picture. 
Place mouse cursor in the TV picture.
Press a key to change TV channel.
Move cursor.

When I subsequently move the mouse, I get a black square in the picture where
the cursor was during the channel change. This is with i810 video and a
bt848-based TV card.

Comment 1 Mike A. Harris 2003-01-24 13:45:51 UTC
Can you test wether or not "swcursor" makes the problem go away, and then
report this upstream to xfree86@xfree86.org as well, so that David
can fix it (since he's the current driver maintainer)?



Comment 2 Mike A. Harris 2003-02-14 23:13:23 UTC
ping?

Comment 3 Mike A. Harris 2003-02-24 10:50:51 UTC
Defering for future

Comment 4 Mike A. Harris 2003-04-25 10:10:05 UTC
This is likely fixed in 4.3.0 in RHL 9 now, so I'm going to assume that, and
close it CURRENTRELEASE, however if the problem exists still in RHL 9,
please file a bug report upstream at http://bugs.xfree86.org and then reopen
this report, and add the upstream URL and I'll track it upstream.

Parallelization.  ;o)


Note You need to log in before you can comment on or make changes to this bug.