You are not logged in.
- Topics: Active | Unanswered
#1 2017-07-11 01:19:06
- Salkay
- Member
- Registered: 2014-05-22
- Posts: 619
The AppStream system cache was updated, but some errors were detected
I just updated my system this morning.
extra/appstream 0.11.1-1 0.11.1-2 -0.01 MiB 1.80 MiB
extra/appstream-qt 0.11.1-1 0.11.1-2 0.00 MiB 0.05 MiB
extra/archlinux-appstream-data 20170425-1 20170711-1 0.22 MiB 16.05 MiB
extra/intel-ucode 20170511-1 20170707-1 0.30 MiB 1.02 MiB
core/iproute2 4.12.0-1 4.12.0-2 0.07 MiB 0.66 MiB
extra/kdelibs 4.14.33-1 4.14.33-2 -0.24 MiB 12.15 MiB
core/libarchive 3.3.1-5 3.3.2-1 0.00 MiB 0.44 MiB
extra/libblockdev 2.9-1 2.10-1 0.03 MiB 0.15 MiB
community/libtommath 1.0-1 1.0-2 0.00 MiB 0.05 MiB
extra/mlt 6.4.1-6 6.4.1-7 -0.13 MiB 1.71 MiB
extra/qhull 2015.2-1 2015.2-2 0.06 MiB 0.86 MiB
extra/tidy 5.4.0-1 5.4.0-2 0.11 MiB 0.33 MiBAnd got the following message
:: Running post-transaction hooks...
...
(3/5) Updating the appstream index...
The AppStream system cache was updated, but some errors were detected, which might lead to missing metadata. Refer to the verbose log for more information.
error: command failed to execute correctlyWhat does that mean and should I be worried? If so, how can I fix it? Thanks in advance.
Offline
#2 2017-07-11 04:25:27
- amish
- Member
- Registered: 2014-05-10
- Posts: 470
Re: The AppStream system cache was updated, but some errors were detected
I get same error.
I rebooted and then manually ran this:
/usr/bin/appstreamcli refresh-cache --force --verboseIt does something and returns with exit code 2.
** (appstreamcli:1572): DEBUG: Added /usr/share/app-info/xmls to metadata search path.
** (appstreamcli:1572): DEBUG: Data did not change, no cache refresh needed.
** (appstreamcli:1572): DEBUG: Forcing refresh anyway.
** (appstreamcli:1572): DEBUG: Refreshing AppStream cache
** (appstreamcli:1572): DEBUG: Searching for data in: /usr/share/app-info/xmls
** (appstreamcli:1572): DEBUG: Reading: /usr/share/app-info/xmls/extra.xml.gz
** (appstreamcli:1572): DEBUG: Reading: /usr/share/app-info/xmls/core.xml.gz
** (appstreamcli:1572): DEBUG: Reading: /usr/share/app-info/xmls/community.xml.gz
** (appstreamcli:1572): DEBUG: Metadata ignored: Detected colliding ids: system/os/package/libreoffice-base.desktop was already added with the same priority.
** (appstreamcli:1572): DEBUG: Metadata ignored: Detected colliding ids: system/os/package/libreoffice-calc.desktop was already added with the same priority.
... more similar lines
** (appstreamcli:1572): DEBUG: Metadata ignored: Detected colliding ids: system/os/package/yabause.desktop was already added with the same priority.
** (appstreamcli:1572): DEBUG: WARNING: Ignored component 'xnc-gnome2.desktop': The component is invalid.
...
** (appstreamcli:1572): DEBUG: system/os/package/vim-latex extends system/os/package/gvim.desktop, but system/os/package/gvim.desktop was not found.
** (appstreamcli:1572): DEBUG: system/os/package/zathura-pdf-poppler.desktop extends system/os/package/zathura.desktop, but system/os/package/zathura.desktop was not found.
** (appstreamcli:1572): DEBUG: WARNING: Ignored component 'org.kde.plasma.systemmonitor.net': The component is invalid.
** (appstreamcli:1572): DEBUG: WARNING: Ignored component 'org.kde.plasma.icontasks': The component is invalid.
...
** (appstreamcli:1572): DEBUG: system/os/package/nautilus-sendto extends system/os/package/nautilus.desktop, but system/os/package/nautilus.desktop was not found.
** (appstreamcli:1572): DEBUG: WARNING: Ignored component 'org.kde.plasma.windowlist': The component is invalid.
...
** (appstreamcli:1572): DEBUG: WARNING: Ignored component 'org.kde.plasma.taskmanager': The component is invalid.
** (appstreamcli:1572): DEBUG: Stemming language is: en
The AppStream system cache was updated, but some errors were detected, which might lead to missing metadata. Refer to the verbose log for more information.However, everything seems to be running fine. But looks like appstream bug?
Last edited by amish (2017-07-11 04:26:54)
Offline
#3 2017-07-11 09:59:23
- mcloaked
- Member
- From: Yorkshire, UK
- Registered: 2012-02-02
- Posts: 1,240
Re: The AppStream system cache was updated, but some errors were detected
I decided to downgrade which completed without error:
# pacman -U /var/cache/pacman/pkg/archlinux-appstream-data-20170425-1-any.pkg.tar.xz
loading packages...
warning: downgrading package archlinux-appstream-data (20170711-1 => 20170425-1)
resolving dependencies...
looking for conflicting packages...
Packages (1) archlinux-appstream-data-20170425-1
Total Installed Size: 16.44 MiB
Net Upgrade Size: -0.22 MiB
:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring [############################] 100%
(1/1) checking package integrity [############################] 100%
(1/1) loading package files [############################] 100%
(1/1) checking for file conflicts [############################] 100%
(1/1) checking available disk space [############################] 100%
:: Processing package changes...
(1/1) downgrading archlinux-appstream-data [############################] 100%
:: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Updating the appstream index...
AppStream cache update completed successfully.I will leave mine on the previous version until a fixed package update is available.
Edit: I just found https://bugs.archlinux.org/task/52190 so maybe this error output is nothing to worry about?
Last edited by mcloaked (2017-07-11 10:11:53)
Mike C
Offline
#4 2017-07-11 10:21:26
- Salkay
- Member
- Registered: 2014-05-22
- Posts: 619
Re: The AppStream system cache was updated, but some errors were detected
mcloaked wrote:
I just found https://bugs.archlinux.org/task/52190 so maybe this error output is nothing to worry about?
Hmm… yes possibly. The wording is slightly different, but it looks like the intent is the same.
Offline
#5 2017-07-11 19:47:24
- mcloaked
- Member
- From: Yorkshire, UK
- Registered: 2012-02-02
- Posts: 1,240
Re: The AppStream system cache was updated, but some errors were detected
Another update is available that installs without error:
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
Packages (1) archlinux-appstream-data-20170711-2
Total Download Size: 16.12 MiB
Total Installed Size: 16.73 MiB
Net Upgrade Size: 0.07 MiB
:: Proceed with installation? [Y/n]
:: Retrieving packages...
archlinux-appstream-data-20170711-2-any 16.1 MiB 3.98M/s 00:04 [###############################################] 100%
(1/1) checking keys in keyring [###############################################] 100%
(1/1) checking package integrity [###############################################] 100%
(1/1) loading package files [###############################################] 100%
(1/1) checking for file conflicts [###############################################] 100%
(1/1) checking available disk space [###############################################] 100%
:: Processing package changes...
(1/1) upgrading archlinux-appstream-data [###############################################] 100%
:: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Updating the appstream index...
AppStream cache update completed successfully.So version archlinux-appstream-data-20170711-2 now fixes the original problem so you can now mark this as SOLVED?
Last edited by mcloaked (2017-07-11 19:47:58)
Mike C
Offline
#6 2017-07-12 06:53:22
- Salkay
- Member
- Registered: 2014-05-22
- Posts: 619
Re: The AppStream system cache was updated, but some errors were detected
mcloaked wrote:
So version archlinux-appstream-data-20170711-2 now fixes the original problem so you can now mark this as SOLVED?
Yes, the recent update worked fine for me too. I'll leave the topic "unsolved" for now, because I would still like to know what the error meant, and whether it stuffed something up semi-permanently that the recent version did not fix.
Offline