Ubuntu
apt-xapian-index package

update-apt-xapian-index maxes CPU

Bug #769215 reported by Vallery Lancey on 2011-04-22

This bug report is a duplicate of: Bug #363695: update-apt-xapian-index uses too much CPU and memory. Edit Remove

This bug affects 11 people

Affects		Status	Importance	Assigned to	Milestone
	apt-xapian-index (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Binary package hint: apt-xapian-index

update-apt-xapian-index frequently maxes the CPU for about a minute. This happens after some updates, and after closing the software centre (even if nothing was installed or removed).

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: apt-xapian-index 0.41ubuntu6
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Fri Apr 22 14:28:57 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110410)
PackageArchitecture: all
ProcEnviron:
LANGUAGE=en_CA:en
LANG=en_CA.UTF-8
SHELL=/bin/bash
SourcePackage: apt-xapian-index
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Vallery Lancey (muscovy) wrote on 2011-04-22:

Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")

Revision history for this message

Serhiy (xintx-ua) wrote on 2011-05-20:

Can I make it run with less priority? Somehow set nice level for it not for one session but for every startup?

Revision history for this message

another_sam (anothersam) wrote on 2011-06-10:

Reading
http://www.enricozini.org/sw/apt-xapian-index/
I think it is totally impertinent to have this process wildly riding the CPU.

If this is pretending to keep Ubuntu Software Center running properly, I think this is not the right approach. What happened to the good ol' apt-get update?

Please don't plague Ubuntu with this kind of indexers. The only unasked task I want my PC to do is the update-manager looking for updates, once each 24h, during 30 seconds.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2011-09-29:

Status changed to 'Confirmed' because the bug affects multiple users.