Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 531822 - www-client/firefox-34.0.5 with www-plugins/adobe-flash fails to play YouTube videos / rectangle is black and unresponsive
Summary: www-client/firefox-34.0.5 with www-plugins/adobe-flash fails to play YouTube ...
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Mozilla Gentoo Team
URL: https://www.youtube.com/watch?v=CMCWb...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-06 16:49 UTC by Martin von Gagern
Modified: 2014-12-06 17:18 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
emerge --info (www-client:firefox-bin-34.0.5.emerge--info,7.86 KB, text/plain)
2014-12-06 16:56 UTC, Martin von Gagern 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin von Gagern 2014-12-06 16:49:39 UTC 
Firefox 34 doesn't seem to play Flash videos on You Tube. The player element stays black. This is with both www-client/firefox-34.0.5 and www-client/firefox-bin-34.0.5. I'm still building www-client/firefox-34.0.5-r1 but judging from the change log I don't expect a relevant change. www-client/firefox-bin-31.3.0 on the other hand works as it should. Flash is www-plugins/adobe-flash-11.2.202.424.
Comment 1 Martin von Gagern 2014-12-06 16:56:40 UTC 
Created attachment 391074 [details]
emerge --info
Comment 2 Jeroen Roovers (RETIRED) gentoo-dev 2014-12-06 17:03:50 UTC 
Works fine here. Does the console log any interesting errors?
Comment 3 Martin von Gagern 2014-12-06 17:18:33 UTC 
Sorry, the Flash Block addon was to blame, even after disabling it using its tool bar button. Disabling it on the Addons page made things work again, and also showed me that Flash Block is officially incompatible with this version of FF, except that it was still available due to my use of the Compatibility Reporter Addon. So it's my own fault, in a number of ways. Sorry for the noise!