mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-01-23 23:20:51 +01:00
[Issue]: UPnP requests fail if the meta data contains control characters #4667
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#4667
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 @iamsrp on GitHub (Feb 24, 2023).
Please describe your bug
Retrieving data via UPnP will fail with an exception in the server and a 400 error in the client if an MP3 has control characters in its meta-data. The exception is something like:
My reproducer script is:
However, the current
upnpyseems to be buggy and doesn't like Jellyfin for some reason, so you might need to use my tweaked version: https://github.com/iamsrp/upnpyThanks,
srp
Jellyfin Version
Other
if other:
10.8.4
Environment
Jellyfin logs
FFmpeg logs
Please attach any browser or client logs here
N/A
Please attach any screenshots here
N/A
Code of Conduct
@jellyfin-bot commented on GitHub (Jun 25, 2023):
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 master branch, 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.
@iamsrp commented on GitHub (Jun 29, 2023):
[Bump]
@jellyfin-bot commented on GitHub (Oct 29, 2023):
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.
@iamsrp commented on GitHub (Oct 29, 2023):
[keepalive]
@cvium commented on GitHub (Oct 29, 2023):
Is there any way you can test this on unstable (backup your db etc.)?
@iamsrp commented on GitHub (Oct 29, 2023):
Hmm, thanks for the nudge here. I just discovered that, since I logged this, Ubuntu commented out my jellyfin source when it upgraded to
jammy. I'm upgrading now and will see if that fixes it.If it doesn't, work then do I just replace
mainwith unstable in this?And upgrade? I'm assuming that backing up the DB just means a tarball of
/var/lib/jellyfin, correct?@cvium commented on GitHub (Oct 29, 2023):
I use two separate installs, so I don't know for certain. If that folder contains your library.db and jellyfin.db files, then that sounds about right.
@iamsrp commented on GitHub (Oct 29, 2023):
Well, hurrah for procrastination. I upgraded to the latest version and my reproducer will no longer reproduce. That either means that the bad metadata has vanished since logging this (unlikely) or that the issue has been since fixed.
Either way, since I have no reproducer at this point there's nothing actionable here, so I'll close this issue.
Thanks for the help!
srp