starred/jellyfin
1
0
Fork 0
mirror of https://github.com/jellyfin/jellyfin.git synced 2026-07-16 05:43:54 +03:00
Code Issues 822 Packages Projects Releases 17 Wiki Activity

Live TV channels misplaced order when 'favourites at beginning' is activated. #7678

New Issue
Open
opened 2026-02-07 05:19:31 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-07 05:19:31 +03:00
Owner
Copy Link

Originally created by @gormogon250 on GitHub (Nov 3, 2025).

Description of the bug

After updating to 10.11.1 I've noticed that if 'favourites at beginning' is selected on Live TV, then random channels are misplaced. It's all in order when 'favourites at beginning' isn't selected, But on one account random channels such as 1,4,7,10,11,14,15,16,17,22,24,30 and 970 are also placed at the beginning despite not being favourites and on a different account it seems to be 134,160,320,321,605,9,20 seem to be placed randomly after channel 20.

Reproduction steps

  1. Have Live TV on server.
  2. Open Jellyfin
  3. Open Guide
  4. Activate 'place favourites at beginning' setting

What is the current bug behavior?

Now channels at some point should be not ordered by channel number despite the setting being on. it seems to be different numbers of channels and placement displacement for each account

What is the expected correct behavior?

Only the favourites should be misplaced at the beginning, and the rest of the channels should remain in order.

Jellyfin Server version

10.10.0+

Specify commit id

No response

Specify unstable release number

No response

Specify version number

No response

Specify the build version

10.11.1

Environment

- OS:
- Linux Kernel:
- Virtualization:
- Clients:
- Browser:
- FFmpeg Version:
- Playback Method:
- Hardware Acceleration:
- GPU Model:
- Plugins:
- Reverse Proxy:
- Base URL:
- Networking:
- Jellyfin Data Storage:
- Media Storage:
- External Integrations:

Jellyfin logs

n/a

FFmpeg logs

Client / Browser logs

No response

Relevant screenshots or videos

No response

Additional information

No response

Originally created by @gormogon250 on GitHub (Nov 3, 2025). ### Description of the bug After updating to 10.11.1 I've noticed that if 'favourites at beginning' is selected on Live TV, then random channels are misplaced. It's all in order when 'favourites at beginning' isn't selected, But on one account random channels such as 1,4,7,10,11,14,15,16,17,22,24,30 and 970 are also placed at the beginning despite not being favourites and on a different account it seems to be 134,160,320,321,605,9,20 seem to be placed randomly after channel 20. ### Reproduction steps 1. Have Live TV on server. 2. Open Jellyfin 3. Open Guide 4. Activate 'place favourites at beginning' setting ### What is the current _bug_ behavior? Now channels at some point should be not ordered by channel number despite the setting being on. it seems to be different numbers of channels and placement displacement for each account ### What is the expected _correct_ behavior? Only the favourites should be misplaced at the beginning, and the rest of the channels should remain in order. ### Jellyfin Server version 10.10.0+ ### Specify commit id _No response_ ### Specify unstable release number _No response_ ### Specify version number _No response_ ### Specify the build version 10.11.1 ### Environment ```markdown - OS: - Linux Kernel: - Virtualization: - Clients: - Browser: - FFmpeg Version: - Playback Method: - Hardware Acceleration: - GPU Model: - Plugins: - Reverse Proxy: - Base URL: - Networking: - Jellyfin Data Storage: - Media Storage: - External Integrations: ``` ### Jellyfin logs ```shell n/a ``` ### FFmpeg logs ```shell ``` ### Client / Browser logs _No response_ ### Relevant screenshots or videos _No response_ ### Additional information _No response_
OVERLORD added the buglive-tv labels 2026-02-07 05:19:31 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
EFjellyfin.db
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
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
Mirrored from GitHub Pull Request
 question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No Label bug live-tv
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#7678
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?