Bug 13073

Summary: can't get the rootfs build , postinstall intercept hook 'update_icon_cache' failed
Product: [Runtime] Installation Reporter: Islam Essam <islam.essam.dev>
Component: InstallationAssignee: Ross Burton <ross.burton>
Status: RESOLVED WORKSFORME QA Contact:
Severity: major    
Priority: Medium CC: kevin.tian
Version: 2.6   
Target Milestone: 2.8   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know
Attachments:
Description Flags
Error report none

Description Islam Essam 2018-12-11 20:28:23 UTC
Created attachment 4401 [details]
Error report

http://errors.yoctoproject.org/Errors/Details/211337/
Comment 1 Ross Burton 2018-12-13 15:47:02 UTC
The log says this:

TOPDIR/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/intercept_scripts-8130062cc577a1d3a8bf6051c69d8d7d676e5cf9cad3a7da37426a98dfd13ec0/update_icon_cache: line 6: TOPDIR/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/recipe-sysroot-native//gdk-pixbuf-2.0/gdk-pixbuf-query-loaders: No such file or directory

That's right, the path should be .../recipe-sysroot-native/usr/bin/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders.  Note the missing usr/bin in the middle.

Is there anything non-standard about this build configuration?
Comment 2 Ross Burton 2018-12-13 15:52:07 UTC
I meant usr/lib not usr/bin.

The error comes from the update_icon_cache intercept:

	$STAGING_DIR_NATIVE/${libdir_native}/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders --update-cache

gtk-icon-cache installs this intercept:

	$INTERCEPT_DIR/postinst_intercept update_icon_cache ${PKG} \
		mlprefix=${MLPREFIX} \
		libdir_native=${libdir_native}


bitbake.conf defines libdir_native:

	libdir_native = "${prefix_native}/lib"
Comment 3 Islam Essam 2019-01-15 22:06:20 UTC
the only change is that i am using it on Ubuntu 18.04, but everything else is standard
Comment 4 Ross Burton 2019-06-04 13:45:04 UTC
Can you still replicate this?  Did you find the problem?
Comment 5 Ross Burton 2019-06-13 15:06:38 UTC
No reply, assuming no.  If you can replicate this please reopen the bug with more details.