mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-01-23 23:20:51 +01:00
When Playback -> Resume -> Maximum resume percentage is set to 100% video is not set as watched correctly #6613
Labels
No labels
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
EFjellyfin.db
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: starred/jellyfin#6613
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Dyr-Fenrir on GitHub (Dec 27, 2024).
This issue respects the following points:
Description of the bug
When the following option: "Administration" -> "Dashboard" -> "Server" -> "Playback" -> "Resume" -> "Maximum resume percentage" is set to 100%, when a video is watched and reaches the end and stops playing automatically, it will still appear in the "Continue Watching" list.
When clicked on from the "Continue Watching", the video will appear blank with a total time of "0:00", I then need to press "Back" and click on the video again from "Continue Watching", repeating this process will eventually make it disappear from the "Continue Watching" list and it will then be able to replay correctly from the beginning next time from it's original location in the library.
Reproduction steps
What is the current bug behavior?
The video still appears in the "Continue Watching" list and will be resumed in an inconsistent state (blank screen with total at 0:00) when being clicked on a few times (need to use the back button to go back to the dashboard) until it will eventually disappear correctly form the "Continue Watching" and can be replayed normally. Sometimes, it will also go back to the dashboard, the progress bar will appear to be at 0 and clicking on the video again will remove it from the "Continue Watching".
What is the expected correct behavior?
The video should disappear from the "Continue Watching" list and can be replayed normally from the start after.
Jellyfin Server version
10.10.0+
Specify commit id
No response
Specify unstable release number
No response
Specify version number
No response
Specify the build version
10.10.3
Environment
Jellyfin logs
FFmpeg logs
Client / Browser logs
No response
Relevant screenshots or videos
No response
Additional information
No response
@jellyfin-bot commented on GitHub (Apr 27, 2025):
This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.
If you have any questions you can use one of several ways to contact us.
@Dyr-Fenrir commented on GitHub (May 1, 2025):
Greetings,
I am still experiencing this issue in version 10.10.7.
I do not have new logs to provide, but I noticed another behavior linked to this issue, whenever I finish watching a video, after the behavior described above, said video is also not flagged as "mark played" and appears in the new content section of the homepage.
Furthermore, if a video was completely watched previously and then watched again (or "mark played" manually), the "mark played" is also "removed" and the video, then, also appears in the "recently added in movies" section.
@jellyfin-bot commented on GitHub (Aug 31, 2025):
This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.
If you have any questions you can use one of several ways to contact us.
@Dyr-Fenrir commented on GitHub (Sep 10, 2025):
Greetings,
There was no version updates as far as I am aware, although one is currently in RC, I did try again with version 10.10.7 and I still have the same issue, as soon as the release is available, I will make sure to try it and give an update.
Note: This post is mainly to prevent the issue to be closed due to being stale.