Bug 8398 - gnome-terminal shows Failed to open VDPAU backend libvdpau_nouveau.so: cannot open shared objectfile: File or directory doesn't exist when running Firefox
Summary: gnome-terminal shows Failed to open VDPAU backend libvdpau_nouveau.so: cannot...
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: x86_64 Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-15 16:41 CET by Kristoffer Grundström
Modified: 2013-08-28 17:21 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Kristoffer Grundström 2012-12-15 16:41:07 CET 
Description of problem: Using 3.3.8-desktop-2.mga2 as kernel, when using firefox-10.0.11-1.mga2 via gnome-terminal together with the flag -d I see this error:

Failed to open VDPAU backend libvdpau_nouveau.so: cannot open shared objectfile: File or directory doesn't exist

Version-Release number of selected component (if applicable): 10.0.11

How reproducible: Everytime.

Steps to Reproduce:
1. Use 3.3.8-desktop-2 as kernel.
2. Either disable or delete any Testing-medias for your mirror or mirrorlist.
3. Make sure you're fully updated.
4. Login to Gnome.
5. Open gnome-terminal.
6. Type firefox <any url to a site that plays any P2P-material such as football-games> -d & press Enter.
7. When Firefox opens that page, that's when you'll see that message.
Manuel Hiebel 2012-12-25 14:46:06 CET

Severity: normal => minor

Comment 1 Samuel Verschelde 2013-08-28 17:21:01 CEST 
This is not a gnome-terminal bug, just a message from firefox, that comes from the flashplayer plugin, so not from Mageia. You can report the bug to adobe but they discontinued support for linux so that would be a waste of time.

Status: NEW => RESOLVED
CC: (none) => stormi
Resolution: (none) => INVALID
Source RPM: gnome-terminal => (none)
Note You need to log in before you can comment on or make changes to this bug.