GNOME Bugzilla – Bug 650388
Cheese: Segmentation fault after choosing effect
Last modified: 2011-06-17 14:17:49 UTC
Hi, so after I choose which effect to use, cheese crashes with this message: ################################################################################ ** (cheese:9377): WARNING **: Internal GStreamer error: clock problem. Please file a bug at http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer. ** (cheese:9377): WARNING **: Internal data flow problem. ** (cheese:9377): WARNING **: Internal data flow problem. ** (cheese:9377): WARNING **: Internal data flow problem. ** (cheese:9377): WARNING **: Internal data flow problem. ** (cheese:9377): WARNING **: Internal data flow problem. ** (cheese:9377): WARNING **: Internal data flow problem. ** (cheese:9377): WARNING **: Internal data flow problem. ** (cheese:9377): WARNING **: Internal data flow problem. ** (cheese:9377): WARNING **: Internal data flow problem. (cheese:9377): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed Segmentation fault ############################ lsusb ################################# Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 003: ID 17ef:1004 Lenovo Integrated Webcam Bus 003 Device 007: ID 0a5c:2110 Broadcom Corp. Bluetooth Controller Bus 003 Device 003: ID 147e:2016 Upek Biometric Touchchip/Touchstrip Fingerprint Sensor Bus 005 Device 003: ID 0461:4d22 Primax Electronics, Ltd ############################ uname -r################################ 2.6.38-ARCH #####################################################################
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance! If you can reproduce it while running under gdb (see http://live.gnome.org/GettingTraces/Details#gdb-not-yet-running for details about how to do this), that might help getting a better trace if you've already got debug packages installed.
I forgot to mention that I'm running Gnome 3...anyway here's the trace: ###############################stack trace#################################### Program received signal SIGSEGV, Segmentation fault. 0xb7479920 in vfprintf () from /lib/libc.so.6 (gdb) thread apply all bt
+ Trace 227161
Thread 1 (Thread 0xb6b477f0 (LWP 11062))
Can you please install debuginfo packages of glib, clutter, gtk3, cheese and provide updated traces, tia.
Hi, I think this is a dup of #647677
Thanks, Laurent. I'm marking this bug as a duplicate of #647677 that is now solved in git version. If it still happens with master, please reopen and provide a stacktrace. *** This bug has been marked as a duplicate of bug 647677 ***