GNOME Bugzilla – Bug 598804
crash in Movie Player: Searching some video wit...
Last modified: 2010-04-15 15:45:04 UTC
Version: 2.28.1 What were you doing when the application crashed? Searching some video with youtube plugin The search progress bar was pulsing, changed term and hit enter a few times then it crashed. Distribution: Gentoo Base System release 2.0.1 Gnome Release: 2.26.3 2009-09-18 (Gentoo) BugBuddy Version: 2.28.0 System: Linux 2.6.30-gentoo-r6 #1 SMP Sun Sep 6 13:03:09 CEST 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10603901 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: canberra-gtk-module, globalmenu-gnome, gnomebreakpad Memory status: size: 631349248 vsize: 631349248 resident: 47960064 share: 22482944 rss: 47960064 rss_rlim: 18446744073709551615 CPU usage: start_time: 1255817101 rtime: 119 utime: 111 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/totem' [?1034h[Thread debugging using libthread_db enabled] [New Thread 0x7fd0fc45d750 (LWP 27662)] [New Thread 0x7fd0dc907910 (LWP 27676)] [New Thread 0x7fd0e736a910 (LWP 27666)] [New Thread 0x7fd0e85c3910 (LWP 27665)] [New Thread 0x7fd0e920c910 (LWP 27664)] 0x00007fd0f87a6a4f in __libc_waitpid (pid=27677, stat_loc=0x7fff543417a0, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 in ../sysdeps/unix/sysv/linux/waitpid.c
+ Trace 218387
Thread 1 (Thread 0x7fd0fc45d750 (LWP 27662))
---- Critical and fatal warnings logged during execution ---- ** GLib-GIO **: g_simple_async_result_set_from_error: assertion `error != NULL' failed ** GLib **: g_error_free: assertion `error != NULL' failed Output of custom script "/usr/libexec/totem/totem-bugreport.py": gst-typefind-0.10 version 0.10.24 GStreamer 0.10.24 http://packages.gentoo.org/package/media-libs/gstreamer Listened to a "" file on 2009-10-13T02:16:37 ----------- .xsession-errors (298 sec old) --------------------- (epiphany:6331): GLib-GObject-WARNING **: invalid (NULL) pointer instance (epiphany:6331): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed evolution-alarm-notify-Message: Alarm callback! evolution-alarm-notify-Message: Process alarm with trigger 1255816800 evolution-alarm-notify-Message: alarm.c:249: Requested removal of nonexistent alarm! evolution-alarm-notify-Message: Setting timeout for 86396 1255903200 1255816804 evolution-alarm-notify-Message: Mon Oct 19 00:00:00 2009 evolution-alarm-notify-Message: Sun Oct 18 00:00:04 2009 ** (totem:27307): WARNING **: totem_publish_plugin_activate: Impossible de créer le client Avahi : An unexpected D-Bus error occured (totem:27307): libepc-WARNING **: epc_service_monitor_constructed: Cannot create service type browser for '_totem._sub._easy-publish-http._tcp': Impossible de créer le client Avahi : An unexpected D --------------------------------------------------
Here is what was printed on the terminal when totem crashed: $ totem libgdata-Message: Unhandled XML in GDataYouTubeVideo: <georss:where><gml:Point><gml:pos>52.47148895263672 -1.9003772735595703</gml:pos></gml:Point></georss:where> libgdata-Message: Unhandled XML in GDataYouTubeVideo: <georss:where><gml:Point><gml:pos>52.47151565551758 -1.9004631042480469</gml:pos></gml:Point></georss:where> (totem:27662): GLib-GIO-CRITICAL **: g_simple_async_result_set_from_error: assertion `error != NULL' failed (totem:27662): GLib-CRITICAL **: g_error_free: assertion `error != NULL' failed ** libgdata:ERROR:gdata-service.c:955:gdata_service_query_finish: code should not be reached 41 ../sysdeps/unix/sysv/linux/waitpid.c: No such file or directory. May it be related to bug #598801 or bug #598798 ?
we're having a similar issue on https://bugs.edge.launchpad.net/ubuntu/+source/totem/+bug/516882
Sorry for the late response; this bug somehow completely slipped under my radar. It should be fixed in libgdata 0.6.4. Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of bug 613529 ***