Library thumbnail generation fails for one library

[Rumbah 8]

Hi,

I just noticed a problem with thumbnail gerneration for my movie library. I just get an empty picture. Running a new library metadata scan does not change it.

I already tried deleting the picture and run a new scan, deleting the picture and set an new one myually. Then deleting it again and run a new scan.

But everytime this new grey preview gets generated. It is there as I can delete it but the new generated is that one again.

 

My Emby server is version 4.7.6.0. The poster pictures inside the library work normally and there is no problem.

[Luke 42083]

HI there, try using the image editor to delete the existing image. Then run a library scan. Once it completes, see if you have an image after that. If not, then please attach the emby server log. Thanks.

[Rumbah 8]

Hi, sadly that does not fix it and now it happens for other libraries, too.

Here a log where it happens, seems something is crashing when building the picture.

embyserver.zip

[Happy2Play 9783]

So this suggests a platform specific issue.

Quote

The version of the native libSkiaSharp library (88.0) is incompatible with this version of SkiaSharp. Supported versions of the native libSkiaSharp library are in the range [80.2, 81.0).
    Source: SkiaSharp

Will have to look but thought this was mentions in another topic.

[Happy2Play 9783]

Error mentioned over here

So an Arch Linux package issue it looks like.

[Rumbah 8]

Hmm, yes, I use Arch Linux, too, and one or two days ago the following updates got installed:

[2022-08-11T13:03:09+0200] [ALPM] upgraded dotnet-host (6.0.6.sdk106-1 -> 6.0.8.sdk108-1)
[2022-08-11T13:03:09+0200] [ALPM] upgraded dotnet-runtime (6.0.6.sdk106-1 -> 6.0.8.sdk108-1)
[2022-08-11T13:03:09+0200] [ALPM] upgraded aspnet-runtime (6.0.6.sdk106-1 -> 6.0.8.sdk108-1)
[2022-08-11T13:03:09+0200] [ALPM] upgraded skia-sharp (2.80.3-1 -> 2.88.0-1)

So is the updated skia-sharp package the culprit? Then I'll report it to the emby-server package maintainer. It's the only skia package installed for me.

 

Or will it need a change in Emby so I'll have to wait for the next Emby version?

Edited August 13, 2022 by Rumbah

[Happy2Play 9783]

Will have to wait on the devs to comment but suggest that update is the culprit.

[Luke 42083]

17 hours ago, Rumbah said:

Hmm, yes, I use Arch Linux, too, and one or two days ago the following updates got installed:

[2022-08-11T13:03:09+0200] [ALPM] upgraded dotnet-host (6.0.6.sdk106-1 -> 6.0.8.sdk108-1)
[2022-08-11T13:03:09+0200] [ALPM] upgraded dotnet-runtime (6.0.6.sdk106-1 -> 6.0.8.sdk108-1)
[2022-08-11T13:03:09+0200] [ALPM] upgraded aspnet-runtime (6.0.6.sdk106-1 -> 6.0.8.sdk108-1)
[2022-08-11T13:03:09+0200] [ALPM] upgraded skia-sharp (2.80.3-1 -> 2.88.0-1)

So is the updated skia-sharp package the culprit? Then I'll report it to the emby-server package maintainer. It's the only skia package installed for me.

 

Or will it need a change in Emby so I'll have to wait for the next Emby version?

Emby Server is currently built against SkiaSharp 2.80.3, not the newer 2.88.0. So yes this is the problem. You'll need to roll back SkiaSharp.

On other platforms we embed Skia directly into the server package and this never becomes a problem, but since this isn't the ArchLinux way of doing things, we just use whatever is on your system.

[Happy2Play 9783]

@chowbok are you following this as you mentioned this issues in your topic, but appears more ArchLinux users are reporting this.

Edited August 13, 2022 by Happy2Play

[chowbok 132]

Yes. Downgrading skia-sharp did not solve my problem, unfortunately.

[Luke 42083]

Hi, downgrading to what? Why do you think it didn't solve the issue?

[chowbok 132]

I downgraded skia-sharp to 2.80.3 but I'm still not able to play all the files from the tag page, as outlined in the other thread.

[alucryd 316]

A new 4.7.6.0-2 package is up, it bundles a prebuilt skia-sharp. Please give it a try. Downgrading should have fixed your issue though, so you might have another issue on top of skia-sharp.

[Rumbah 8]

Yes, I can confirm that downgrading fixed the issue mentioned here.

And I just tested 4.7.6.0-2, works like a charm. Thank you for your hard work!