Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: I used xawtv for many years without problems. After upgrade to F21, I can no longer switch channels. Whatever channel was set when xawtv started, displays fine. But when I switch the channel, the image freezes. The sound, however, changes fine. If I restart xawtv, it will properly display the channel to which I switched. Version-Release number of selected component (if applicable): xawtv-3.103-4.fc21.x86_64 (worked on the latest from F19, not tried on F20) How reproducible: Easily Steps to Reproduce: 1. start xawtv 2. make sure the disaplay is fine 3. switch channel Actual results: Video freezes, only sound changes Expected results: Both sound and video changes. Additional info: Verified with tvtime: switching works fine. Unfortunately tvtime does not support sound, so I have to stick to xawtv...
ioctl: VIDIOC_REQBUFS(count=0;type=VIDEO_CAPTURE;memory=MMAP): Device or resource busy ioctl: VIDIOC_REQBUFS(count=2;type=VIDEO_CAPTURE;memory=MMAP): Device or resource busy Warning: Non-character code(s) in source. Warning: Non-character code(s) in source. ioctl: VIDIOC_QBUF(index=0;type=VIDEO_CAPTURE;bytesused=221184;flags=0x2003 [MAPPED,QUEUED,(null)];field=BOTTOM;;timecode.type=0;timecode.flags=0;timecode.frames=0;timecode.seconds=0;timecode.minutes=0;timecode.hours=0;timecode.userbits="";sequence=0;memory=MMAP): Device or resource busy libv4l2: error dequeuing buf: Device or resource busy ioctl: VIDIOC_DQBUF(index=0;type=VIDEO_CAPTURE;bytesused=0;flags=0x0 [];field=ANY;;timecode.type=0;timecode.flags=0;timecode.frames=0;timecode.seconds=0;timecode.minutes=0;timecode.hours=0;timecode.userbits="";sequence=0;memory=MMAP): Device or resource busy ioctl: VIDIOC_REQBUFS(count=0;type=VIDEO_CAPTURE;memory=MMAP): Device or resource busy v4l2: read: Invalid argument What can this mean? Maybe xawtv now tries to open the new channel somehow before closing the previous one? Just a wild guess.
The fix is posted: https://bugzilla.redhat.com/show_bug.cgi?id=1155784#c5
*** This bug has been marked as a duplicate of bug 1155784 ***