Update-mime-database is getting very slow during apps installation

Bug #1816674 reported by Antonio Solida
28
This bug affects 6 people
Affects Status Importance Assigned to Milestone
shared-mime-info (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

The installation of some apps has become very slow due to the update-mime-database command that takes up a lot of time.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: shared-mime-info 1.10-1
ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 19 22:37:53 2019
InstallationDate: Installed on 2019-01-16 (34 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SourcePackage: shared-mime-info
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Antonio Solida (solida-antonio) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in shared-mime-info (Ubuntu):
status: New → Confirmed
Revision history for this message
Pierre-Antoine Champin (pchampin) wrote :

Same problem with 20.04.

I believe this is related to this issue: https://bbs.archlinux.org/viewtopic.php?id=255817 .

FTR, as `apt-daily.service` is running on startup, this was also increasing my boot-time significantly (although I found a workaround for this particular problem). Just to emphasize that this is a serious bug.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Could you give some details on how you workarounded the startup issue?

Revision history for this message
yurx cherio (cherio) wrote :

This has been a disk muncher for over a year now. The way I know the update is running through mime database is I hear my disks going into grinding mode.

Revision history for this message
Pierre-Antoine Champin (pchampin) wrote (last edit ):

@Sebastien Sorry for the late reply.

I recall that the workaround consisted in adding a random delay to the apt-daily task, so that it would not happen *right* at startup.

How exactly this was done, unfortunately, I didn't write it down :-/ but I think it was adding or creating the file ./system/apt-daily.timer, ensuring that it contained the RandomizedDelaySec directive.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.