GNOME Bugzilla – Bug 335123
totem crashes every time when trying to add an additional item to the playlist
Last modified: 2006-03-20 12:33:22 UTC
Steps to reproduce: 1. open totem, add one or more items to playlist 2. play playlist 3. press "Add..."-Button in playlist or open movie -> open file ... Stack trace: Debugging Information: 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) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1226180944 (LWP 14972)] [New Thread -1327576144 (LWP 14986)] [New Thread -1306227792 (LWP 14982)] [New Thread -1297835088 (LWP 14981)] [New Thread -1287554128 (LWP 14980)] [New Thread -1275061328 (LWP 14979)] [New Thread -1266398288 (LWP 14978)] [New Thread -1258005584 (LWP 14975)] [New Thread -1245127760 (LWP 14974)] [New Thread -1237124176 (LWP 14973)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 67053
Other information: totem was started from command-line, maybe the messages are helpful: user ~ $ totem (totem:14925): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (totem:14925): Gtk-CRITICAL **: gtk_object_sink: assertion `GTK_IS_OBJECT (object)' failed (totem:14925): Gtk-CRITICAL **: gtk_file_filter_get_name: assertion `GTK_IS_FILE_FILTER (filter)' failed (totem:14925): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (totem:14925): Gtk-CRITICAL **: gtk_object_sink: assertion `GTK_IS_OBJECT (object)' failed
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. Already fixed in 1.2.2 *** This bug has been marked as a duplicate of 324240 ***