Created attachment 399071 [details] lsusb.log If I press the "start recording" button in cheese, it changes the icon to the stop icon but the text does not change. The webcam image turns black for 2-3 seconds, then works again. At that time, the video is captured but the button label is still wrong. If I press "start recording" again, recording stops but the button now stays disabled, so that I need to restart cheese in order to record a new video. This is what I see on the console: --- [liveuser@localhost Desktop]$ cheese libv4l2: error converting / decoding frame data: v4l-convert: error parsing JPEG header: Not a JPG file ? libv4l2: error converting / decoding frame data: v4l-convert: error parsing JPEG header: We do not support more than 4 AC Huffman table << starting recording >> << stopping recording >> (cheese:3723): GLib-GObject-CRITICAL **: g_signal_emit_valist: assertion `signal_id > 0' failed libv4l2: error converting / decoding frame data: v4l-convert: error parsing JPEG header: Not a JPG file ? libv4l2: error converting / decoding frame data: v4l-convert: error parsing JPEG header: Not a JPG file ? ---
Btw, same results with cheese 2.29.90 (as in current F13) as well as the manually updated cheese 2.29.92 from Koji.
I also updated gstreamer* to the packages from updates-testing
While doing the webcam tests for test day, I remember the Recording button needing to pressed twice, but I started the cheese app from the menu and didn't see the terminal errors, so I went back. Unlike the original poster I didn't get v4l errors, only gtk errors. When opening cheese I get: (cheese:3130): Gtk-WARNING **: Theme directory 256x256/status;scalable/apps of theme gnome has no size field When closing cheese I got: (cheese:3130): GLib-GObject-CRITICAL **: g_signal_emit_valist: assertion `signal_id > 0' failed When clicking the record button (second from left), a Start Recording button appeared with a red circle. After pressing the Start Recording button, the red button changed to grey, but the button still said Start Recording instead of Stop recording. I also experienced the program lockup, not only when trying to start a new recording, but when trying to switch to Photo or the Burst mode. All buttons remained greyed out, but menu choices above and photos and videos below were accessible. I also had to exit program before I could restart functions.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.