Upgrade to 10.7.0 removes library access from users #2779

Closed
opened 2025-12-21 21:06:20 +01:00 by backuprepo · 1 comment
Owner

Originally created by @brianjmurrell on GitHub (Mar 12, 2021).

Describe the bug
After upgrading to 10.7.0 none of my users has any media. Investigating it appears that all of the User->Library selections have been cleared.

System (please complete the following information):

  • OS: Fedora 33
  • Virtualization: None
  • Clients: Browser
  • Browser: Chrome 88
  • Jellyfin Version: 10.7.0
  • Playback: N/A
  • Installed Plugins: Unknown
  • Reverse Proxy: None
  • Base URL: none
  • Networking: Native
  • Storage: Local

To Reproduce

  1. On a system with multiple users and multiple libraries, upgrade to 10.7.0
  2. Log in as a user

Expected behavior
Should see media in the associated libraries as it was before the upgrade.

Originally created by @brianjmurrell on GitHub (Mar 12, 2021). **Describe the bug** After upgrading to 10.7.0 none of my users has any media. Investigating it appears that all of the User->Library selections have been cleared. **System (please complete the following information):** - OS: Fedora 33 - Virtualization: None - Clients: Browser - Browser: Chrome 88 - Jellyfin Version: 10.7.0 - Playback: N/A - Installed Plugins: Unknown - Reverse Proxy: None - Base URL: none - Networking: Native - Storage: Local **To Reproduce** <!-- Steps to reproduce the behavior: --> 1. On a system with multiple users and multiple libraries, upgrade to 10.7.0 2. Log in as a user **Expected behavior** Should see media in the associated libraries as it was before the upgrade.
backuprepo 2025-12-21 21:06:20 +01:00
  • closed this issue
  • added the
    bug
    stale
    labels
Author
Owner

@stale[bot] commented on GitHub (Jul 10, 2021):

This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.
If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or nightlies, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.
This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.

@stale[bot] commented on GitHub (Jul 10, 2021): This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments. If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or nightlies, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label. This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on [Matrix or Social Media](https://docs.jellyfin.org/general/getting-help.html).
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: starred/jellyfin#2779
No description provided.