You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a bug, not a question or a configuration issue; Please visit our forum or chat rooms first to troubleshoot with volunteers, before creating a report. The links can be found here.
This issue is not already reported on GitHub(I've searched it).
I'm using an up to date version of Jellyfin Server stable, unstable or master; We generally do not support previous older versions. If possible, please update to the latest version before opening an issue.
Nov 11 21:52:58 media jellyfin[48061]: [21:52:58] [INF] Playback stopped reported by app Android TV 0.17.9 playing Die Bounty. Stopped at 3135133 ms
Nov 11 21:52:58 media jellyfin[48061]: [21:52:58] [INF] Playback stop tracker found, processing stop : aab8879beaf04362dcfa80c42b877d3b7c1cb49a-dd99268c2eef4d659207c675967d3f05-e9db1d38d619637817dfcb7bd>
Nov 11 21:52:58 media jellyfin[48061]: [21:52:58] [INF] PlaybackTracker : Adding Stop Event : 11/11/2024 21:52:58
Nov 11 21:52:58 media jellyfin[48061]: [21:52:58] [INF] Playback stop but TrackedPlaybackInfo not found! not storing activity in DB
Nov 11 21:52:58 media jellyfin[48061]: [21:52:58] [INF] Started user data sync
Nov 11 21:52:58 media jellyfin[48061]: [21:52:58] [ERR] An error has occurred in UserUpdateTimerCallback
Nov 11 21:52:58 media jellyfin[48061]: System.InvalidCastException: Unable to cast object of type'System.Guid' to type'System.String'.
Nov 11 21:52:58 media jellyfin[48061]: at lambda_method1263(Closure, Object, Object)
Nov 11 21:52:58 media jellyfin[48061]: at LiteDB.BsonMapper.DeserializeObject(EntityMapper entity, Object obj, BsonDocument value)
Nov 11 21:52:58 media jellyfin[48061]: at LiteDB.BsonMapper.Deserialize(Type type, BsonValue value)
Nov 11 21:52:58 media jellyfin[48061]: at LiteDB.LiteQueryable`1.<ToEnumerable>b__27_2(BsonDocument x)Nov 11 21:52:58 media jellyfin[48061]: at System.Linq.Enumerable.SelectEnumerableIterator`2.ToList()Nov 11 21:52:58 media jellyfin[48061]: at Jellyfin.Plugin.KodiSyncQueue.Data.DbRepo.SetUserInfoSync(List`1 dtos, List`1 itemRefs, String userId)Nov 11 21:52:58 media jellyfin[48061]: at Jellyfin.Plugin.KodiSyncQueue.EntryPoints.UserSyncNotification.SaveUserChanges(List`1 dtos, List`1 itemRefs, String userName, String userId)Nov 11 21:52:58 media jellyfin[48061]: at Jellyfin.Plugin.KodiSyncQueue.EntryPoints.UserSyncNotification.SendNotifications(IEnumerable`1 changes, List`1 itemRefs, CancellationToken cancellationToken)Nov 11 21:52:58 media jellyfin[48061]: at Jellyfin.Plugin.KodiSyncQueue.EntryPoints.UserSyncNotification.UpdateTimerCallback(Object state)
FFmpeg logs
Client / Browser logs
No response
Relevant screenshots or videos
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
errror
added
the
bug
This PR or Issue describes or fixes something that isn't working
label
Nov 12, 2024
I disabled the kodisyncqueue plugin a few days ago. Since then, the error was not reported any more. So it definitely has something to do with kodisyncqueue. Any news about my report?
This issue respects the following points:
Description of the bug
Since upgrading to Jellyfin 10.10, the error
An error has occurred in UserUpdateTimerCallback
shows up in the logs, whenever a replay is stopped.Reproduction steps
What is the current bug behavior?
The messages mentions in the logs section are shown in the log.
What is the expected correct behavior?
The log should only report, that the playback has stopped, but not an error in UserUpdateTimerCallback and corresponding Exception and backtrace.
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.1
Environment
Jellyfin logs
FFmpeg logs
Client / Browser logs
No response
Relevant screenshots or videos
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: