Re: Missing Shared Object File for ffmpeg
On Wed, 21 Mar 2018 12:46:06 -0500 David Wright wrote: > On Tue 20 Mar 2018 at 21:29:49 (-0400), Dan Norton wrote: > > On Tue, 20 Mar 2018 18:35:48 -0500 > > David Wright wrote: > > > > > On Tue 20 Mar 2018 at 18:41:55 (-0400), Dan Norton wrote: > > > > On Tue, 20 Mar 2018 13:42:24 -0500 > > > > David Wright wrote: > > > > > > > > > On Tue 20 Mar 2018 at 13:47:42 (-0400), Dan Norton wrote: > > > > > > On Tue, 20 Mar 2018 12:59:21 -0400 > > > > > > Greg Wooledge 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 ffmpegDepends 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. > > > > > > > > The broken system was installed in December 2017. Looking at > > > > all the logs in /var/log/apt/history* (extracting the ones that > > > > were archived) and running: > > > > dan@deb9:~/apt.logs$ grep -rnw '.' -e 'libopenal1' | less > > > > ...there is one hit, other than today's --reinstall and that is > > > > an install: > > > > > > > > Start-Date: 2017-12-17 21:29:03 > > > > Commandline: /usr/sbin/synaptic > > > > Requested-By: dan (1200) > > > > Install: [...] > > > > libopenal1:amd64 (1:1.17.2-4+b2, automatic), # e pluribus unum > > > > [...] > > > > > > > > > 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. > > > > > > > > > > > > > Apparently nothing during these attempts involved libopenal1, > > > > according to the logs in /var/log/apt/ - is there anywhere else > > > > that could shed light on this? > > > > > > Is it still marked as Automatic? Particularly if you try to > > > install it, it will lose that flag (all this is IIRC). Further > > > use of that command sequence would have no effect in that case. > > > > > > > root@deb9:~# apt search libopenal1 > > Sorting... Done > > Full Text Search... Done > > libopenal1/stable,now 1:1.17.2-4+b2 amd64 [installed,automatic] > > [...] > > > > > The dependency is via another package. I've found that removing a > > > package doesn't always reach down to all the Automatic packages > > > beneath it. This is easily demonstrated by installing a package > > > with multiple dependencies (in depth) and then immediately purging > > > it. > > > > > > But none of this gets down to the root of the problem (why the > > > installed package didn't provide the library). Perhaps it might > > > be worth occasionally running > > > # debsums -l > > > # debsums -ca > > > to check things over. There's also dpkg -V. > > > > > > > root@deb9:~# debsums -l > > root@deb9:~# > > > > root@deb9:~# debsums -ca 2>/home/dan/debsums.out > > /etc/lvm/lvm.conf > > ...producing 958.9 kB of missing file messages in debsums.out, none > > mention libopenal1. > > Interesting difference between your systems and mine: > > wheezy: > > # debsums -l > # debsums -ca > /etc/apt-cacher
Re: Missing Shared Object File for ffmpeg
On Tue 20 Mar 2018 at 21:29:49 (-0400), Dan Norton wrote: > On Tue, 20 Mar 2018 18:35:48 -0500 > David Wright wrote: > > > On Tue 20 Mar 2018 at 18:41:55 (-0400), Dan Norton wrote: > > > On Tue, 20 Mar 2018 13:42:24 -0500 > > > David Wright wrote: > > > > > > > On Tue 20 Mar 2018 at 13:47:42 (-0400), Dan Norton wrote: > > > > > On Tue, 20 Mar 2018 12:59:21 -0400 > > > > > Greg Wooledge 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 ffmpegDepends 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. > > > > > > The broken system was installed in December 2017. Looking at all the > > > logs in /var/log/apt/history* (extracting the ones that were > > > archived) and running: > > > dan@deb9:~/apt.logs$ grep -rnw '.' -e 'libopenal1' | less > > > ...there is one hit, other than today's --reinstall and that is an > > > install: > > > > > > Start-Date: 2017-12-17 21:29:03 > > > Commandline: /usr/sbin/synaptic > > > Requested-By: dan (1200) > > > Install: [...] > > > libopenal1:amd64 (1:1.17.2-4+b2, automatic), # e pluribus unum > > > [...] > > > > > > > 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. > > > > > > > > > > Apparently nothing during these attempts involved libopenal1, > > > according to the logs in /var/log/apt/ - is there anywhere else > > > that could shed light on this? > > > > Is it still marked as Automatic? Particularly if you try to install > > it, it will lose that flag (all this is IIRC). Further use of that > > command sequence would have no effect in that case. > > > > root@deb9:~# apt search libopenal1 > Sorting... Done > Full Text Search... Done > libopenal1/stable,now 1:1.17.2-4+b2 amd64 [installed,automatic] > [...] > > > The dependency is via another package. I've found that removing a > > package doesn't always reach down to all the Automatic packages > > beneath it. This is easily demonstrated by installing a package > > with multiple dependencies (in depth) and then immediately purging > > it. > > > > But none of this gets down to the root of the problem (why the > > installed package didn't provide the library). Perhaps it might > > be worth occasionally running > > # debsums -l > > # debsums -ca > > to check things over. There's also dpkg -V. > > > > root@deb9:~# debsums -l > root@deb9:~# > > root@deb9:~# debsums -ca 2>/home/dan/debsums.out > /etc/lvm/lvm.conf > ...producing 958.9 kB of missing file messages in debsums.out, none > mention libopenal1. Interesting difference between your systems and mine: wheezy: # debsums -l # debsums -ca /etc/apt-cacher-ng/security.conf (.deb cache) /etc/console-setup/remap.inc (VC key definitions) /etc/exim4/passwd.client (email submission at home) /etc/kbd/config (key repeat rate and blanking) /etc/timidity/timidity.cfg (waveforms) # # dpkg too old for -V jessie: # debsums -l # debsums -ca /etc/issue (prompt contains ti
Re: Missing Shared Object File for ffmpeg
On Tue, 20 Mar 2018 18:35:48 -0500 David Wright wrote: > On Tue 20 Mar 2018 at 18:41:55 (-0400), Dan Norton wrote: > > On Tue, 20 Mar 2018 13:42:24 -0500 > > David Wright wrote: > > > > > On Tue 20 Mar 2018 at 13:47:42 (-0400), Dan Norton wrote: > > > > On Tue, 20 Mar 2018 12:59:21 -0400 > > > > Greg Wooledge 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 ffmpegDepends 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. > > > > The broken system was installed in December 2017. Looking at all the > > logs in /var/log/apt/history* (extracting the ones that were > > archived) and running: > > dan@deb9:~/apt.logs$ grep -rnw '.' -e 'libopenal1' | less > > ...there is one hit, other than today's --reinstall and that is an > > install: > > > > Start-Date: 2017-12-17 21:29:03 > > Commandline: /usr/sbin/synaptic > > Requested-By: dan (1200) > > Install: [...] > > libopenal1:amd64 (1:1.17.2-4+b2, automatic), # e pluribus unum > > [...] > > > > > 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. > > > > > > > Apparently nothing during these attempts involved libopenal1, > > according to the logs in /var/log/apt/ - is there anywhere else > > that could shed light on this? > > Is it still marked as Automatic? Particularly if you try to install > it, it will lose that flag (all this is IIRC). Further use of that > command sequence would have no effect in that case. > root@deb9:~# apt search libopenal1 Sorting... Done Full Text Search... Done libopenal1/stable,now 1:1.17.2-4+b2 amd64 [installed,automatic] [...] > The dependency is via another package. I've found that removing a > package doesn't always reach down to all the Automatic packages > beneath it. This is easily demonstrated by installing a package > with multiple dependencies (in depth) and then immediately purging > it. > > But none of this gets down to the root of the problem (why the > installed package didn't provide the library). Perhaps it might > be worth occasionally running > # debsums -l > # debsums -ca > to check things over. There's also dpkg -V. > root@deb9:~# debsums -l root@deb9:~# root@deb9:~# debsums -ca 2>/home/dan/debsums.out /etc/lvm/lvm.conf ...producing 958.9 kB of missing file messages in debsums.out, none mention libopenal1. root@deb9:~# dpkg -V >/home/dan/dpkg.out ...producing 590.2 kB of text lines, none mention libopenal1. Now that libopenal1 has been reinstalled and ffmpeg runs this is probably to be expected, right? It would have been more interesting if done when deb9 was broken WRT ffmpeg. - Dan
Re: Missing Shared Object File for ffmpeg
On Tue 20 Mar 2018 at 18:41:55 (-0400), Dan Norton wrote: > On Tue, 20 Mar 2018 13:42:24 -0500 > David Wright wrote: > > > On Tue 20 Mar 2018 at 13:47:42 (-0400), Dan Norton wrote: > > > On Tue, 20 Mar 2018 12:59:21 -0400 > > > Greg Wooledge 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 ffmpegDepends 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. > > > > The broken system was installed in December 2017. Looking at all the > logs in /var/log/apt/history* (extracting the ones that were > archived) and running: > dan@deb9:~/apt.logs$ grep -rnw '.' -e 'libopenal1' | less > ...there is one hit, other than today's --reinstall and that is an > install: > > Start-Date: 2017-12-17 21:29:03 > Commandline: /usr/sbin/synaptic > Requested-By: dan (1200) > Install: [...] > libopenal1:amd64 (1:1.17.2-4+b2, automatic), # e pluribus unum > [...] > > > 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. > > > > Apparently nothing during these attempts involved libopenal1, according > to the logs in /var/log/apt/ - is there anywhere else that could shed > light on this? Is it still marked as Automatic? Particularly if you try to install it, it will lose that flag (all this is IIRC). Further use of that command sequence would have no effect in that case. The dependency is via another package. I've found that removing a package doesn't always reach down to all the Automatic packages beneath it. This is easily demonstrated by installing a package with multiple dependencies (in depth) and then immediately purging it. But none of this gets down to the root of the problem (why the installed package didn't provide the library). Perhaps it might be worth occasionally running # debsums -l # debsums -ca to check things over. There's also dpkg -V. Cheers, David.
Re: Missing Shared Object File for ffmpeg
On Tue, 20 Mar 2018 13:42:24 -0500 David Wright wrote: > On Tue 20 Mar 2018 at 13:47:42 (-0400), Dan Norton wrote: > > On Tue, 20 Mar 2018 12:59:21 -0400 > > Greg Wooledge 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 ffmpegDepends 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. > The broken system was installed in December 2017. Looking at all the logs in /var/log/apt/history* (extracting the ones that were archived) and running: dan@deb9:~/apt.logs$ grep -rnw '.' -e 'libopenal1' | less ...there is one hit, other than today's --reinstall and that is an install: Start-Date: 2017-12-17 21:29:03 Commandline: /usr/sbin/synaptic Requested-By: dan (1200) Install: [...] libopenal1:amd64 (1:1.17.2-4+b2, automatic), # e pluribus unum [...] > 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. > Apparently nothing during these attempts involved libopenal1, according to the logs in /var/log/apt/ - is there anywhere else that could shed light on this? - Dan
Re: Missing Shared Object File for ffmpeg
On Tue, 20 Mar 2018 19:02:23 +0100 wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Tue, Mar 20, 2018 at 01:47:42PM -0400, Dan Norton wrote: > > [...] > > > > apt-get --reinstall install libopenal1 > > > > > > > That did it - thanks, Greg! > > My guess would be that libopenal1 (the package) was installed, > but the library (the file) has been somehow deleted. > > The --reinstall forces apt to install the package even if it > thinks it's already there (quite useful in such a case :) > "--reinstall install" - that's strange and unusual :) but I'm glad it worked. - Dan > Cheers > - -- t > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.12 (GNU/Linux) > > iEYEARECAAYFAlqxTK8ACgkQBcgs9XrR2kbmSgCffJO16KsjvSFiI144dqzK0+Ip > vEgAn124eKQhe4hESe71CJ0avU+jOh+P > =GtAc > -END PGP SIGNATURE- >
Re: Missing Shared Object File for ffmpeg
On Tue 20 Mar 2018 at 13:47:42 (-0400), Dan Norton wrote: > On Tue, 20 Mar 2018 12:59:21 -0400 > Greg Wooledge 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 ffmpegDepends 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.
Re: Missing Shared Object File for ffmpeg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Mar 20, 2018 at 01:47:42PM -0400, Dan Norton wrote: [...] > > apt-get --reinstall install libopenal1 > > > > That did it - thanks, Greg! My guess would be that libopenal1 (the package) was installed, but the library (the file) has been somehow deleted. The --reinstall forces apt to install the package even if it thinks it's already there (quite useful in such a case :) Cheers - -- t -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlqxTK8ACgkQBcgs9XrR2kbmSgCffJO16KsjvSFiI144dqzK0+Ip vEgAn124eKQhe4hESe71CJ0avU+jOh+P =GtAc -END PGP SIGNATURE-
Re: Missing Shared Object File for ffmpeg
On Tue, 20 Mar 2018 12:59:21 -0400 Greg Wooledge 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 ffmpegDepends 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?
Re: Missing Shared Object File for ffmpeg
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 ffmpegDepends 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
Re: Missing Shared Object File for ffmpeg
On Tue 20 Mar 2018 at 15:57:03 (+), Curt wrote: > On 2018-03-20, David Wright wrote: > >> > >> Yes the package is libopenal1. I don't have the package in Stretch, > >> though ffmpeg is installed. > > > > In my ftp.us.debian.org_debian_dists_stretch_main_binary-amd64_Packages > > (39116092 Mar 10 03:33) ffmpeg says: > > > > Package: ffmpeg > > > > > and libavdevice57 says: > > > > > so how do you get around not installing libopenal1? > > **Important informational note: I am not the OP, posed no > question in this thread, nor asked for any help (although I might need > some). I'm only a lowly participant.** > > I'm sorry; I've sent you on a chase in which the goose is unfortunately > wild. > > I do have libopenal1, in fact; I misread the output of "apt show libopenal1" > earlier. > > Once again, apologies. That's OK. In the absence of anything from the OP, I thought that you might have downloaded something from backports or that multimedia archive which can get you into a mess. (In which case, you might have acted as a proxy for the OP.) Cheers, David.
Re: Missing Shared Object File for ffmpeg
On Tue, 20 Mar 2018 08:41:40 -0400 Greg Wooledge wrote: > On Tue, Mar 20, 2018 at 10:12:41AM +, Curt wrote: > > On 2018-03-20, wrote: > > > Now the interesting question would be: in *both* your stretches? > > > > It is interesting maybe. I don't understand it, though. > > Basically, you're not supplying enough information to diagnose the > problem. We would need some or all of: > (from the non-working system) > * Your /etc/apt/sources.list file. deb http://debian.gtisc.gatech.edu/debian/ stretch main contrib non-free deb-src http://debian.gtisc.gatech.edu/debian/ stretch main contrib non-free deb http://security.debian.org/debian-security stretch/updates main contrib non-free deb-src http://security.debian.org/debian-security stretch/updates main contrib non-free deb http://debian.gtisc.gatech.edu/debian/ stretch-updates main contrib non-free deb-src http://debian.gtisc.gatech.edu/debian/ stretch-updates main contrib non-free deb http://debian.gtisc.gatech.edu/debian/ stretch-backports main contrib non-free > * The exact version of the ffmpeg package (dpkg -l ffmpeg | cat). ii ffmpeg 7:3.2.10-1~deb9u1 amd64 > * 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 ffmpegDepends libavdevice57 (>= 7:3.2.10) i A libavdevice57 Depends libopenal1 (>= 1.14) > * Any interesting files in /etc/apt/apt.conf.d/ which may affect >package selection (especially the treament of Suggests and > Recommends). root@deb9:~# egrep -wr 'Suggests|Recommends' /etc/apt/apt.conf.d/ /etc/apt/apt.conf.d/99synaptic:APT::Install-Recommends "true"; > > >From the non-working system, of course. Though you may find the > output of "aptitude why libopenal1" to be informative on the working > system. > i ffmpegDepends libavdevice57 (>= 7:3.2.10) i A libavdevice57 Depends libopenal1 (>= 1.14) A thought: The working system is little changed from the installed state, so it has mozilla. However, on the non-working system, mozilla is purged and palemoon installed. The name "ffmpeg"... ^^ ...any relation to firefox?
Re: Missing Shared Object File for ffmpeg
On 2018-03-20, David Wright wrote: >> >> Yes the package is libopenal1. I don't have the package in Stretch, >> though ffmpeg is installed. > > In my ftp.us.debian.org_debian_dists_stretch_main_binary-amd64_Packages > (39116092 Mar 10 03:33) ffmpeg says: > > Package: ffmpeg > and libavdevice57 says: > so how do you get around not installing libopenal1? **Important informational note: I am not the OP, posed no question in this thread, nor asked for any help (although I might need some). I'm only a lowly participant.** I'm sorry; I've sent you on a chase in which the goose is unfortunately wild. I do have libopenal1, in fact; I misread the output of "apt show libopenal1" earlier. Once again, apologies. -- Bah, the latest news, the latest news is not the last. Samuel Beckett
Re: Missing Shared Object File for ffmpeg
On Tue, Mar 20, 2018 at 09:50:53AM -0500, David Wright wrote: > In my ftp.us.debian.org_debian_dists_stretch_main_binary-amd64_Packages > (39116092 Mar 10 03:33) ffmpeg says: > > Package: ffmpeg > Version: 7:3.2.10-1~deb9u1 > Installed-Size: 2137 > Maintainer: Debian Multimedia Maintainers > > Architecture: amd64 > Replaces: libav-tools (<< 6:12~~), qt-faststart (<< 7:2.7.1-3~) > Depends: libavcodec57 (>= 7:3.2.10) | libavcodec-extra57 (>= 7:3.2.10), > libavdevice57 (>= 7:3.2.10), … > so how do you get around not installing libopenal1? Either by having ffmpeg from a non-stretch source (e.g. one of the "multimedia" repositories), or by having libavcodec-extra57 instead of libavcodec57. Note the " | " in that Depends line. > BTW Greg, aptitude why libopenal1 might not help because it only > displays the “most installed, strongest, tightest, shortest” > dependency chain, which here is: > > i mplayer-gui Depends libopenal1 (>= 1.14) Even if the chance of it helping from the broken system is tiny, we still face the fundamental problem that the OP is not providing ANY information at all, so ANYTHING we can get would be an improvement. Seeing "aptitude why libopenal1" from the working system may clue the OP in with "Oh yeah, I did *that*, I forgot!" or whatever. This may all help someone who's having a similar problem a year from now and is reading this thread in the archives.
Re: Missing Shared Object File for ffmpeg
On Tue 20 Mar 2018 at 08:41:05 (+), Curt wrote: > On 2018-03-20, wrote: > > > > Try "apt-file search" (in package apt-file): > > > > tomas@trotzki:~$ apt-file search libopenal.so.1 > > libopenal1: /usr/lib/x86_64-linux-gnu/libopenal.so.1 > > libopenal1: /usr/lib/x86_64-linux-gnu/libopenal.so.1.17.2 > > > > I guess libopenal gets loaded on-demand as a plugin. Are you > > sure you are trying the same video on both systems? Otherwise, > > I don't have an idea on what could cause this difference. > > > > Yes the package is libopenal1. I don't have the package in Stretch, > though ffmpeg is installed. In my ftp.us.debian.org_debian_dists_stretch_main_binary-amd64_Packages (39116092 Mar 10 03:33) ffmpeg says: Package: ffmpeg Version: 7:3.2.10-1~deb9u1 Installed-Size: 2137 Maintainer: Debian Multimedia Maintainers Architecture: amd64 Replaces: libav-tools (<< 6:12~~), qt-faststart (<< 7:2.7.1-3~) Depends: libavcodec57 (>= 7:3.2.10) | libavcodec-extra57 (>= 7:3.2.10), libavdevice57 (>= 7:3.2.10), … and libavdevice57 says: Package: libavdevice57 Source: ffmpeg Version: 7:3.2.10-1~deb9u1 Installed-Size: 278 Maintainer: Debian Multimedia Maintainers Architecture: amd64 Depends: libasound2 (>= 1.0.16), libavc1394-0 (>= 0.5.3), libavcodec57 (>= 7:3.2.10) | libavcodec-extra57 (>= 7:3.2.10), libavfilter6 (>= 7:3.2.10) | libavfilter-extra6 (>= 7:3.2.10), libavformat57 (>= 7:3.2.10), libavutil55 (>= 7:3.2.10), libc6 (>= 2.14), libcaca0 (>= 0.99.beta17-1), libcdio-cdda1 (>= 0.83), libcdio-paranoia1 (>= 0.83), libdc1394-22, libgl1-mesa-glx | libgl1, libiec61883-0 (>= 1.2.0), libjack-jackd2-0 (>= 1.9.10+20150825) | libjack-0.125, libopenal1 (>= 1.14), … so how do you get around not installing libopenal1? BTW Greg, aptitude why libopenal1 might not help because it only displays the “most installed, strongest, tightest, shortest” dependency chain, which here is: i mplayer-gui Depends libopenal1 (>= 1.14) > ffmpeg -formats > > informs me that my ffmpeg was configured with "--enable-openal" and > includes the "D openal OpenAL audio capture device". > > This post is probably what they call "superfétatoire" in French. Cheers, David.
Re: Missing Shared Object File for ffmpeg
On 2018-03-20, Greg Wooledge wrote: > On Tue, Mar 20, 2018 at 10:12:41AM +, Curt wrote: >> On 2018-03-20, wrote: >> > Now the interesting question would be: in *both* your stretches? >> >> It is interesting maybe. I don't understand it, though. > > Basically, you're not supplying enough information to diagnose the > problem. We would need some or all of: I'm not the OP and don't have a problem. > * Your /etc/apt/sources.list file. > * The exact version of the ffmpeg package (dpkg -l ffmpeg | cat). > * The output of "apt policy ffmpeg". > * The output of "aptitude why libopenal1". > * Any interesting files in /etc/apt/apt.conf.d/ which may affect >package selection (especially the treament of Suggests and Recommends). > >>From the non-working system, of course. Though you may find the > output of "aptitude why libopenal1" to be informative on the working > system. > > -- Bah, the latest news, the latest news is not the last. Samuel Beckett
Re: Missing Shared Object File for ffmpeg
On Tue, Mar 20, 2018 at 10:12:41AM +, Curt wrote: > On 2018-03-20, wrote: > > Now the interesting question would be: in *both* your stretches? > > It is interesting maybe. I don't understand it, though. Basically, you're not supplying enough information to diagnose the problem. We would need some or all of: * Your /etc/apt/sources.list file. * The exact version of the ffmpeg package (dpkg -l ffmpeg | cat). * The output of "apt policy ffmpeg". * The output of "aptitude why libopenal1". * Any interesting files in /etc/apt/apt.conf.d/ which may affect package selection (especially the treament of Suggests and Recommends). >From the non-working system, of course. Though you may find the output of "aptitude why libopenal1" to be informative on the working system.
Re: Missing Shared Object File for ffmpeg
On 2018-03-20, wrote: > >> Yes the package is libopenal1. I don't have the package in Stretch, >> though ffmpeg is installed. > > I take "you don't have the package in Stretch" to mean "in your box > it isn't installed", because the package does exist in Stretch (at > least in my little corner of the universe). Yes, sorry for the equivocal formulation. The libopenal1 package is indeed in the Debian repositories but isn't installed on my machine. > Now the interesting question would be: in *both* your stretches? It is interesting maybe. I don't understand it, though. >> ffmpeg -formats >> >> informs me that my ffmpeg was configured with "--enable-openal" and >> includes the "D openal OpenAL audio capture device". >> >> This post is probably what they call "superfétatoire" in French. > > Heh. Had to look that up, thanks for a new word: perhaps I can build > that in and impress my teacher ;-D > > Cheers > - -- tomás > > -- Bah, the latest news, the latest news is not the last. Samuel Beckett
Re: Missing Shared Object File for ffmpeg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Mar 20, 2018 at 08:41:05AM +, Curt wrote: > On 2018-03-20, wrote: > > > > Try "apt-file search" (in package apt-file): > > > > tomas@trotzki:~$ apt-file search libopenal.so.1 > > libopenal1: /usr/lib/x86_64-linux-gnu/libopenal.so.1 > > libopenal1: /usr/lib/x86_64-linux-gnu/libopenal.so.1.17.2 > > > > I guess libopenal gets loaded on-demand as a plugin. Are you > > sure you are trying the same video on both systems? Otherwise, > > I don't have an idea on what could cause this difference. > > > > Yes the package is libopenal1. I don't have the package in Stretch, > though ffmpeg is installed. I take "you don't have the package in Stretch" to mean "in your box it isn't installed", because the package does exist in Stretch (at least in my little corner of the universe). Now the interesting question would be: in *both* your stretches? > ffmpeg -formats > > informs me that my ffmpeg was configured with "--enable-openal" and > includes the "D openal OpenAL audio capture device". > > This post is probably what they call "superfétatoire" in French. Heh. Had to look that up, thanks for a new word: perhaps I can build that in and impress my teacher ;-D Cheers - -- tomás -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlqwzh4ACgkQBcgs9XrR2kZ3jgCeJ6UEvl2kF+XqN7nhTC37XH51 dfMAniKLhq48tJKrE731n7qulfgyhGxx =k9iu -END PGP SIGNATURE-
Re: Missing Shared Object File for ffmpeg
On 2018-03-20, wrote: > > Try "apt-file search" (in package apt-file): > > tomas@trotzki:~$ apt-file search libopenal.so.1 > libopenal1: /usr/lib/x86_64-linux-gnu/libopenal.so.1 > libopenal1: /usr/lib/x86_64-linux-gnu/libopenal.so.1.17.2 > > I guess libopenal gets loaded on-demand as a plugin. Are you > sure you are trying the same video on both systems? Otherwise, > I don't have an idea on what could cause this difference. > Yes the package is libopenal1. I don't have the package in Stretch, though ffmpeg is installed. ffmpeg -formats informs me that my ffmpeg was configured with "--enable-openal" and includes the "D openal OpenAL audio capture device". This post is probably what they call "superfétatoire" in French. -- Bah, the latest news, the latest news is not the last. Samuel Beckett
Re: Missing Shared Object File for ffmpeg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Mar 19, 2018 at 09:38:57PM -0400, Dan Norton wrote: > I have two stretch systems, named deb4 and deb9. Both were installed > via netinst, have the latest apt update; apt upgrade, and report: > > $ uname -v > #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) > > Several attempts to install ffmpeg on deb9 have appeared to succeed, > but ffmpeg with various options consistently reports: > > ffmpeg: error while loading shared libraries: libopenal.so.1: cannot > open shared object file: No such file or directory [...] > # apt search openal > ...and saw that it contains libopenal.so.1 but: > # apt install openal > E: Unable to locate package openal > > What do I need to do to figure out what's wrong with deb9? Try "apt-file search" (in package apt-file): tomas@trotzki:~$ apt-file search libopenal.so.1 libopenal1: /usr/lib/x86_64-linux-gnu/libopenal.so.1 libopenal1: /usr/lib/x86_64-linux-gnu/libopenal.so.1.17.2 I guess libopenal gets loaded on-demand as a plugin. Are you sure you are trying the same video on both systems? Otherwise, I don't have an idea on what could cause this difference. Cheers - -- tomás -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEUEARECAAYFAlqwv2sACgkQBcgs9XrR2ka2RQCeKHXeOiA6bHvSgZk93n61eT63 tYAAmIA+rqqtp+SQq9FhdztKiFLZhdg= =+2nB -END PGP SIGNATURE-
Missing Shared Object File for ffmpeg
I have two stretch systems, named deb4 and deb9. Both were installed via netinst, have the latest apt update; apt upgrade, and report: $ uname -v #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) Several attempts to install ffmpeg on deb9 have appeared to succeed, but ffmpeg with various options consistently reports: ffmpeg: error while loading shared libraries: libopenal.so.1: cannot open shared object file: No such file or directory On the other system, deb4, ffmpeg installed and ran immediately and was successfully used to split a .mov file into two parts. /etc/apt/sources.list is the same on deb4 and deb9. I have compared the package versions on deb9 with those on deb4 and they are the same. Before reinstalling ffmpeg on deb9 I ran: # apt purge ffmpeg # apt autoremove # apt install ffmpeg I've run ldconfig and repeated the above. STW, I've set LD_LIBRARY_PATH=/usr/local/lib and repeated. Also tried: # apt search openal ...and saw that it contains libopenal.so.1 but: # apt install openal E: Unable to locate package openal What do I need to do to figure out what's wrong with deb9? - Dan
