mpv Information

mpv v0.40.0-dirty Copyright © 2000-2025 mpv/MPlayer/mplayer2 projects
 built on Apr  4 2025 07:28:54
libplacebo version: v7.349.0
FFmpeg version: n7.1
FFmpeg library versions:
   libavcodec      61.19.100
   libavdevice     61.3.100
   libavfilter     10.4.100
   libavformat     61.7.100
   libavutil       59.39.100
   libswresample   5.3.100
   libswscale      8.3.100

Other Information

- Linux version:NAME="EndeavourOS" / archlinux
- Kernel Version:
- GPU Model:
- Mesa/GPU Driver Version:
- Window Manager and Version:
- Source of mpv:
- Latest known working version:
- Issue started after the following happened:

Reproduction Steps

1. Givien that https://aa.com/ is protected by a self-signed CA and TLS client authentication
2. mpv https://aa.com/bbb.mp4 --tls-cert-file=~/.ssl/pubkey.pem --tls-key-file=~/.ssl/privkey.pem --tls-ca-file=~/.ssl/ca.pem

Expected Behavior

mpv expands ~/.ssl/pubkey.pem to /home/user/.ssl/pubkey.pem and reads it

I add char *mp_get_user_path(void *talloc_ctx, struct mpv_global *global, const char *path); calls at these lines, and it works.

However, I don't know talloc and mpv well and don't know:

1. what to fill the 1st arg (talloc_ctx)
2. whether free the return value of mp_get_user_path or not after av_dict_set calls

Actual Behavior

mpv does not expand the user path and tries to load '~/.ssl/pubkey.pem', which does not exist.

Log File

[ffmpeg] tls: Unable to set cert/key files ~/.ssl/pubkey.pem and ~/.ssl/privkey.pem: Error while reading file.
Failed to open https://aa.com/bbb.mp4.

Sample Files

No response

I carefully read all instruction and confirm that I did the following:

• I tested with the latest mpv version to validate that the issue is not already fixed.
• I provided all required information including system and mpv version.
• I produced the log file with the exact same set of files, parameters, and conditions used in "Reproduction Steps", with the addition of --log-file=output.txt.
• I produced the log file while the behaviors described in "Actual Behavior" were actively observed.
• I attached the full, untruncated log file.
• I attached the backtrace in the case of a crash.