After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 600313 - Visualisations stop updating after seek
Visualisations stop updating after seek
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
0.10.x
Other Linux
: Normal minor
: 0.10.26
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-11-01 15:45 UTC by Alberto Salvia Novella
Modified: 2009-12-24 12:54 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
The gdb stack trace obtained in the console after a visualisation crash (24.14 KB, text/plain)
2009-11-03 12:52 UTC, Alberto Salvia Novella 		Details
The gdb stack trace obtained in the console after a visualisation stop (27.89 KB, text/plain)
2009-11-03 12:56 UTC, Alberto Salvia Novella 		Details

Description Alberto Salvia Novella 2009-11-01 15:45:52 UTC 
Some times, high definition "GOOM: What a GOOM!" freezes when changing between windows. I will try to find out if the problem applies to other previews and qualities.

This bug has been found in Totem 2.28.1, under Ubuntu 9.10.

Large information can be found here: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/465498
Comment 1 Alberto Salvia Novella 2009-11-02 14:05:21 UTC 
The bug is preview type and quality independent, and appears instantly when moving the reproduction time bar.
Comment 2 Tim-Philipp Müller 2009-11-03 00:40:31 UTC 
When changing between windows? What windows do you mean?

Could you install libgstreamer0.10-0-dbg gstreamer0.10-plugins-base-dbg and gstreamer0.10-plugins-good-dbg and then provide a gdb stack trace from when it is frozen? With something like:


  $ pidof totem
  1234
  $ gdb -p 1234
  Welcome to the GNU debuger bla bla bla bla
  (gdb) thread apply all bt
  .... copy'n'paste output from here into the bug or attach it ...
  (gdb) kill
  (gdb) quit
Comment 3 Alberto Salvia Novella 2009-11-03 12:52:09 UTC 
Created attachment 146825 [details]
The gdb stack trace obtained in the console after a visualisation crash
Comment 4 Alberto Salvia Novella 2009-11-03 12:56:59 UTC 
Created attachment 146826 [details]
The gdb stack trace obtained in the console after a visualisation stop
Comment 5 Bastien Nocera 2009-11-03 12:59:52 UTC 
It's not a crash, the visualisations simply stop updating after a seek.

1. Load up a music file in totem
2. See that the visualisation is moving
3. Seek
4. Visualisation isn't moving anymore

Everything else works as expected.
Comment 6 Alberto Salvia Novella 2009-11-03 13:15:17 UTC 
(In reply to comment #5)
> It's not a crash, the visualisations simply stop updating after a seek.

That's true. Sorry for the mistake at comments 3 and 4.
Comment 7 Wim Taymans 2009-12-11 15:28:15 UTC 
commit f44d8c31de98a1521be1092f163a987eff0fd799
Author: Wim Taymans <wim.taymans@collabora.co.uk>
Date:   Fri Dec 11 16:26:00 2009 +0100

    bin: never skip a state change to PLAYING
    
    Never skip the state change to playing, even if the element is already in the
    right state. We need this because we also distribute the base_time while doing
    the state change and skipping this step would leave some elements without a new
    base_time.
    
    Fixes #600313
Comment 8 Bastien Nocera 2009-12-24 12:54:48 UTC 
(Reassign to gstreamer, as that's where the fix is)