Appstreamcli hanging with 100% CPU usage during update


It took quite some time for me to find this solution. When the average user starts googling this, they are going to find all sorts of things which do not apply, for example:

What a nightmare! This demonstrates why the system update utility needs to include a twitter-type client to inform the user of emerging issues related to broken update functionality. How else will the average user cope with a new issue like this, when there are so many possible causes for the same type of problem?

Yes I know, it poses the question of who should have the authority to broadcast alerts. Perhaps a majority vote by a jury of lead developers or team managers who could activate the feature by signing a proposed broadcast message with their PGP key. Moderators of the forum or the bug tracker would then submit proposals for broadcast...

0 0

Welcome to the Ubuntu Weekly Newsletter, Issue 466 for the week May 16 - 22, 2016.

In This Issue

Thank you [Community Council] Ubuntu Stats Danish Team Ubuntu 16.04 Release Party at Aarhus Library

LoCo Events

Dustin Kirkland: Byobu Hollywood Melodrama and Ubuntu Featured on NBCNews! Canonical Design Team: Colour palette updates Kubuntu Wire: Plasma 5.6.4 available in Kubuntu 16.04 Backports Ubuntu Touch on a tablet… it’s a N7 not a M10 Digital signage solution, Screenly, chooses Canonical’s Ubuntu Core In The Blogosphere Other Articles of Interest Featured Audio and Video Weekly Ubuntu Development Team Meetings Upcoming Meetings and Events Updates and Security for 12.04, 14.04, 15.10 and 16.04 And much more!

Mark Shuttleworth writes a short post thanking the Ubuntu Community Council for their proactive interest in keeping the community happy. He concludes: “They say that it’s tough at the top because the easy problems don’t get escalated, and that is...

0 0

I have a third-party Ubuntu repo at I'm using a Xenial test machine. After refreshing sources with apt-get update, I run appstreamcli as follows:

sudo tools/appstreamcli refresh --force --verbose --details

It then hangs, using 100% CPU. I've left it as long as 10 minutes and it still doesn't finish. The output is:

** (appstreamcli:13992): DEBUG: Refreshing AppStream cache ** (appstreamcli:13992): DEBUG: Reading: /usr/share/app-info/xmls/org.freedesktop.fwupd.xml ** (appstreamcli:13992): DEBUG: Reading: /var/lib/app-info/yaml/archive.ubuntu.com_ubuntu_dists_xenial_main_dep11_Components-amd64.yml.gz ** (appstreamcli:13992): DEBUG: Reading: /var/lib/app-info/yaml/archive.ubuntu.com_ubuntu_dists_xenial-updates_main_dep11_Components-amd64.yml.gz ** (appstreamcli:13992): DEBUG: Reading: /var/lib/app-info/yaml/archive.ubuntu.com_ubuntu_dists_xenial-updates_restricted_dep11_Components-amd64.yml.gz ** (appstreamcli:13992): DEBUG: Reading:...
0 0

Almost solved it...

Short answer: A corrupted calendar entry caused all the issues.

1) I found my main calendar and sorted it by days created.
2) I went through recent entries; some had invalid characters (Chineses unicode characters) for fields.
3) I deleted all entries from the last week (note tried starting up here and hang still occurred)
4) I then delete the "Calendar Cache" as well and it worked!
5) Widgets are working fine as well, as the iCal widget is happy again.

PROBLEM STILL OCCURS: Somewhere, some how the OS keeps re-generating the bad entries!

Apparently somewhere the OS is keeping another copy of the calendar and it would re-generate (with bad entries) the calendar if they were deleted.

If anyone knows how it's doing this (the journaled file system perhaps?) I'd love to know.

=====[ UPDATE 10/1 11:40pm EST ]===== Solved but man I don't wish this on anyone. So everything above is correct; my...

0 0

There are some operations that hang on one of my repositories:

git gc: hangs with 100% usage at "Counting objects: 7409"

when I launch gitk, it launches this command, which also hangs with 100% CPU usage:

git log --no-color -z --pretty=raw --parents --boundary 6ca9fbc0393cbc05e6ef7d67768ff1570e3fc42e 5741492043ebbc19013baf8c1c162b32b0e37ce5 6732226ff033e0d0dcdb47aa5c69d09551252caa 16871466fdae51bbf3dbeabd5dfbf2b02d4da03b e87ffba9df6cd03e0ea1c91821e8f2d3f0af2ca6 fb6abea427f3f4770caed5a4b31deeac606d5391 08671dcf23c663efa9758006af71e3281c119bc8 7cdbf2f37bc64ec765c961af0d6bd301f1cc0826 239d75a028f0eb6141ab5d32b008994367f08edf d6c135ae2ce4a099dfc444dba1e5bd29c7a82e2e 80d40034e9bd2eca48b2833a7846fd097a4e3f60 5741492043ebbc19013baf8c1c162b32b0e37ce5 faf15d38deb1abc2359f6d40315cf089331ba01b f0f1feaf60dea3eae104e5d09a3edb0dcb7f22a3 d9758d39749aa1717d43cf5483027a006f41f09c dccc73a3107c69f8020dce655c2eb10c6d0a6e2f d9758d39749aa1717d43cf5483027a006f41f09c...

0 0
0 0
please report to ZA support. Link in my signature. Here running Skype 4.1 on VISTA and ZAX 9 and have no issues whatsoever.
Also try to remove skype and reinstall from scratch.

You could also try to exclude skype from the antivirus on access scanning as well as trying to boot your PC only with ZA and check again, to isolate any other third party software potentially conflicting.

1.) Click Start -> Run
2.) Type MSConfig in the run box (or search box in VISTA) and click OK (ENTER in VISTA)
3.) Once in MSConfig, click the Startup Tab
4.) Remove the checks from everything except ZLClient
5.) Click the Services Tab
6.) Place a check in "Hide All Microsoft Services"
7.) Now remove checks from everything other than TrueVector Internet
Monitor and ForceField (if present), and click OK.
8.) Restart your computer

How does it work?

NOTE: You can place your computer back into a normal startup process by
going back...

0 0

Even genuine copies of windows have issues. There's mention of it going years back with svchost.exe using 100% of the cpu cycles. Not saying this is the case here, since there are many possibilities. In some cases it was a glitch with windows automatic update, on legit windows installs. Like any software, windows is prone to goof up.

My suggestion would be to open task manager, go to processes tab, make sure to click the check box at the lower left that says 'show processes from all users' - the list without checking that only shows a portion of the processes actually running and the culprit may not show up. Then look at your cpu column. Maybe even click on 'cpu' so it resorts the list from highest to lowest usage (just be aware that as different processes use different amounts of cpu this will cause the list to jump around and constantly resort...

0 0