Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#46464 - [ffmpeg2.8] adds /usr/lib to path before any file starting with letter after f

Attached to Project: Arch Linux
Opened by James Duley (parched) - Monday, 28 September 2015, 18:41 GMT
Last edited by Maxime Gauduin (Alucryd) - Friday, 25 May 2018, 19:39 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Maxime Gauduin (Alucryd)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


Due to this commit
any file in /etc/ starting with a letter after 'f' can't override the default loader path /usr/lib.

I suggest if ffmpeg-compat is trying to hack like this then it should rename to ZZ-ffmpeg-compat.conf
so it doesn't conflict with other potential users of

This task depends upon

Closed by  Maxime Gauduin (Alucryd)
Friday, 25 May 2018, 19:39 GMT
Reason for closing:  Won't fix
Additional comments about closing:  ffmpeg2.8 is gone
Comment by Maxime Gauduin (Alucryd) - Friday, 23 October 2015, 09:44 GMT
Why not name your hack AA-foo.conf?
Comment by James Duley (parched) - Friday, 23 October 2015, 20:00 GMT
I have done something similar and it works fine, but to avoid future confusion I think this should be changed.
What I have isn't a hack, paths are supposed to be searched before the default library path.
ffmpeg-compat is breaking this convention with its hack.
Comment by James Duley (parched) - Friday, 23 October 2015, 20:08 GMT
Maybe we should have a convention like udev and start all .conf files with a number
and then have something like 50-default.conf contain /usr/lib so a package can go before or after
Comment by Maxime Gauduin (Alucryd) - Wednesday, 28 October 2015, 10:29 GMT
I don't mind calling it 99-ffmpeg-compat.conf to follow the usual conf conventions rather than ZZ-ffmpeg-compat.conf.
Comment by James Duley (parched) - Wednesday, 18 November 2015, 20:15 GMT
Yes that's a good idea, although 51-ffmpeg-compat.conf would probably better, then <50 is before standard paths and >50 is after standard paths.
Ultimately it would be best to have 50-default.conf with the standard paths provided by filesystem then ffmpeg-compat wouldn't need them.
Comment by Kevin Mihelich (kmihelich) - Tuesday, 24 May 2016, 19:22 GMT
This issue is also present the in ffmpeg2.8.
Comment by Eli Schwartz (eschwartz) - Tuesday, 15 August 2017, 16:20 GMT
  • Field changed: Attached to Project (Community Packages → Arch Linux)
  • Field changed: Summary ([ffmpeg-compat] adds /usr/lib to path before any file starting with letter after f → [ffmpeg2.8] adds /usr/lib to path before any file starting with letter after f)
ffpeg-compat no longer exists, but ffmpeg2.8 is still an issue. Any plans to fix this?