Jellyfin Media Player 1.12.0 — the first minute without a single click
How we tested: a clean Debian 13 in a disposable container; source — official file https://github.com/jellyfin/jellyfin-desktop/releases/download/v1.12.0/jellyfin-media-player_1.12.0-trixie.deb (jellyfin-media-player 1.12.0+deb). Run as a regular user on a virtual screen, 60 seconds, nothing clicked. 18.10.2026. Every network request and every file written was recorded; the code was not decompiled. The container was deleted afterwards.
Program website: https://jellyfin.org/
Package SHA-256: fa6d3697fd7ec61392826e47c7e6bb79cab005e48fba568dfabda7ae937a1e25
Summary
| What we checked | Result |
|---|---|
| Built-in telemetry, crash reporting, analytics, ad SDKs | none |
| Network requests in the first minute | not a single network request |
| Known trackers among the servers | none |
| Files written in the first minute | 135 |
| The program ran the whole time | yes — process alive at the end |
What is built in
16 files (1 MB) were checked.
No code of known telemetry, crash reporting, analytics or ad SDKs was found.
Where it connected
Not a single request: no DNS lookup, no connection.
What it wrote to disk
Folders the program wrote files to during the minute:
| Folder | Files |
|---|---|
~/.cache/mesa_shader_cache_db | 102 |
~/.local/share | 30 |
~/.cache/Jellyfin Media Player | 1 |
~/.cache/qtshadercache-x86_64-little_endian-lp64 | 1 |
~/.config/jellyfin.org | 1 |
How to read this card
- This is the first minute after launch with no action at all: what the program does on its own. Normal use may involve more requests.
- A “built-in SDK” means the library’s code was found. It does not prove data transfer, and an address in the code is not a request.
- The review was made automatically using a single method. You can check any program yourself here.