Bug 13859

Summary: adwaita-icon-theme cannot find GTK+3 gtk-update-icon-cache command
Product: [Build System, Metadata & Runtime] OE-Core Reporter: cyril.franceschini
Component: oe-core otherAssignee: Unassigned <unassigned>
Status: CLOSED FIXED QA Contact:
Severity: minor    
Priority: Medium+ CC: akuster, randy.macleod
Version: 2.6.4   
Target Milestone: 3.2 M2   
Hardware: Other   
OS: arm   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description cyril.franceschini 2020-04-06 13:55:03 UTC 
When I try to install the packagegroup-core-x11-base package, it gives me an error at runtime "configurating" task.

The adwaita-icon-theme recipe inherits the gtk-icon-cache class but the gtk+3 recipe adds an alternative to the gtk-update-icon-cache comand as "gtk-update-icon-cache-3.0". Unfortunately "update-alternative" occurs AFTER the adwaita-icon-theme configuration. It leads to an error: "gtk-update-icon-cache: command not found".

Here is the output:

Configuring libharfbuzz0.
Configuring libxdmcp6.
Configuring libatk-1.0-0.
Configuring libfontenc1.
Configuring libxau6.
Configuring libxcb1.
Configuring libx11-6.
Configuring libxmuu1.
Configuring mini-x-session.
update-alternatives: Linking /usr/bin/x-session-manager to /usr/bin/mini-x-session
Configuring libgdk-pixbuf-2.0-0.
Configuring libgdk-pixbuf-2.0-loader-png.
Configuring libxext6.
Configuring libxi6.
Configuring libxtst6.
Configuring libatspi0.
Configuring libatk-bridge-2.0-0.
Configuring xserver-xf86-config.
Configuring libxkbfile1.
Configuring xkbcomp.
Configuring libxrender1.
Configuring libxft2.
Configuring hicolor-icon-theme.
Configuring adwaita-icon-theme-symbolic.
///var/lib/opkg/info/adwaita-icon-theme-symbolic.postinst: line 14: gtk-update-icon-cache: command not found
Configuring libxcb-shm0.
Configuring libdrm2.
Configuring libglapi0.
Configuring mesa-megadriver.
Configuring libpciaccess0.
Configuring libpixman-1-0.
Configuring libxfont2-2.
Configuring rgb.
Configuring xf86-input-libinput.
Configuring xserver-xorg.
Configuring xf86-video-fbdev.
Configuring libxcb-dri2-0.
Configuring libglib-2.0-utils.
Configuring libxcb-util1.
Configuring libxfixes3.
Configuring libxdamage1.
Configuring libxxf86vm1.
Configuring libx11-xcb1.
Configuring libxcb-glx0.
Configuring libgl-mesa.
Configuring libxcb-render0.
Configuring libcairo2.
Configuring libcairo-gobject2.
Configuring libepoxy0.
Configuring libxcomposite1.
Configuring libxcursor1.
Configuring libxrandr2.
Configuring libfribidi0.
Configuring pango.
Configuring glibc-gconv.
Configuring glibc-gconv-iso8859-1.
Configuring liberation-fonts.
FC_DEBUG=1
/usr/share/fonts: skipping, existing cache is valid: 0 fonts, 2 dirs
/usr/share/fonts/truetype: skipping, existing cache is valid: 21 fonts, 0 dirs
/usr/share/fonts/ttf: skipping, existing cache is valid: 12 fonts, 0 dirs
/home/root/.local/share/fonts: skipping, no such directory
/home/root/.fonts: skipping, no such directory
/var/cache/fontconfig: cleaning cache directory
/home/root/.cache/fontconfig: not cleaning non-existent cache directory
/home/root/.fontconfig: not cleaning non-existent cache directory
fc-cache: succeeded
Configuring libgdk-pixbuf-2.0-loader-gif.
Configuring libgdk-pixbuf-2.0-loader-jpeg.
Configuring libgdk-pixbuf-2.0-loader-xpm.
Configuring libgtk-3.0.
update-alternatives: Linking /usr/bin/gtk-update-icon-cache to /usr/bin/gtk-update-icon-cache-3.0
Configuring libxinerama1.
Configuring libxxf86dga1.
Configuring libpcre2.
Configuring libvte-2.91-0.
Configuring matchbox-terminal.
Configuring util-linux-mcookie.
Configuring xinit.
Configuring xserver-nodm-init.
Comment 1 Randy MacLeod 2020-04-09 14:45:27 UTC 
Is this reproducible or a race in the build?
Are you able to reproduce it in a more recent supported release or on master?
Comment 2 cyril.franceschini 2020-04-09 14:47:10 UTC 
It happens 100% of the time at first boot (package configuring).
I'm not able to use another branch.
Comment 3 Randy MacLeod 2020-04-14 09:18:52 UTC 
Hi Cyril,

Unfortunately 2.6 is no longer supported by the YoctoProject team:
   https://wiki.yoctoproject.org/wiki/Releases

It's possible that someone will try to reproduce this on a supported branch and fix it if it's still a problem. If you need support for 2.6, there are a number of companies that do that as briefly mentioned here:
   https://wiki.yoctoproject.org/wiki/FAQ#What_is_the_overall_support_plan_for_the_Yocto_Project.3F
Some YP members are listed here:
https://www.yoctoproject.org/ecosystem/members/

I'll leave this defect open for now in case someone takes an interest in it.
Comment 4 Randy MacLeod 2020-04-14 09:19:45 UTC 
Cyril provided the info needed so changing status back to New.
Comment 5 Armin Kuster 2020-08-06 08:03:37 UTC 
this is fixed in Master.

https://git.openembedded.org/openembedded-core/commit/?id=ec0888d73d7e7f811961f50f334c72fbc6b1d401

This breaks older releases so no backport.
Comment 6 Armin Kuster 2020-08-06 08:03:50 UTC 
.