[Bug 969579] Re: xvba-va-driver broken

2012-04-21 Thread Krzysztof Klimonda
Package installs libraries in the wrong location, not taking multiarch into consideration. It's too late in the cycle to sync with Debian (fixing bug #809765) because the debian package FTBFS due to the missing header file. But we can fix the current package so it installs libraries in the correct

[Bug 969579] Re: xvba-va-driver broken

2012-04-21 Thread Launchpad Bug Tracker
This bug was fixed in the package xvba-video - 0.7.8-1ubuntu3 --- xvba-video (0.7.8-1ubuntu3) precise; urgency=low * debian/rules, debian/install.in: - Add support for the multiarch paths to the packaging and install VA-API driver in the correct location. (LP: #969579)

[Bug 969579] Re: xvba-va-driver broken

2012-04-17 Thread RussianNeuroMancer
Do you try workaround from bug 800022? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969579 Title: xvba-va-driver broken To manage notifications about this bug go to:

[Bug 969579] Re: xvba-va-driver broken

2012-04-17 Thread Miguel
Thank you for pointing me to that other bug, I seem to have solved the problem using the following workaround: 1)create a symlink with sudo ln -s /usr/lib/va/drivers/fglrx_drv_video.so /usr/lib/x86_64-linux- gnu/dri/fglrx_drv_video.so 2)Add the line LIBVA_DRIVER_NAME=fglrx to /etc/environment.

[Bug 969579] Re: xvba-va-driver broken

2012-04-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xvba-video (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969579 Title:

[Bug 969579] Re: xvba-va-driver broken

2012-03-30 Thread Miguel
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969579 Title: xvba-va-driver broken To manage notifications about this bug go to: