Red Hat Bugzilla – Bug 804435
RFE: please put the vegas plugin into a separate subpackage to avoid conflicts with the original Adobe flashplayer
Last modified: 2012-05-15 23:19:19 EDT
Description of problem:
The library /usr/lib64/mozilla/plugins/libtotem-vegas-plugin.so from totem-mozplugin registers with the same name and version as the original flash plugin.
Not only that it doesn't work for example for playing youtube video, but it also knocks-out the original Adobe Flash plugin if it is installed.
I believe that there should be some clear way how to recognize this "Shockwave Flash" is actually not a "Shockwave", but Totem Vegas.
Also only way how to disable is to uninstall the totem-mozplugin, which removes other useful plugins as well.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install firefox
2. Install totem-mozplugin
3. Install original adobe flash from http://get.adobe.com/flashplayer/
Flash objects will not work. For example youtube videos.
Flash objects should be using original flash plugin from adobe if it is installed
workaround to make Flash plugin working in Fedora 17 Alpha is to remove the totem-mozplugin
rpm -e totem-mozplugin
I've been hitting this problem too, and the answer to me seems easy, since the totem vegas plugin conflicts with the original flash plugin and some people want to use the original flash plugin, while using the other totem plugins for for example mms streams, the vegas plugin should be in its own package. I've updated $summary to reflect this.
For other people reading along bug 806605 has an interesting workaround, mkdir /etc/totem and place the file from attachment 574375 [details] there.
*** Bug 806605 has been marked as a duplicate of this bug. ***
FWIW this was one of the first things that I hit on F17 Beta RC3. I don't think breaking flash by default is a good thing to do, even though I understand that it is not supported. Please split off the vegas plugin until it is a ready replacement.
As a workaround, I have gone into google chrome, about:plugins and disabled:
Name: Shockwave Flash
Version: 11.1 r102
and gone into Firefox and disabled one of the Shockwave Flash plugins. Strangely, firefox is reporting both plugins at the same version, so I had to use trial-and-error to ensure I disabled the correct Shockwave plugin.
After I disabled them, flash works.
Created attachment 582406 [details]
Split off vegas
Here is a patch to split it off.
Want/need an ACK from Bastien before pushing it.
*** Bug 819176 has been marked as a duplicate of this bug. ***
*** Bug 812203 has been marked as a duplicate of this bug. ***
This is a serious issue. Can we bump the priority please? The totem flash plugin CANNOT DISPLAY EVERYTHING THAT THE ADOBE FLASH PLUGIN CAN. I encountered a flash game, for example, that simply wouldn't work in the totem plugin. Shipping a plugin that is going to override another plugin that works properly, and that is unable to do everything that other plugin can actually do, seems like a pretty darn good way to anger and frustrate users and damage the Fedora user experience.
totem-3.4.1-3.fc17 has been submitted as an update for Fedora 17.
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing totem-3.4.1-3.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
Doesn't fix this issue for me
(In reply to comment #11)
> Doesn't fix this issue for me
That is weird:
[hans@localhost ~]$ rpm -ql totem-mozplugin
No more vegas plugin, and:
Shows a separate totem-mozplugin-vegas package. Did you perhaps accidentally install the new -vegas package?
-1 NTH as this can be fixed with an update and there is only a small effect on live images.
+1 NTH, I'd rather have this included in the base repo to avoid changing user experience (removing flash video support) with a 0-day update.
Actually LiveCDs benefit from the old totem, because you can play YouTube from them. But I still think +1 NTH is proper due to the reasons stated in comment 14. Flash plugin will be installed by lots of Fedora users, maybe even sooner then doing a system update. There might be a lot of confusion and unneeded bug reports when Flash doesn't work at all. Other users might be thrilled YouTube works without flash, until they update their system and it's gone. This update seems pretty safe and should not break anything.
(In reply to comment #12)
You're right, I was using totem-mozplugin-3.4.1-2.fc17.x86_64, not totem-mozplugin-3.4.1-3.fc17.x86_64.
+1 NTH to keep behaviour consistent between initial install and post-update.
(In reply to comment #15)
> Actually LiveCDs benefit from the old totem, because you can play YouTube from
Not without installing gstreamer codecs .. OTOH with the new totem youtube will fallback to HTML5+webm for most (newer) videos so the new totem will get you youtube while the old will not ;)
+1 NTH, change is pretty isolated and safe and has a good result. That makes it accepted.
Fedora Bugzappers volunteer triage team
totem-3.4.1-3.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.