[Issue]: Unable to access settings #5708

Closed
opened 2026-02-07 02:10:13 +03:00 by OVERLORD · 8 comments
Owner

Originally created by @gogo199432 on GitHub (May 12, 2024).

Please describe your bug

weird bug I'm having with 10.9 . Almost all my settings pages are invisible / it looks like they are slid up over the top of the screen. I can just barely make out some UI elements.

The following pages load for some reason: Notifications, Extensions/Catalogue, Extensions/Repos, Library/(bottom 3 options), Playback/(bottom 3 options)

kép

Reproduction Steps

Just simply "apt upgrade"-d my bookworm Debian box

Jellyfin Version

10.9.0

if other:

No response

Environment

- OS: Debian 12 (bookworm)
- Linux Kernel: 6.x
- Virtualization: Proxmox VM
- Clients: Browser (Firefox and Chrome)
- Browser: Firefox 125.0.3 and Chrome

Jellyfin logs

Could not access logs page. Systemctl didn't print anything at all.

FFmpeg logs

No response

Please attach any browser or client logs here

No response

Please attach any screenshots here

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
Originally created by @gogo199432 on GitHub (May 12, 2024). ### Please describe your bug weird bug I'm having with 10.9 . Almost all my settings pages are invisible / it looks like they are slid up over the top of the screen. I can just barely make out some UI elements. The following pages load for some reason: Notifications, Extensions/Catalogue, Extensions/Repos, Library/(bottom 3 options), Playback/(bottom 3 options) ![kép](https://github.com/jellyfin/jellyfin/assets/9107561/e452d53f-a43f-4ef9-8da2-2bda28d11eff) ### Reproduction Steps Just simply "apt upgrade"-d my bookworm Debian box ### Jellyfin Version 10.9.0 ### if other: _No response_ ### Environment ```markdown - OS: Debian 12 (bookworm) - Linux Kernel: 6.x - Virtualization: Proxmox VM - Clients: Browser (Firefox and Chrome) - Browser: Firefox 125.0.3 and Chrome ``` ### Jellyfin logs ```shell Could not access logs page. Systemctl didn't print anything at all. ``` ### FFmpeg logs _No response_ ### Please attach any browser or client logs here _No response_ ### Please attach any screenshots here _No response_ ### Code of Conduct - [X] I agree to follow this project's Code of Conduct
OVERLORD added the bug label 2026-02-07 02:10:13 +03:00
Author
Owner

@jellyfin-bot commented on GitHub (May 12, 2024):

Hi, it seems like your issue report has the following item(s) that need to be addressed:

  • The format of the environment section has been altered from the template.

This is an automated message, currently under testing. Please file an issue here if you encounter any problems.

@jellyfin-bot commented on GitHub (May 12, 2024): Hi, it seems like your issue report has the following item(s) that need to be addressed: - The format of the environment section has been altered from the template. This is an automated message, currently under testing. Please file an issue [here](https://github.com/jellyfin/jellyfin-triage-scripts/issues) if you encounter any problems.
Author
Owner

@crobibero commented on GitHub (May 12, 2024):

Try clearing browser cache.
Logs can be also be found directly on disk.

@crobibero commented on GitHub (May 12, 2024): Try clearing browser cache. Logs can be also be found directly on disk.
Author
Owner

@gogo199432 commented on GitHub (May 12, 2024):

I have tried cleaning cache. Also as described I tried 2 separate browsers, same behaviour

@gogo199432 commented on GitHub (May 12, 2024): I have tried cleaning cache. Also as described I tried 2 separate browsers, same behaviour
Author
Owner

@thornbill commented on GitHub (May 12, 2024):

Any errors present in the browser console?

@thornbill commented on GitHub (May 12, 2024): Any errors present in the browser console?
Author
Owner

@gogo199432 commented on GitHub (May 12, 2024):

There are no actual errors in either journalctl or in the browser console. Last log is for logging in on the server side.

@gogo199432 commented on GitHub (May 12, 2024): There are no actual errors in either journalctl or in the browser console. Last log is for logging in on the server side.
Author
Owner

@mrboobek commented on GitHub (May 12, 2024):

Same here, after upgrading to latest docker cointainer from linuxserver.io I can't enter settings (blank screen).

Edit: Ok, after fresh install everything work as it should, looks like it was some third party skin error.

@mrboobek commented on GitHub (May 12, 2024): Same here, after upgrading to latest docker cointainer from linuxserver.io I can't enter settings (blank screen). Edit: Ok, after fresh install everything work as it should, looks like it was some third party skin error.
Author
Owner

@gogo199432 commented on GitHub (May 13, 2024):

Apologies, apparenly I'm an idiot and I did have custom css too. I don't even remember importing it, must have been a couple of years ago. After deleting it from branding.xml, the settings load fine. I'll be closing this ticket :)

@gogo199432 commented on GitHub (May 13, 2024): Apologies, apparenly I'm an idiot and I did have custom css too. I don't even remember importing it, must have been a couple of years ago. After deleting it from branding.xml, the settings load fine. I'll be closing this ticket :)
Author
Owner

@keesfluitman commented on GitHub (May 13, 2024):

Apologies, apparenly I'm an idiot and I did have custom css too. I don't even remember importing it, must have been a couple of years ago. After deleting it from branding.xml, the settings load fine. I'll be closing this ticket :)

Didnt work for me. i had a theme activated as well. Tried to delete the theme plugin manually, but no look to see the content yet to do anything. I guess i should go back to a backup, remove the theme and do it then. Or find if i can use CLI to deactivate the plugin or theme.

<?xml version="1.0" encoding="utf-8"?>
<BrandingOptions xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <LoginDisclaimer />
  <CustomCss>@import url('https://ctalvio.github.io/Kaleidochromic/default_style.css');:root {--accent: 98.00787045,121.00999580324999,204.99450000000002;}
:root {--rounding: 12px;}
</CustomCss>
  <SplashscreenEnabled>false</SplashscreenEnabled>
</BrandingOptions>

This is my branding.xml
removing the custom css doesnt help.

@keesfluitman commented on GitHub (May 13, 2024): > Apologies, apparenly I'm an idiot and I did have custom css too. I don't even remember importing it, must have been a couple of years ago. After deleting it from branding.xml, the settings load fine. I'll be closing this ticket :) Didnt work for me. i had a theme activated as well. Tried to delete the theme plugin manually, but no look to see the content yet to do anything. I guess i should go back to a backup, remove the theme and do it then. Or find if i can use CLI to deactivate the plugin or theme. ``` <?xml version="1.0" encoding="utf-8"?> <BrandingOptions xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <LoginDisclaimer /> <CustomCss>@import url('https://ctalvio.github.io/Kaleidochromic/default_style.css');:root {--accent: 98.00787045,121.00999580324999,204.99450000000002;} :root {--rounding: 12px;} </CustomCss> <SplashscreenEnabled>false</SplashscreenEnabled> </BrandingOptions> ``` This is my branding.xml removing the custom css doesnt help.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#5708