Your message dated Wed, 11 Jun 2014 18:01:16 +0200
with message-id <[email protected]>
and subject line Re: Bug#664700: libva1: please search dri module in
/usr/lib/{<triplet>/, }dri
has caused the Debian Bug report #664700,
regarding libva1: please search dri module in /usr/lib/{<triplet>/,}dri
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
664700: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664700
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libva1
Version: 1.0.15-4
Severity: normal
Hi,
please use a search path for the DRI modules that contains both
/usr/lib/<triplet>/dri
/usr/lib/dri
While we can (hopefully) fix the Debian packages to ship the files in
the multiarch locations, the multiarch move "breaks" any third-party
(probably proprietary) software/installer/... that is not multiarch
aware. Therefore "plugins" should be searched in both locations.
So far the following problems have been reported:
xvba-va:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664487
fglrx + vainfo:
$ vainfo
libva: VA-API version 0.32.0
Xlib: extension "XFree86-DRI" missing on display ":0".
libva: va_getDriverName() returns 0
libva: Trying to open /usr/lib/x86_64-linux-gnu/dri/fglrx_drv_video.so
libva: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit
I'm not sure if I can move dri/fglrx_drv_video.so around - it is loaded
from the fglrx driver (a non-free blob) using the hardcoded path
/usr/lib/dri ... (and the last time I tried to use symlinks (although in
a different context) the fglrx blob used lstat() and complained about
world writable files ...)
Andreas
--- End Message ---
--- Begin Message ---
On 2014-05-10 14:10:33, Sebastian Ramacher wrote:
> > please use a search path for the DRI modules that contains both
> > /usr/lib/<triplet>/dri
> > /usr/lib/dri
> > While we can (hopefully) fix the Debian packages to ship the files in
> > the multiarch locations, the multiarch move "breaks" any third-party
> > (probably proprietary) software/installer/... that is not multiarch
> > aware. Therefore "plugins" should be searched in both locations.
> >
> > So far the following problems have been reported:
> >
> > xvba-va:
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664487
> >
> > fglrx + vainfo:
> >
> > $ vainfo
> > libva: VA-API version 0.32.0
> > Xlib: extension "XFree86-DRI" missing on display ":0".
> > libva: va_getDriverName() returns 0
> > libva: Trying to open /usr/lib/x86_64-linux-gnu/dri/fglrx_drv_video.so
> > libva: va_openDriver() returns -1
> > vaInitialize failed with error code -1 (unknown libva error),exit
> >
> > I'm not sure if I can move dri/fglrx_drv_video.so around - it is loaded
> > from the fglrx driver (a non-free blob) using the hardcoded path
> > /usr/lib/dri ... (and the last time I tried to use symlinks (although in
> > a different context) the fglrx blob used lstat() and complained about
> > world writable files ...)
>
> I'm currently going through some old bug reports and stumbled upon this
> one. I'm wondering if there's still something left to do here. All the
> DRI modules seem to be in the multi arch path nowadays and #664487 has
> been fixed two years ago.
>
> Since there doesn't appear to be a bug present anymore I'm leaning
> towards closing the bug. What do you think?
Closing the bug. If you think there is something to be fixed, please
reopen the bug with further information.
Cheers
--
Sebastian Ramacher
signature.asc
Description: Digital signature
--- End Message ---
