mpv-player / mpv-player/mpv

Watch history file stored in current directory when running with `--no-config`

Open
#16,358 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

core
Dominant language
C
Stars
37k
Forks
3.5k
Avg merge
1d 10h
Merged PRs (30d)
22

Description

mpv Information
mpv v0.40.0 Copyright © 2000-2025 mpv/MPlayer/mplayer2 projects
libplacebo version: v7.349.0
FFmpeg version: 7.1.1-1+b1
FFmpeg library versions:
   libavcodec      61.19.101
   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: Debian GNU/Linux unstable (sid)
- Kernel Version: Linux host 6.12.27-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.27-1 (2025-05-06) x86_64 GNU/Linux
- GPU Model:
- Mesa/GPU Driver Version:
- Window Manager and Version:
- Source of mpv: Debian package
- Latest known working version:
- Issue started after the following happened:
Reproduction Steps

Run

mpv --no-config --save-watch-history 'https://www.youtube.com/watch?v=dQw4w9WgXcQ'
Expected Behavior

Watch history file should be stored in ~~state/watch_history.jsonl as documented in the man page.

Actual Behavior

Watch history file is stored the current directory.

Log File

output.txt

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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the command with mpv --no-config --save-watch-history and compare the actual file location with the man page's ~~state/watch_history.jsonl expectation. Then trace the --no-config and --save-watch-history entry points using the attached output.txt; done means the history file is stored in the documented state path rather than the current directory.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.