As I cannot see how to re-open an existing bug, a new bug report that #363695 is rearing its ugly head again (look at the comments) Why not limit the CPU/mem usage of update-apt-xapian-index to 5% of the system? That way no one would even notice... (or make it an optional package instead of default...)
Better that then seeing lots of comments to a bug whose status has been "fix released" for years but apparently still bothers end-users...
uname --kernel-release&&lsb_release --all
3.13.0-54-generic
LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
Distributor ID: Ubuntu
Description: Ubuntu 14.04.2 LTS
Release: 14.04
Codename: trusty
apt-cache policy apt-xapian-index
apt-xapian-index:
Installed: 0.45ubuntu4
Candidate: 0.45ubuntu4
Version table:
*** 0.45ubuntu4 0
500 http://mirror.i3d.net/pub/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
What I expect to happen: *absolutely nothing* (visible in CPU/MEM monitor) ;-)
What happened instead: 100% of 1 core used for >10 seconds (didn't catch it starting)
