GNOME Bugzilla – Bug 496235
Crash after gst_type_find_factory_call_function
Last modified: 2007-12-27 21:57:14 UTC
Version: 2.18.3 What were you doing when the application crashed? playing the movie Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 69267456 vsize: 69267456 resident: 29769728 share: 18911232 rss: 29769728 rss_rlim: 4294967295 CPU usage: start_time: 1194897881 rtime: 40 utime: 37 stime: 3 cutime:1 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/totem' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208747408 (LWP 18342)] [New Thread -1237582960 (LWP 18345)] [New Thread -1221379184 (LWP 18344)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 177262
Thread 2 (Thread -1237582960 (LWP 18345))
----------- .xsession-errors (6 sec old) --------------------- (gnome-terminal:2977): Vte-WARNING **: No handler for control sequence `device-control-string' defined. (gnome-help:24325): Bonobo-CRITICAL **: bonobo_object_corba_objref: assertion `BONOBO_IS_OBJECT (object)' failed (gnome-help:25067): Bonobo-CRITICAL **: bonobo_object_corba_objref: assertion `BONOBO_IS_OBJECT (object)' failed (gnome-terminal:2977): Vte-WARNING **: No handler for control sequence `device-control-string' defined. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3c0005a (move - Ope) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: last_user_time (1194631931) is greater than comparison timestamp (631024034). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET Window manager warning: 0x4400003 (Totem Movi) appears to be one of the offending windows with a timestamp of 1194631931. Working around... Window manager warning: last_user_time (1194897853) is greater than comparison timestamp (896945401). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET Window manager warning: 0x4200003 (Totem Movi) appears to be one of the offending windows with a timestamp of 1194897853. Working around... Window manager warning: last_user_time (1194897881) is greater than comparison timestamp (896973663). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET Window manager warning: 0x4200003 (Totem Movi) appears to be one of the offending windows with a timestamp of 1194897881. Working around... --------------------------------------------------
Looks like a GStreamer bug; forwarding to the GStreamer guys. Unique stacktrace. Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!