The burn-in subtitles will become semi-transparent when enable hardware acceleration

[gnattu]

Now I doubt if it is a hardware or firmware bug of your specific iGPU handling the alpha channels.

[Giresharu]

This issue does not provide any relevant log information, and it only reproduces on my server. And I’ve reinstalled Jellyfin many times.
What should I do now?

Can you elaborate on which system your jellyfin run at and which distro you are using? Kernel Version?

Intel arc is still a bit new so there still could be some driver bugs left.

The kernel version inside both the host and the container are: 
Linux NAS 6.1.0-27-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.115-1 (2024-11-01) x86_64 GNU/Linux

I am now preparing to try installing it directly on Debian without using Docker, to see if there is any difference.
=== ===
After testing, the same situation occurs when directly installed on the host. Maybe I should look for clues related to Intel drivers.

[Fate]

This issue does not provide any relevant log information, and it only reproduces on my server. And I’ve reinstalled Jellyfin many times.
What should I do now?

Can you elaborate on which system your jellyfin run at and which distro you are using? Kernel Version?

Intel arc is still a bit new so there still could be some driver bugs left.

The kernel version inside both the host and the container are: 
Linux NAS 6.1.0-27-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.115-1 (2024-11-01) x86_64 GNU/Linux

I am now preparing to try installing it directly on Debian without using Docker, to see if there is any difference.
=== ===
After testing, the same situation occurs when directly installed on the host. Maybe I should look for clues related to Intel drivers.

Any chance you could try something newer?

Like ubuntu 24.10 or manjaro with the 6.11 kernel?

[Giresharu]

This issue does not provide any relevant log information, and it only reproduces on my server. And I’ve reinstalled Jellyfin many times.
What should I do now?

Can you elaborate on which system your jellyfin run at and which distro you are using? Kernel Version?

Intel arc is still a bit new so there still could be some driver bugs left.

The kernel version inside both the host and the container are: 
Linux NAS 6.1.0-27-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.115-1 (2024-11-01) x86_64 GNU/Linux

I am now preparing to try installing it directly on Debian without using Docker, to see if there is any difference.
=== ===
After testing, the same situation occurs when directly installed on the host. Maybe I should look for clues related to Intel drivers.

Any chance you could try something newer?

Like ubuntu 24.10 or manjaro with the 6.11 kernel?

Should I try change the host system environment, or should I switch to a Jellyfin image that uses Ubuntu as its environment? 
It’s not convenient for me to change the host system environment.

[TheDreadPirate]

Do your debian sources pull from non-free and non-free-firmware?

[Giresharu]

Do your debian sources pull from non-free and non-free-firmware?

I installed from the complete DVD ISO image downloaded from the Debian official website.

[TheDreadPirate]

I meant the configs in /etc/apt/sources.list.d/. Your sources would need "non-free" and "non-free-firmware" in the component list. I believe those two components are not included due to Debian only allowing "free" packages, by default.

Code:

deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware

[Giresharu]

I meant the configs in /etc/apt/sources.list.d/.  Your sources would need "non-free" and "non-free-firmware" in the component list.  I believe those two components are not included due to Debian only allowing "free" packages, by default.

Code:

deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware

Do you mean "/ect/apt/sources.list.d/docker.list"?
It is:

Code:

deb [arch=amd64 signed-by=/etc/apt/keyrings/docker.asc] https://download.docker.com/linux/debian  bookworm stable

Or "debian.sources"?
It is:

Code:

Types: deb                                                                                                                                     
URIs: http://deb.debian.org/debian                                                                                                             
Suites: bookworm bookworm-updates                                                                                                               
Components: main contrib non-free-firmware non-free                                                                                             
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg                                                                                       

Types: deb                                                                                                                                     
URIs: http://deb.debian.org/debian-security                                                                                                     
Suites: bookworm-security                                                                                                                       
Components: main contrib non-free-firmware non-free                                                                                             
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg                                                                                                         

[TheDreadPirate]

debian.sources. And it looks like you have all the non-free repos, so that's removes that as a factor.

[Giresharu]

This issue does not provide any relevant log information, and it only reproduces on my server. And I’ve reinstalled Jellyfin many times.
What should I do now?

Can you elaborate on which system your jellyfin run at and which distro you are using? Kernel Version?

Intel arc is still a bit new so there still could be some driver bugs left.

The kernel version inside both the host and the container are: 
Linux NAS 6.1.0-27-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.115-1 (2024-11-01) x86_64 GNU/Linux

I am now preparing to try installing it directly on Debian without using Docker, to see if there is any difference.
=== ===
After testing, the same situation occurs when directly installed on the host. Maybe I should look for clues related to Intel drivers.

Any chance you could try something newer?

Like ubuntu 24.10 or manjaro with the 6.11 kernel?

Recently, I finally had the opportunity to switch my system to Ubuntu 24.04.1 LTS, and I reinstalled the Jellyfin container in Docker with hardware acceleration enabled. The same issue can still be triggered. This seems to suggest that the problem is not due to the system itself.