+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Collections broken after upgrading from 10.8.13 to 10.9.9 (/t-collections-broken-after-upgrading-from-10-8-13-to-10-9-9)
Collections broken after upgrading from 10.8.13 to 10.9.9 - Perseverant - 2024-08-12
They're broken server-side (I can't see them in Android TV 0.17 either, but I'm guessing it's a core functionality issue, not a client issue because...) When I try to go to collections via the web app, the blue circle just spins and spins and none of my collections show. I have a backup, so I'm not panicking, but would like to get this resolved.
I still see my collections in config\data\collections - they're just not showing in the front-end UI.
Anything I can provide to aid in troubleshooting this one? I did search other threads, and I saw mention of collections getting deleted if a server is unavailable at startup, but that wouldn't be relevant to me since my docker instance and my files are all living on the same Synology NAS.
RE: Collections broken after upgrading from 10.8.13 to 10.9.9 - TheDreadPirate - 2024-08-12
Can you share your log via pastebin? Preferably the log file that contains the first startup post-upgrade.
RE: Collections broken after upgrading from 10.8.13 to 10.9.9 - Perseverant - 2024-08-12
(2024-08-12, 02:52 AM)TheDreadPirate Wrote: Can you share your log via pastebin? Preferably the log file that contains the first startup post-upgrade.Here you are. I think this should capture things. There is a log for tomorrow, which I haven't even hit yet, so not sure what's up with the timestamps of things, but hopefully this is what's needed. Thanks for taking a look:
[ removed ]
RE: Collections broken after upgrading from 10.8.13 to 10.9.9 - TheDreadPirate - 2024-08-12
Set this docker environment variable to 0.
DOTNET_SYSTEM_GLOBALIZATION_INVARIANT
RE: Collections broken after upgrading from 10.8.13 to 10.9.9 - Perseverant - 2024-08-12
(2024-08-12, 04:23 AM)TheDreadPirate Wrote: Set this docker environment variable to 0.
DOTNET_SYSTEM_GLOBALIZATION_INVARIANT
That fixed collections. Thank you very much!
Since I have no idea what I just changed and Google searches are not being particularly enlightening, can you help me understand in layman's terms what I just changed and what any downstream implications of that change are (e.g. With that disabled x will no longer work etc.)
RE: Collections broken after upgrading from 10.8.13 to 10.9.9 - TheDreadPirate - 2024-08-12
I think this has to do with different defaults for DOTNET in newer versions of Jellyfin. When DOTNET_SYSTEM_GLOBALIZATION_INVARIANT is set to 1, DOTNET it will not process anything that has non-English characters in it. That can be CJK, that can be German umlauts, anything not English will cause DOTNET to stop.
Setting that environment variable to 0 will allow non-English characters.
RE: Collections broken after upgrading from 10.8.13 to 10.9.9 - TheDreadPirate - 2024-08-12
Strangely, I've never had to set that variable to 0 on my plain Docker on Ubuntu test Jellyfin.