mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-01-23 23:20:51 +01:00
[Issue]: Jellyfin crashed on login from specific device #5378
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#5378
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 @Spomyx on GitHub (Jan 11, 2024).
Please describe your bug
Hi,
A few days ago when tying to use Jellyfin on my Shield TV (2019) it behaved like the user was logged out, when trying to log in i'm sent back to the "select user" screen and if i try a second time, jellyfin closes and says that a crash report has been sent to the server.
I think it happened after the Jellyfin for android TV update 0.16.3 but i think it is a server issue when i read the logs.
I have other devices running latest Jellyfin for android TV which doesn't have this issue and i can confirm i can login with this user on every device i could test.
I feel like the database throws an issue but only when connecting with this device.
Any help appreciated...
Regards,
Jellyfin Version
10.8.13
if other:
No response
Environment
Jellyfin logs
FFmpeg logs
No response
Please attach any browser or client logs here
No response
Please attach any screenshots here
No response
Code of Conduct
@felix920506 commented on GitHub (Jan 11, 2024):
Hi, please provide the server version you are running.
@Spomyx commented on GitHub (Jan 11, 2024):
I forgot sorry, I'm running latest 10.8.13
@solidsnake1298 commented on GitHub (Jan 12, 2024):
Are you able to log in at all on your Shield? If you are, on the home screen of the Jellyfin app, navigate to the gear into in the top right, go to developer options and enable sending crash logs to the server. When the Jellyfin Android TV crashes next it will send a log to your server. The log appears in the same directory as the log you provided and the file name will begin with "upload".
Share that log with us.
@Spomyx commented on GitHub (Jan 12, 2024):
No I can't login at all on the shield.
In fact there's almost nothing I can do on the shield except add an account, change the server or try logging in with my current account.
I may add that I already tried cleaning up the app datas or reinstalling it.
I tried logging in with a different account on my shield and it works
@nielsvanvelzen commented on GitHub (Jan 12, 2024):
This means your Jellyfin database is corrupted so it was unable to save the crash logs generated by the app. Which are likely caused by this same issue.
@Spomyx commented on GitHub (Jan 12, 2024):
That's what I understand from the logs too but I don't understand why it only happens on this specific user/device combo.
In addition I'm very positive there were no storage incident or any other kind of issue on my server between the last working state and now that would explain the corruption.
All of this makes it very hard to troubleshoot without database knowledge, this looks like a very specific corruption
@barronpm commented on GitHub (Jan 12, 2024):
You can try opening the db in https://sqlitebrowser.org/, maybe try the devices table and try to access the row for your device? My best guess is that the problem would be there based on the behavior, but it's hard to know for sure.
@solidsnake1298 commented on GitHub (Jan 12, 2024):
Instead of opening SQLite you could go to the Jellyfin Dashboard on a PC and open the Devices menu, find any entries for your shield and delete them.
@Spomyx commented on GitHub (Jan 12, 2024):
I tried removing all occurences of my shield device in the jellyfin web interface, it worked for all but the one associated to my user (endless loading)
so i opened the jellyfin.db in sqlite browser and removed the associated line in the "Devices" table.
The device was correctly removed in the interface but the issue persists.
The behavior changed slightly in the client, i get "unable to connect to the server" and the app is not crashing anymore
The logs are slightly different too
@solidsnake1298 commented on GitHub (Jan 12, 2024):
Have you tried clearing the app cache for Jellyfin on your Shield?
@Spomyx commented on GitHub (Jan 12, 2024):
I reinstalled again so i guess it qualifies as a cache clear ?
@Spomyx commented on GitHub (Jan 15, 2024):
Hi,
i managed to fix it by investigating sqlite3 CLI
here is the error displayed:
and this simple command fixed it (even though errors are displayed):
after restarting JF with the recovered DB i can login successfully on my shield TV
I will mark it as resolved but i still have no idea what caused this issue.
Thanks to everyone who took time to answer.