No suitable decoder module for fourcc `XVID' [Solved]

[dosdo]

In http://www.debian-multimedia.org/ we can read this:

Code: Select all

18/06/2008 : Broken ffmpeg libraries : Since Debian use the same soname packages name than my packages, official packages (vlc, totem, etc...) linked against libavc* doesn't work with my libavc* packages. If you want to use vlc and friends you need to downgrade libavc* packages to the official packages. Beware : downgrading to these packages will remove all debian-multimedia packages who depends on libavc* To downgrade do the following : dpkg -l | grep 3:2008 for each package echoed do : apt-get install --reinstall <package>=0.svn20080206-8 0.svn20080206-8 is the unstable version and 0.cvs20070307-6 for testing (check with apt-cache for the current version). If somebody know a better solution tell me.

[cb474]

I had the same problem with vlc 0.8.6.e-2.3+b1 in debian-testing and solved it as follows:

-- Uninstall vlc and all its dependencies.
-- Remove all installed packages from the repository http://www.debian-multimedia.org with Synaptic.
-- Remove http://www.debian-multimedia.org from my sources.list.
-- Update the list of packages from Synaptic (apt-get update).
-- Reinstall vlc and its dependencies from Synaptic.
-- Empty the cache from the terminal ($ rm ~ / .vlc/cache/plugins- *. dat)

I used this method for solving the problem. But then what if I have some other packages (like Lame and Realplayer) that I want to use, which do come from debian-multimedia? My solution was to reenable the debian-multimedia repository and reinstall Lame and Realplayer and then disable debian-multimedia. But, of course, now I won't get updates to these packages, without constantly enabling and disabling the debian-multimedia repository.

If I leave debian-multimedia enabled, will vlc end up getting upgraded from that repositiory rather than from the official debian repositories? And then I'll end up with the problem all over again? What's the solution to this situation?

[bugmenot]

I had the same problem with vlc 0.8.6.e-2.3+b1 in debian-testing and solved it as follows:

-- Uninstall vlc and all its dependencies.
-- Remove all installed packages from the repository http://www.debian-multimedia.org with Synaptic.
-- Remove http://www.debian-multimedia.org from my sources.list.
-- Update the list of packages from Synaptic (apt-get update).
-- Reinstall vlc and its dependencies from Synaptic.
-- Empty the cache from the terminal ($ rm ~ / .vlc/cache/plugins- *. dat)

I used this method for solving the problem. But then what if I have some other packages (like Lame and Realplayer) that I want to use, which do come from debian-multimedia? My solution was to reenable the debian-multimedia repository and reinstall Lame and Realplayer and then disable debian-multimedia. But, of course, now I won't get updates to these packages, without constantly enabling and disabling the debian-multimedia repository.

If I leave debian-multimedia enabled, will vlc end up getting upgraded from that repositiory rather than from the official debian repositories? And then I'll end up with the problem all over again? What's the solution to this situation?

Try locking the packages in Synaptic. Once you re-enable the repository and reload the package info, check which packages synaptic wants to upgrade, then select them and go to Package > Lock Package. This should theoretically take care of the problem, allowing you to only install those packages which do not mess with ffmpeg et al.

[marceln]

Hello guys,

Just wanted to say that this problem appears on other platforms as well (slackware 12.1, in my case), because ffmpeg by default installs its headers in /usr/local/include/libavdevice, libavutil, etc. But vlc expects to find all the ffmpeg headers in the same location (/usr/local/include/ffmpeg, for instance).
This prevented vlc from compiling the avcodec plugin.
In my case I just created /usr/local/include/ffmpeg and copied all the headers there.

[graysky]

Man, I have the same problem w/ my vlc on lenny amd64: after I installed some stuff from the http://www.debian-multimedia.org repo, my vlc doesn't display xvid at all

I had the same problem with vlc 0.8.6.e-2.3+b1 in debian-testing and solved it as follows:

-- Uninstall vlc and all its dependencies.
-- Remove all installed packages from the repository http://www.debian-multimedia.org with Synaptic.
-- Remove http://www.debian-multimedia.org from my sources.list.
-- Update the list of packages from Synaptic (apt-get update).
-- Reinstall vlc and its dependencies from Synaptic.
-- Empty the cache from the terminal ($ rm ~ / .vlc/cache/plugins- *. dat)

When I attempted to remove some of the packages from the multimedia repo, synaptic told me it wanted to remove gnome! I'm not sure how to proceede since I know I don't wanna let it remove my desktop



Anyone?

BTW, vlc on my lenny box is 0.8.6h

[zyndarius]

Man, I have the same problem w/ my vlc on lenny amd64: after I installed some stuff from the http://www.debian-multimedia.org repo, my vlc doesn't display xvid at all

I had the same problem with vlc 0.8.6.e-2.3+b1 in debian-testing and solved it as follows:

-- Uninstall vlc and all its dependencies.
-- Remove all installed packages from the repository http://www.debian-multimedia.org with Synaptic.
-- Remove http://www.debian-multimedia.org from my sources.list.
-- Update the list of packages from Synaptic (apt-get update).
-- Reinstall vlc and its dependencies from Synaptic.
-- Empty the cache from the terminal ($ rm ~ / .vlc/cache/plugins- *. dat)

When I attempted to remove some of the packages from the multimedia repo, synaptic told me it wanted to remove gnome! I'm not sure how to proceede since I know I don't wanna let it remove my desktop



Anyone?

BTW, vlc on my lenny box is 0.8.6h

try to use apt-get install gnome to make apt-get to recognize the package as manually installed.

do the same with everything you are sure that must not be removed

and BTW, I am having the same problem in Debian Lenny amd64 with ver 0.8.6h

[indiefan23]

This is one of the most stupid comment ever...

VLC still support XVID perfectly.
The fact that YOUR distribution miscompiles VLC is NOT our fault.
If your VLC is correctly comiled, it has the FFmpeg plugin and support XVID.

Bug YOUR distribution. Not us.

Know what? This is a total BS response. Your error message says it's impossible to fix and is totally misleading. Because of your arrogance it still says that 3 years later and I'm struggling to get it fixed on my computer. Yea, it's my distro's fault that the links to your software from your site don't work. then you try to fix it and all you get is key board warriors talking smack instead of the help these forums are supposed to provide for situations like this. GTFO.

[Rémi Denis-Courmont]

Sorry but you're the one talking BS here, and that makes you badly ungrateful.

In this thread, VLC (and gstreamer too!) were broken because of the debian-multimedia garbage repository. And no, just removing the repository from the list does not fix the problem. It's not so easy once debian-multimedia messed up your Linux installation.

Neither the VideoLAN developers, nor your distirbution can fix problems caused by (your use of) debian-multimedia. We even have a PRETTY DAMN F*CKING CLEAR warning not to use Debian Multimedia EVER EVER at the very top of this forum. There is not much more we can do.

[indiefan23]

No. VLC works. Use a windows or a mac or a fedora to see...

"No suitable decoder module for fourcc 'XVID'" means the module cache is corrupted or the VLC is miscompiled and vlc-ffmpeg-plugin isn't there.

So, sorry, this isn't a VLC bug.

Good lord. Stop trying to deny responsibility. VLC spits out a decoder error so why not just pipe that into your UI instead of "this problem can't be fixed." I don't care who's fault it is, you guys can trap the error and provide help on how to fix it. Does it even matter? Standard use of your product on fedora crashes. It's reported and all you do is give people the run around.

You're totally full of it. Your software says its impossible to fix making it look like VLC purposefully controls something that prevents this operation. Stop making excuses and acting like I'm being a bad person for pointing out something that's obviously dumb is dumb. It's also obviously not a debian issue either since I get the same problems on Fedora, and I've seen other people having the same problems on other distros. It's pretty damn f*cking clear there's an issue of fragility of your releases if it's breaking everywhere, is it not?

Question: Did VLC mis-report a state as impossible to fix, that was actually possible to fix, and provide little to no information on the problem, rather discourage people from solving the issue?

Answer: Why yes it did, and the problem was reported to them years ago but everyone was too convinced of their awesome to do anything about it.

That's reality. If I'm grateful or ungrateful it still sucks and you pretending like it's not a problem is what's keeping it at that level.

[Jean-Baptiste Kempf]

No. VLC works. Use a windows or a mac or a fedora to see...

"No suitable decoder module for fourcc 'XVID'" means the module cache is corrupted or the VLC is miscompiled and vlc-ffmpeg-plugin isn't there.

So, sorry, this isn't a VLC bug.

Good lord. Stop trying to deny responsibility. VLC spits out a decoder error so why not just pipe that into your UI instead of "this problem can't be fixed." I don't care who's fault it is, you guys can trap the error and provide help on how to fix it. Does it even matter? Standard use of your product on fedora crashes. It's reported and all you do is give people the run around.

You're totally full of it. Your software says its impossible to fix making it look like VLC purposefully controls something that prevents this operation. Stop making excuses and acting like I'm being a bad person for pointing out something that's obviously dumb is dumb. It's also obviously not a debian issue either since I get the same problems on Fedora, and I've seen other people having the same problems on other distros. It's pretty damn f*cking clear there's an issue of fragility of your releases if it's breaking everywhere, is it not?

Question: Did VLC mis-report a state as impossible to fix, that was actually possible to fix, and provide little to no information on the problem, rather discourage people from solving the issue?

Answer: Why yes it did, and the problem was reported to them years ago but everyone was too convinced of their awesome to do anything about it.

That's reality. If I'm grateful or ungrateful it still sucks and you pretending like it's not a problem is what's keeping it at that level.

And of course, you are being banned of here. Topic is locked too.

We have no time to spend with people unable to read and understand basic english and who refuse to understand basic concepts...
Not to mention insults...