Talk:Browser plugins

From ArchWiki
Revision as of 06:55, 26 October 2013 by Lahwaacz (talk | contribs) (Permissions of /usr/bin/mozilla/ going to 700: rm old section: no longer relevant)
Jump to: navigation, search

Relocating Firefox specific content

Should this be moved back into Firefox? Dres 15:40, 16 January 2010 (EST)

The only Firefox-specific content I see is Browser Plugins#Plugins cannot be downloaded; the other troubleshooting tips are valid for other browsers (which tend to use the $MOZ_PLUGIN_PATH as well). This could easily be moved back.
-- pointone 13:04, 19 January 2010 (EST)
I can't personally gage on that, so I delegate to what's been pointed out. Dres 03:25, 23 January 2010 (EST)

plugin location

firefox (3.6.13) on arch 64 bit does look at /usr/lib/mozilla/plugins

instead of

~/mozilla/plugins/ or ~/.mozilla/plugins/

at least for I need to link to the correct /usr/lib/mozilla/plugins for it to work

Blue Tint Flash problem reloaded

To solve the blue tint problem I had to right-click a flash element already running and set (in "preferences") off the hw acceleration, otherwise I had blue tint regardless the libvdpau workaround.

Should this be added to the wiki?

Adobe Flash Player: Hardware acceleration

The Article states For hardware acceleration on Intel/AMD, you can use libvdpau-va-glAUR — VAAPI backend for VDPAU. For AMD you should also install xvba-videoAUR. Can someone clarify that? It's totally unclear to me, which ATI/AMD drivers are meant. I assume, I need xvba-video when I use the catalyst/fglrx driver. What about libvdpau-va-gl? Do I need this when using the open-source radeon-driver? Do I need this if you use catalyst? Or do I need this anyway? Holzhaus (talk) 21:33, 25 October 2013 (UTC)

See VA-API, I wonder why it isn't linked from this page... -- Lahwaacz (talk) 06:48, 26 October 2013 (UTC)