Description of problem: Running updated cheese or gnome-control-center and trying to take a photo (or turning the camera on). Version-Release number of selected component: cheese-3.14.1-1.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 3 cmdline: /usr/bin/cheese --gapplication-service executable: /usr/bin/cheese kernel: 3.17.1-302.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 ?? #1 draw_pt_emit_linear at draw/draw_pt_emit.c:235 #2 emit at draw/draw_pt_fetch_shade_pipeline_llvm.c:336 #3 llvm_pipeline_generic at draw/draw_pt_fetch_shade_pipeline_llvm.c:468 #4 llvm_middle_end_linear_run at draw/draw_pt_fetch_shade_pipeline_llvm.c:532 #5 vsplit_segment_simple_linear at draw/draw_pt_vsplit_tmp.h:240 #6 vsplit_run_linear at draw/draw_split_tmp.h:60 #7 draw_pt_arrays at draw/draw_pt.c:149 #8 draw_vbo at draw/draw_pt.c:564 #9 llvmpipe_draw_vbo at lp_draw_arrays.c:132
Created attachment 948626 [details] File: backtrace
Created attachment 948627 [details] File: cgroup
Created attachment 948628 [details] File: core_backtrace
Created attachment 948629 [details] File: dso_list
Created attachment 948630 [details] File: environ
Created attachment 948631 [details] File: exploitable
Created attachment 948632 [details] File: limits
Created attachment 948633 [details] File: maps
Created attachment 948634 [details] File: open_fds
Created attachment 948635 [details] File: proc_pid_status
Created attachment 948636 [details] File: var_log_messages
Created attachment 948637 [details] gdb output of backtrace full - missing debuginfos? This is the backtrace given by gdb by cheese and gnome-control-center when trying to turn on the webcam to take a photo. I'm not sure what debuginfos are missing and I see no prompt to download them. I'm suspicious that this may be related to kernel problems, and I'm trying to rebuild the rawhide kernel to see how it works. (I have heard it corrects at least one of the issues present on 3.17.x.) The only common thread seems to be libjpeg.
Whatever the cause, this issue appears to be resolved on my machine now.