GNOME Bugzilla – Bug 524229
Crash on startup with V4L (1, not 2) webcam
Last modified: 2008-03-27 19:35:57 UTC
DESCRIPTION: Simply doesn't start, with or without the webcam connected. Driver of the webcam gspcav1. Same webcam works with every other application, skype included. Cheese worked this summer, doesn't work anymore since middle Autumn (if I remember correctly, but I'm not sure of *when* it occures for the first time) LOG: Distribution: Unknown Gnome Release: 2.22.0 2008-03-17 (Archlinux) BugBuddy Version: 2.22.0 System: Linux 2.6.24-ARCH #1 SMP PREEMPT Mon Mar 24 11:54:58 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Flat Icon Theme: gnome Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Output of custom script "/usr/libexec/cheese/cheese-bugreport.sh": Cheese log: Detected webcam: Logitech QuickCam EC device: /dev/v4l/video0 video/x-raw-yuv 160 x 120 num_framerates 1 25/1 video/x-raw-yuv 320 x 240 num_framerates 1 25/1 video/x-raw-yuv 352 x 288 num_framerates 1 25/1 video/x-raw-yuv 176 x 144 num_framerates 1 25/1 video/x-raw-rgb 160 x 120 num_framerates 1 25/1 video/x-raw-rgb 320 x 240 num_framerates 1 25/1 video/x-raw-rgb 352 x 288 num_framerates 1 25/1 video/x-raw-rgb 176 x 144 num_framerates 1 25/1 video/x-raw-rgb 160 x 120 num_framerates 1 25/1 video/x-raw-rgb 320 x 240 num_framerates 1 25/1 video/x-raw-rgb 352 x 288 num_framerates 1 25/1 video/x-raw-rgb 176 x 144 num_framerates 1 25/1 video/x-raw-rgb 160 x 120 num_framerates 1 25/1 video/x-raw-rgb 320 x 240 num_framerates 1 25/1 video/x-raw-rgb 352 x 288 num_framerates 1 25/1 video/x-raw-rgb 176 x 144 num_framerates 1 25/1 v4lsrc name=video_source device=/dev/v4l/video0 ! video/x-raw-yuv,width=352,height=288,framerate=25/1 ! identity
Closing, cheese requires gstreamer0.10-theora, after installing it cheese starts working again.
*** This bug has been marked as a duplicate of 522009 ***