Jellyfin Forum
Help with spurious Logo appearance - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Help with spurious Logo appearance (/t-help-with-spurious-logo-appearance)



Help with spurious Logo appearance - twodragonsrob - 2025-07-10

Hi all,

I need some help and I've had no luck trying to put together useful search terminology (so I'm sorry if this is a repeat).  A few days ago I noticed that movies had a spurious "Naruto" logo appearing on the individual movie page if that movie didn't already have a logo (see the attachments for what I mean).  As you can see from the Edit Images screen attachment, the "Naruto" logo isn't connected to the movie. I've tried to find it on the server without luck.  Interestingly, it's only appearing in the movie library, not in the other libraries on the server (which are also on separate external HDDs).  Does anyone have any clue as to what's gone on, and/or how to remove this behavior?

Thanks in advance


RE: Help with spurious Logo appearance - EFX - 2025-07-12

Have you tried disabling web cache and/or removing all meta data from movie then have it search for them again?


RE: Help with spurious Logo appearance - RostigerSpieler - 2025-07-15

I have added a Logo to TMDB if u need it to change the wrong logo.

https://www.themoviedb.org/tv/76318-20-000-leagues-under-the-sea/images/logos?image_language=en


RE: Help with spurious Logo appearance - Efficient_Good_5784 - 2025-07-15

The issue is that you have anime metadata providers enabled for a library that has non-anime stuff.
It's recommended to move your non-anime stuff to their own library. Then disable the anime providers for that.


RE: Help with spurious Logo appearance - twodragonsrob - 2025-07-16

Thanks the the help guys. Unfortunately none of it seemed to help. In the end, I deleted the library and then recreated it - it didn't take as long as I thought it would, and it appears to have sorted out the problem (although I still don't know what caused it).