<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [regression?][nv34] adobe flash + firefox -> DATA_ERROR" href="https://bugs.freedesktop.org/show_bug.cgi?id=73358#c27">Comment # 27</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [regression?][nv34] adobe flash + firefox -> DATA_ERROR" href="https://bugs.freedesktop.org/show_bug.cgi?id=73358">bug 73358</a> from <a class="email" href="mailto:ronald645@gmail.com" title="Ronald <ronald645@gmail.com>"> Ronald</a> <pre>(In reply to <a href="show_bug.cgi?id=73358#c26">comment #26</a>) > I think you meant to say LD_LIBRARY_PATH=./lib The vdpau_nouveau.so was sitting in mesa/lib/gallium. But it turns out that even with your suggestion it would not load. What I did was this: - vdpau_nouveau.so was sitting in ~/mesa/lib/gallium - cd ~/mesa/lib/gallium - git clone git://people.freedesktop.org/~aplattner/libvdpau - ./configure --with-module-dir=~/mesa/lib/gallium - cd .. - ln -s -t . libvdpau/src/.libs/libvdpau.so - ln -s libvdpau.so libvdpau.so.1 - ln -s libvdpau.so libvdpau.so.1.0.0 - cd ~/mesa/lib/gallium And reran the tests. Same garbled screen as in <a href="show_bug.cgi?id=73358#c23">comment #23</a>. Sorry. I went to verify I did thinks right so I ran inotifywait on the system vdpau and my own build of vdpau: [gebruiker@delta ~]$ inotifywait -m ~/mesa/lib/gallium/libvdpau_nouveau.so Setting up watches. Watches established. mesa/lib/gallium/libvdpau_nouveau.so OPEN mesa/lib/gallium/libvdpau_nouveau.so ACCESS mesa/lib/gallium/libvdpau_nouveau.so CLOSE_NOWRITE,CLOSE mesa/lib/gallium/libvdpau_nouveau.so OPEN mesa/lib/gallium/libvdpau_nouveau.so ACCESS mesa/lib/gallium/libvdpau_nouveau.so CLOSE_NOWRITE,CLOSE ( other terminal ) [gebruiker@delta mesa]$ inotifywait -rm /usr/lib/vdpau/ Setting up watches. Beware: since -r was given, this may take a while! Watches established. ( empty -> not used -> good! ) So I can fairly confidently say that your patch did not fix the issue. > Also, since I'm pretty sure that this is all caused by vdpau, in order for > it to use the libvdpau_nouveau.so that you generated, you need to have a > libvdpau in that *same* lib directory. Otherwise it'll get loaded from a > fixed path. (You can run strace -f -e open to confirm.) Yes, thanks for the tip. I used strace and inotifywait. > Mind testing out <a href="http://patchwork.freedesktop.org/patch/18063/">http://patchwork.freedesktop.org/patch/18063/</a> ? (Note, > again, make _sure_ that the 'new' version of libvdpau_nouveau.so is being > loaded, not the old one.) Yes, you suggested this in <a href="show_bug.cgi?id=73358#c19">comment #19</a> (or did you accidentaly ment another patch?)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>