After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 160749 - [v4lsrc] gst-recorder "v4l source error" failure during bt848 capture
[v4lsrc] gst-recorder "v4l source error" failure during bt848 capture
Status: RESOLVED FIXED
Product: Cupid
Classification: Deprecated
Component: general
0.0.1
Other Linux
: Normal critical
: 0.0.2
Assigned To: Cupid Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-12-08 02:28 UTC by Aaron VanDevender
Modified: 2005-01-11 09:22 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Aaron VanDevender 2004-12-08 02:28:55 UTC
I start gst-recroder and configure a capture from a bt848 v4l video source and
an alsa audio source. As soon as I hit record, I get a stream of error beebs
coming at (I assume) 24 beeps per second. The error dialog says:

Element Video (video4linux/raw) Source gave an error
Could not get/set settings from/on source

At this point nothing will stop it (close box, ^C) and indeed, the entire X
session becomes unresponsive due to the costant deluge of error beeps. So I have
to switch to a virtual console and killall gst-recorder to get it to stop. Once
I have done that, the beeping stops right away, but it still takes about 15
seconds for the desktop to start responding to events again.
Comment 1 Ronald Bultje 2005-01-11 00:25:00 UTC
I can confirm this, I'm trying to debug it now but I'm not having much luck yet...
Comment 2 Ronald Bultje 2005-01-11 09:22:18 UTC
OK, that was a bad night, but it's fixed now. I've emulated errors at random
places and was able to kill all hangs that I could find. If you see more hangs,
let me know.