Description of problem: I know that cheese worked on this computer earlier ... but now, as soon as I start it, the main window appears and then the application segfaults. Here's a backtrace: #0 0x00007fffeaecac06 in ?? () from /usr/lib64/libv4lconvert.so.0 #1 0x00007fffeaecb825 in ?? () from /usr/lib64/libv4lconvert.so.0 #2 0x00007fffeaebee7f in v4lconvert_convert () from /usr/lib64/libv4lconvert.so.0 #3 0x00007fffeb1260a8 in ?? () from /usr/lib64/libv4l2.so.0 #4 0x00007fffeb126943 in v4l2_ioctl () from /usr/lib64/libv4l2.so.0 #5 0x00007fffeb5941b3 in gst_color_balance_channel_get_type () at colorbalancechannel.c:56 #6 0x00007fffeb58b92c in gst_color_balance_channel_get_type () at colorbalancechannel.c:56 #7 0x00007fffeb34353d in gst_base_src_get_range (src=0x7fffe401a320, offset=18446744073709551615, length=4096, buf=<value optimized out>) at gstbasesrc.c:1943 #8 0x00007fffeb345323 in gst_base_src_loop (pad=0x7a38a0) at gstbasesrc.c:2186 #9 0x0000003fcf0787cb in gst_task_func (task=0x7fffe4004a10, tclass=<value optimized out>) at gsttask.c:172 #10 0x0000003f11c62d22 in g_thread_pool_thread_proxy (data=<value optimized out>) at gthreadpool.c:265 #11 0x0000003f11c616e4 in g_thread_create_proxy (data=0x7fffe4124d90) at gthread.c:635 #12 0x0000003f0fc0686a in start_thread (arg=<value optimized out>) at pthread_create.c:297 #13 0x0000003f0f0de25d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #14 0x0000000000000000 in ?? () Version-Release number of selected component (if applicable): cheese-2.26.0-1.fc11.x86_64 How reproducible: Every time Steps to Reproduce: 1. start cheese Actual results: segfault after window appears
Hmm, Are you using F-11 updates-testing ? To be sure could you do: rpm -q libv4l And paste the output here ?
I do have updates-testing enabled, and here's the result of the query you wanted: % rpm -q libv4l libv4l-0.5.98-1.fc11.x86_64
I just tried rolling back to libv4l-0.5.9-1.fc11.x86_64 and cheese works fine -- should the bug be reassigned to libv4l?
(In reply to comment #3) > I just tried rolling back to libv4l-0.5.9-1.fc11.x86_64 and cheese works fine > -- should the bug be reassigned to libv4l? Yes there is a known issue with 0.5.98, I'll change the component, also note that a new 0.5.99, which should fix this, is on its way to updates-testing.
libv4l-0.5.99-1.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/libv4l-0.5.99-1.fc11
libv4l-0.5.99-1.fc11, v4l2ucp-1.3-2.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update libv4l v4l2ucp'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-5968
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Updates-testing now has 0.6.1, since this has only happened in updates testing I'm closing this.