Conversation

Notices

1. Embed this notice
   HistoPol (#HP) 🏴 🇺🇸 🏴 (histopol@mastodon.social)'s status on Tuesday, 27-May-2025 18:07:23 JST HistoPol (#HP) 🏴 🇺🇸 🏴

   in reply to

   • Mina

   @mina

   Sounds really awful.
   I feel ya, Mina.

   • Embed this notice
     Mina (mina@berlin.social)'s status on Tuesday, 27-May-2025 18:07:25 JST Mina

     in reply to

     The snap worked, but only so so:

     Now ffmpeg didn't find its component ffprobe, despite it being part of the snap.

     God, I hated Linux in that moment!

     So, away with the snap.

     Read the ffmpeg documentation, found the list of its libraries, reinstalled them all and then, finally, everything worked.

     But: Am I right or not?

     This is not something a normal person would consider a viable solution.

     3/3

   • Embed this notice
     Mina (mina@berlin.social)'s status on Tuesday, 27-May-2025 18:07:26 JST Mina

     in reply to

     $ sudo apt reinstall ffmpeg

     Alas, to no avail! No improvement.

     So underlying libraries are probably the problem.

     If only apt reinstall had a flag "--all-dependencies"!

     But no. I found a script (on Reddit again) that would do it, but didn't felt like running a script by some random dude, so let's do the "modern" thing and use a snap.

     2/3

   • Embed this notice
     Mina (mina@berlin.social)'s status on Tuesday, 27-May-2025 18:07:27 JST Mina

     Usually, I'm quite happy with #Linux:

     It just works, and I don't have to think about it at all.

     But sometimes, I reckon: If it sucks, it sucks badly.

     I use the command line video editor #ffmpeg quite a lot, but yesterday, it just stopped working, first producing wrong results and then weird error messages.

     Internet search for the error messages gave lots of results from the 2010s and Reddit threads where the issue remained unresolved.

     "OK", I thought, "Let's do what everyone does":

     1/3