SOLVED: Checked movies still in list with weird playback amount - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Support (https://forum.jellyfin.org/f-support) +--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting) +--- Thread: SOLVED: Checked movies still in list with weird playback amount (/t-solved-checked-movies-still-in-list-with-weird-playback-amount)

Checked movies still in list with weird playback amount - Geekphreek - 2024-11-01 I think I need to raise this as a bug, but I want to know if others are having the same issue. I'm running the latest versions of Jellyfin. My primary watching is via a Firestick with Jellyfin for FireTV client. I'm seeing a LOT of my watched media reappearing in Continue Watching, with random amounts of play on them. Is this affecting anyone else? My search didn't yield any real returns for this issue. To clear them, I have to mark as Unplayed and then go back and mark as Played again. However, they may show back up in Continue Watching. RE: Chcked movies still in list with weird playback amount - theguymadmax - 2024-11-01 Sounds like this bug. RE: Chcked movies still in list with weird playback amount - TheDreadPirate - 2024-11-01 Are you using NFOs to save watched status? RE: Checked movies still in list with weird playback amount - Geekphreek - 2024-11-01 I am using the NFO watch status for my user, yes. I'll disable and see if the bug buggers off. It does look like bug https://github.com/jellyfin/jellyfin/issues/12054 Thank you! RE: Checked movies still in list with weird playback amount - TheDreadPirate - 2024-11-01 I remember another user had a similar issue. Something changed with their file permissions for the NFOs and Jellyfin could no longer write to them to update the watch status or watch progress. RE: Checked movies still in list with weird playback amount - Geekphreek - 2024-11-01 Jellyfin has full access to the storage and can write them fine. It's what creates them in the first instance for all of my media. Disabling the NFO writing for a specific user seems to solve it.