All right, thank you for the hints. I will run Valgrind again with headless VLC as soon as I get to my home laptop.
I am also not sure that one cannot find VLC 1.1.x for Lucid in certain PPA. Anyway I am able to build VLC myself with required build settings in the case it will fix the bug. Mon, 12 Jul 2010 08:17:02 -0000 письмо от Rémi Denis-Courmont <575...@bugs.launchpad.net>: >The only way to prevent the offending plugin(s) from loading is to >remove it, which means remove kdelibs5, which means remove KDE. I am not >aware of any way to manually blacklist some Qt4 plugins otherwise. > >The VLC blacklisting is more-or-less a hack and requires VLC-side >infrastructure not available in VLC 1.0.x. To my understanding, Ubuntu >won't backport VLC 1.1 to Lucid. So essentially, it's game over. > >That said, it might also be that the valgrind trace is wrong and the >leak is somewhere else. That can be checked by running a headless VLC >(vlc -I dummy) from the command line, which definitely won't use any Qt4 >or KDE thing. > С наилучшими пожеланиями, Григорий Речистов. Best regards, Grigory Rechistov -- memory leak https://bugs.launchpad.net/bugs/575460 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
