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 325755 - Seek bar sometimes shows erratic behaviour
Seek bar sometimes shows erratic behaviour
Status: RESOLVED DUPLICATE of bug 319298
Product: rhythmbox
Classification: Other
Component: User Interface
0.9.x
Other Linux
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-01-04 11:23 UTC by Sebastien Bacher
Modified: 2006-01-28 13:53 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sebastien Bacher 2006-01-04 11:23:49 UTC
This bug has been opened here: http://bugzilla.ubuntu.com/show_bug.cgi?id=21850

"(gst 0.10 RH)

The seek bar doesn't work very well/smoothly. 
Quite often (say at least once in 20 manipulations), when I move the seek bar
with the mouse, it will exbihit some kind of glitch, during a split a second.
Hard to describe... for example, say the button is in the middle, and I move it
to the right. Well, sometimes, the button will decide to "jump" to the far left,
or far right, or anywhere, then eventually come back where I meant to move it to.
Sometimes, it doesn't even want to go where I want it to, and the cursor/button
(don't know how to call it...) ends up an inch backwards.
Also, when it does this, often, it will stay mute for like 2 seconds, before
resuming the playback.

I first noticed this problem when playing back a podcast episode, and since they
are mp3 files, I thought maybe it's a bug the "ugly" plug-in. So I tried with
OGG songs, and the problem is there as well. Also, I tried both MP3 and OGG with
Totem-gst0.10, and couldn't reproduce the problem neither with OGG or MP3. So it
really seems to be a RH specific problem..."
Comment 1 Alex Lancaster 2006-01-28 13:53:39 UTC
Sounds like a duplicate of either bug #319298.  Closing, please followup there.




*** This bug has been marked as a duplicate of 319298 ***