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 504919 - The sliders remain following the mouse cursor even after releasing the mouse button
The sliders remain following the mouse cursor even after releasing the mouse ...
Status: RESOLVED DUPLICATE of bug 477529
Product: totem
Classification: Core
Component: Movie player
unspecified
Other Linux
: Normal normal
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2007-12-21 19:19 UTC by webplate
Modified: 2007-12-23 11:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description webplate 2007-12-21 19:19:07 UTC
When clicking and remaining clicked on a slider it's usually possible to move it !until! the mouse button is released. Nevertheless the sliders (both for video position and for volume control) remains linked to my cursor moves and I have to click one more time on the slider for it to stop following my movements. This only occurs when the mouse cursor leaves the slider widget area while the mouse button remains clicked.

I first thought of a GTK bug but the sliders in other applications are behaving correctly, so it seems to be totem related.

I'm not sure of the clarity of my description (sorry for my English).
But it's quite a usability issue on my Ubuntu Gutsy.
Comment 1 Bastien Nocera 2007-12-21 23:42:59 UTC
Which version of GTK+ and Totem are you using?
Comment 2 webplate 2007-12-22 17:58:25 UTC
(In reply to comment #1)
> Which version of GTK+ and Totem are you using?
> 

I'm using totem 2.20.0 whith libgtk 2.12.0
Comment 3 Bastien Nocera 2007-12-23 11:06:13 UTC
Upgrade GTK+ and Totem to fix this.

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.


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