60 - 102% CPU usage when a repository throw security errors

[davidak]

In my case the hipchat.basecom.de repo that still uses SHA1!

root@unibook:/home/davidak# apt update
OK:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
OK:2 http://hipchat.basecom.de/clients/linux/apt stable InRelease                                                                          
Holen:3 http://security.ubuntu.com/ubuntu xenial-security InRelease [94,5 kB]                                                                                        
OK:4 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease                                                                                                    
OK:5 http://ppa.launchpad.net/ansible/ansible/ubuntu xenial InRelease                                                                                
OK:6 http://ppa.launchpad.net/elementary-os/stable/ubuntu xenial InRelease                                                                           
OK:7 http://de.archive.ubuntu.com/ubuntu xenial-backports InRelease                                                                                  
OK:8 http://ppa.launchpad.net/elementary-os/os-patches/ubuntu xenial InRelease                                                                       
OK:9 http://ppa.launchpad.net/webupd8team/atom/ubuntu xenial InRelease                                                                        
OK:10 http://archive.canonical.com xenial InRelease                                                                                           
OK:11 https://deb.nodesource.com/node_6.x xenial InRelease                                                            
Ign:12 http://download.opensuse.org/repositories/isv:/ownCloud:/desktop/Ubuntu_16.04  InRelease
OK:13 http://download.opensuse.org/repositories/isv:/ownCloud:/desktop/Ubuntu_16.04  Release
OK:15 https://dl.ring.cx/ring-nightly/ubuntu_16.04 ring InRelease
Es wurden 94,5 kB in 1 s geholt (75,3 kB/s).
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.       
Statusinformationen werden eingelesen.... Fertig
Aktualisierung für 16 Pakete verfügbar. Führen Sie »apt list --upgradable« aus, um sie anzuzeigen.
W: http://hipchat.basecom.de/clients/linux/apt/dists/stable/InRelease: Signature by key 69F57C04EA38EEE7A47E9BCCAAD4AA21729B5780 uses weak digest algorithm (SHA1)

Here is a strace of the packagekitd process: https://gist.github.com/davidak/f1af761d4319c655621122b853bccfee

This is a serious problem that was confirmed by 23 people on elementary OS.

https://bugs.launchpad.net/appcenter/+bug/1587975

I have to kill the process so the notebook fan stops blowing.

---

packagekit 1.0.11-2elementary0.4.4
elementary OS 0.4 Loki (Ubuntu 16.04 based) on a MacBook Pro (Retina)

[hughsie]

You need to file this downstream with elementary OS as we do no QA on that distro whatsoever and I don't know what downstream patches have been used. You might be able to get someone to help you with the aptcc backend on the mailing list or in the IRC channel but you'll need the output of --verbose and perhaps a backtrace with all the debugging symbols installed. Sorry I can't be more helpful.

[ximion]

Jup, please provide the information @hughsie mentioned and file a new bug - from quickly skimming the linked bug report, it looks like AppCenter isn't very smart in requesting changelog downloads. The 100% CPU usage bug looks indeed like some issue in aptcc, maybe file a new bug for that, ideally with information on how to reproduce it (when I tested AppCenter a while back, I didn't see this issue).