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 694540 - No way to disable visualisations in totem-mozilla
No way to disable visualisations in totem-mozilla
Status: RESOLVED DUPLICATE of bug 727761
Product: totem
Classification: Core
Component: Browser plugin (obsolete)
3.6.x
Other Linux
: Normal enhancement
: ---
Assigned To: totem-browser-maint
totem-browser-maint
Depends on:
Blocks:
 
 
Reported: 2013-02-23 17:05 UTC by Fabio
Modified: 2014-04-11 09:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
patch to disable (637 bytes, patch)
2013-02-23 17:05 UTC, Fabio
none Details | Review

Description Fabio 2013-02-23 17:05:21 UTC
Created attachment 237248 [details] [review]
patch to disable 

Downstream at launchpad:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/825580


The totem-mozilla plugin doesn't provide any way to disable visualisations, even if you disable them from the main totem menu.

This means that all audio streams that are shown in the plugin have the default 'goom' visualisation, which is very processor intensive and makes slow machines very sluggish.

I've attached a patch which disables visualisations completely. It would be nice if this could be the default behaviour in ubuntu, at least until upstream provides some way of manually disabling it, for a number of reasons:

1) visualisations like this needlessly waste power, especially on battery
2) visualisations make sound playback on slow computers choppy, and make the computer sluggish
3) no-one really needs visualisations at all.

Thanks.
Comment 1 Bastien Nocera 2014-04-11 09:04:46 UTC
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 bug 727761 ***