On Tue 20 Mar 2018 at 13:47:42 (-0400), Dan Norton wrote: > On Tue, 20 Mar 2018 12:59:21 -0400 > Greg Wooledge <wool...@eeg.ccf.org> wrote: > > > On Tue, Mar 20, 2018 at 12:18:05PM -0400, Dan Norton wrote: > > > > * The output of "apt policy ffmpeg". > > > > > > ffmpeg: > > > Installed: 7:3.2.10-1~deb9u1 > > > Candidate: 7:3.2.10-1~deb9u1 > > > Version table: > > > *** 7:3.2.10-1~deb9u1 500 > > > 500 http://debian.gtisc.gatech.edu/debian stretch/main amd64 > > > Packages > > > 500 http://security.debian.org/debian-security > > > stretch/updates/main amd64 Packages > > > 100 /var/lib/dpkg/status > > > > > > > * The output of "aptitude why libopenal1". > > > > > > i ffmpeg Depends libavdevice57 (>= 7:3.2.10) > > > i A libavdevice57 Depends libopenal1 (>= 1.14) > > > > >From these, it looks like you have the stretch version of ffmpeg, > > >and > > a libopenal1 dependency that can be satisfied by the stretch version > > of libopenal1. > > > > If libopenal1 is not actually installed, then something is very wrong. > > Is it possible that you have the package "installed", but something > > else removed the library file? In that case, just reinstall the > > package: > > > > apt-get --reinstall install libopenal1 > > > > That did it - thanks, Greg! > > But what does this do that apt purge/install of ffmpeg does not?
You posted: # apt purge ffmpeg # apt autoremove # apt install ffmpeg but you didn't show your working. You should check out what happened by looking at /var/log/apt/history.log to see if libopenal1 was affected by this command sequence. For a start, other packages might depend on libopenal1, preventing its auto-removal. Then of course there's the investigation of why it wasn't installed correctly in the first place, and what was happening during the "several attempts" at installing ffmpeg. Cheers, David.