GNOME Bugzilla – Bug 649344
Crash after select a effect
Last modified: 2011-06-20 17:17:59 UTC
Created attachment 187167 [details] Cheese Bug When i select a effect to apply to cheese, cheese inmediatly crash. I attached the outputs that i got in the terminal with differents levels of Debug. $ cheese > salida $ cheese --gst-debug-level=1 >> salida1 $ cheese --gst-debug-level=2 >> salida2 $ cheese --gst-debug-level=3 >> salida3 I hope i can help you with cheese project @alejo0317
All files are empty in your attachment. Need better information.
Hi. This seems to be a duplicate of #647677.
I'm sorry I exec this ("$ cheese --gst-debug-level=2 ") and got this output http://pastebin.com/05GV2GtE And when i exec ("$ cheese") i got this http://pastebin.com/WZd2grJC I hope i can help you. I am on archlinux i386, 2.6.38
Same problem here. Im using Archlinux too.
*** Bug 650734 has been marked as a duplicate of this bug. ***
Hi, I did three steps and I got the same crashes: 1. Tried the effect in cheese with the Cheese installed in gnome 3 - fedora 15 2. Download the last packages (April, 26th) and call cheese from Terminal. 3. Remove cheese and re installed doing this: 3.1. Uninstall the Cheese package. 3.2. Run "yum-builddep cheese" as root to install all of the things Cheese needs to compile. 3.3. As a normal user (i.e. *not* root), extract the Cheese tarball somewhere in your Home directory using "tar -xvzf cheese-3.0.1.tar.gz" 3.4. Go into the Cheese directory and type "./configure" 3.5. If Configure was successful, type "make" to compile Cheese. 3.6. Now, as the root user again, type "make install" to install Cheese. You should now be able to run it. PS: I put some figures about it in my blog: http://lleksah.wordpress.com/2011/06/17/my-second-report-opw/ Regards from, Julita Inca
"Me too" comments are not that helpful - see comment 0 how to provide debug logs.
According to the debug logs from Alessandro Rojas, this is really a duplicate of bug #647677, as Sandro pointed before. Please reopen with a backtrace if you find the patch doesn't solve your problem. *** This bug has been marked as a duplicate of bug 647677 ***