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 683527 - navigation interface: Clutter-Gst-WARNING **: Failed to convert non-scaled coordinates for video-sink
navigation interface: Clutter-Gst-WARNING **: Failed to convert non-scaled co...
Status: RESOLVED INVALID
Product: clutter-gst
Classification: Other
Component: general
1.9.x
Other Linux
: Normal major
: ---
Assigned To: clutter-gst-maint
clutter-gst-maint
Depends on:
Blocks:
 
 
Reported: 2012-09-06 19:21 UTC by Tim-Philipp Müller
Modified: 2012-09-08 22:05 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Tim-Philipp Müller 2012-09-06 19:21:11 UTC 
Moving the mouse pointer in over the video window in totem yields loads of

  Clutter-Gst-WARNING **: Failed to convert non-scaled coordinates for video-sink

warnings. Don't know why clutter_actor_transform_stage_point() fails here, presumably because of "This function only works when the allocation is up-to-date, i.e. inside of paint()"?
Comment 1 Tim-Philipp Müller 2012-09-06 19:26:42 UTC 
This is with clutter 1.10.8 and clutter-gtk 1.2.0 if it matters.
Comment 2 Bastien Nocera 2012-09-07 10:14:21 UTC 
The version of clutter-gst is probably more important. Is it current master?
Comment 3 Tim-Philipp Müller 2012-09-07 10:29:45 UTC 
Yes, commit 28bf1d99fc45f2f8bc37c50aad21e0d55e9489d4

I should add that I'm seeing these with music (visualisations / cover art), not when playing movies.
Comment 4 Tim-Philipp Müller 2012-09-07 10:46:23 UTC 
Maybe also relevant: what gstreamer/gst-plugins-base version are you using ?

I was using git master. Reverting libvisual commit  8222ba16c8f671dc03e24e7b60e3e703046e58c1 in -base seems to have improved stability massively, and I haven't seen any warnings again after that (but it might not be related of course).
Comment 5 Tim-Philipp Müller 2012-09-08 22:05:51 UTC 
Haven't seen this again since I reverted the other commit, so I'm guessing it was the libvisual shader trampling over random memory.


commit 16c185bac6ca543acdbb65562c738195f986b4d7
Author: Tim-Philipp Müller <tim@centricular.net>
Date:   Sat Sep 8 22:56:56 2012 +0100

    libvisual: fix crashes and invalid writes in totem
    
    This reverts part of "visual: enable commented out code again."
    (commit 8222ba16c8f671dc03e24e7b60e3e703046e58c1).
    
    The shader code does indeed look broken (or rather,
    it makes assumptions that are not necessarily true here,
    namly that pixel stride is 4, for example), which
    makes totem very crashy and causes other weird behaviour.
    
    Also see https://bugzilla.gnome.org/show_bug.cgi?id=683527