[totem] youtube.com plugin hangs the player at every start and end of the video clip

[Miroslav Hadzhiev]

Binary package hint: totem

When a video clip is start in Totem through the YouTube Browser plug-in, the player hangs for 6-8 seconds at every start and end of video clips being watched (not stopping it manually but the real end of the clip, so the clip is stopped automatically by Totem).

ProblemType: Bug
Architecture: amd64
Date: Thu Dec 3 15:14:03 2009
DistroRelease: Ubuntu 9.10
Package: totem 2.28.2-0ubuntu3
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
SourcePackage: totem
Uname: Linux 2.6.31-15-generic x86_64
XsessionErrors:
 (gnome-settings-daemon:1649): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1649): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:1688): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:1723): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-panel:1687): Gdk-WARNING **: /build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkdrawable-x11.c:952 drawable is not a pixmap or window

[Pedro Villavicencio (pedro)]

Please try to obtain a backtrace of that hang following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[Miroslav Hadzhiev (xtigyro)]

"gdb-totem.txt" created as described in https://wiki.ubuntu.com/DebuggingProgramCrash and in https://wiki.ubuntu.com/Backtrace

I've run the program twice. You'll see in the debug text file.

[Pedro Villavicencio (pedro)]

file is almost empty, could you please try again? Thanks.

[Victor Vargas (kamus)]

MIro, please could you test if this behaviour is still occurring in latest release of totem included in Ubuntu Maverick? Thanks.

[Omer Akram (om26er)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.