Skip to main content
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: [SOLVED] libheif (Read 1284 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

[SOLVED] libheif

Earlier I updated and got an error message from libheif:
libheif-1.6.2-2

:: Running post-transaction hooks...
(2/3) Probing GDK-Pixbuf loader modules...
g_module_open() failed for /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-heif.so: libx265.so.188: cannot open shared object file: No such file or directory

Then I updated just now and that brought an updated x265-3.3-1 which had the missing /usr/lib/libx265.so.188, and when I reinstalled libheif there was no error message. There were no noticeable problems resulting from the earlier error message, but anyway, now it has successfully run the post transaction hook.

Re: libheif

Reply #1
Earlier I updated and got an error message from libheif:
libheif-1.6.2-2

:: Running post-transaction hooks...
(2/3) Probing GDK-Pixbuf loader modules...
g_module_open() failed for /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-heif.so: libx265.so.188: cannot open shared object file: No such file or directory

Then I updated just now and that brought an updated x265-3.3-1 which had the missing /usr/lib/libx265.so.188, and when I reinstalled libheif there was no error message. There were no noticeable problems resulting from the earlier error message, but anyway, now it has successfully run the post transaction hook.
The new x265 was just submitted to the stable repo, once the mirrors sync, you should get the update and it will be working as intended.

Re: libheif

Reply #2
If anyone got that error message by updating in those few hours and did not reinstall libheif after the new libx265 arrived it won't have run the post transaction hook properly though, which is what I was pointing out (possibly somewhat pedantically, as I'm not exactly sure what libheif or the gdk-pixbuf cache does tbh, but I'm sure it must be useful for something.  :D )
That hook might also be triggered sometimes for some other packages, but it does not run on every pacman transaction it seems.

This is what should have been written to the gdk-pixbuf cache:
Code: [Select]
$ gdk-pixbuf-query-loaders /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-heif.so
# GdkPixbuf Image Loader Modules file
# Automatically generated file, do not edit
# Created by gdk-pixbuf-query-loaders from gdk-pixbuf-2.40.0
#
"/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-heif.so"
"heif" 4 "pixbufloader-heif" "HEIF Image" "LGPL3"
"image/heif" "image/heic" ""
"heif" "heic" ""
"    ftyp" "xxxx    " 100

This is run by /usr/share/libalpm/hooks/gdk-pixbuf-query-loaders.hook
[Trigger]
Type = File
Operation = Install
Operation = Upgrade
Operation = Remove
Target = usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/*.so

[Action]
Description = Probing GDK-Pixbuf loader modules...
When = PostTransaction
Exec = /usr/bin/gdk-pixbuf-query-loaders --update-cache

Re: libheif

Reply #3
Going to bump libheif, so it will trigger correctly for you and others that may have issue.

Edit: Has been revbump'd slightly, so should be good after mirrors sync.

 

Re: libheif

Reply #4
That will certainly avoid any unexpected problems, that is very kind of you.


Re: libheif

Reply #6
libheif provides a new potential jpg replacement according to Wikipedia:
High Efficiency Image File Format (HEIF) is a container format for individual images and image sequences. It was developed by the Moving Picture Experts Group (MPEG) and is defined by MPEG-H Part 12 (ISO/IEC 23008-12). The MPEG group claims that twice as much information can be stored in a HEIF image as in a JPEG image of the same size, resulting in a better quality image. HEIF also supports animation, and is capable of storing more information than an animated GIF at a small fraction of the size.
The error has showed me something new!

Re: libheif

Reply #7
If you wouldn't mind and problem is solved, please mark it as Solved :)