x11-themes/nuovo-icon-theme fails to install properly with the error: "Failed to update cache with icon /usr/share/icons/Nuovo" Which is repeated in every subsequent emerge of any icon theme. Additionally, there are no icons for Nuovo visible or usable in Plasma (a separate bug will be filed). This was mentioned on the forum in 2017 (see URL) Reproducible: Always Steps to Reproduce: 1. Install x11-themes/nuovo-icon-theme and notice the error message. 2. Try and install a few other icon themes and see the same error message. Actual Results: You receive the error message: "Failed to update cache with icon /usr/share/icons/Nuovo" Which repeats itself in a cascading effect when future icon themes are installed. Expected Results: The icon theme should properly install without any errors. The also cascades with other failures along the way, such as x11-themes/nou-icon-theme. See bug 695362.
"Additionally, there are no icons for Nuovo visible or usable in Plasma (a separate bug will be filed)." This is bug 695368
*** Bug 695368 has been marked as a duplicate of this bug. ***
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b6be580ab6d9f842d1f985d061ca18decd90d7be commit b6be580ab6d9f842d1f985d061ca18decd90d7be Author: Jeroen Roovers <jer@gentoo.org> AuthorDate: 2019-09-27 12:55:18 +0000 Commit: Jeroen Roovers <jer@gentoo.org> CommitDate: 2019-09-27 12:59:33 +0000 x11-themes/nuovo-icon-theme: gnome2-utils => xdg-utils Package-Manager: Portage-2.3.76, Repoman-2.3.17 Bug: https://bugs.gentoo.org/695364 Signed-off-by: Jeroen Roovers <jer@gentoo.org> x11-themes/nuovo-icon-theme/nuovo-icon-theme-0.5.ebuild | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-)
Not sure why the cache update fails. Perhaps the index.theme files are invalid?
Despite initial confusion in my filing of this bug, this is not a duplicate, but a separate bug related to 695362. Forum discussion (referred to as "Bug A" in the forum): https://forums.gentoo.org/viewtopic-p-8374466.html
The latest version (at this time 0.5-r1) of this package no longer has this problem.
