[Bug 1816045] Re: secureboot-db: release upgrade from 16.04 to 18.04 modifies changelog.gz but resets mtime
Thanks for explaining. I am using an internally developed, Python-based
backup system. It makes backups from Btrfs snapshots and regularly
verifies the integrity of the entire restore process. The verification
shows discrepancies such as the one above.
As most backup systems rely on mtime to detect changes for performance,
I suppose this is really a widespread problem. It probably goes
undetected in the majority of cases as backup systems usually don't do
100% integrity verification lacking file system snapshots.
My backup system uses regexp-based filtering to switch from mtime to
content change detection. In this case the relevant line in its YAML
configuration file is:
- { pattern: '^usr/share/doc/[^/]*/changelog[^/]*$', filter:
compare-contents }
The problem is not just limited to package installation files as this
excerpt shows:
- { pattern: '^var/lib/sudo/', filter: compare-contents }
- { pattern: '^var/lib/machines$', filter: compare-contents }
- { pattern: '^var/cache/man/(.*/)?index\.db$', filter: compare-contents }
And there are even more entries in my list. I wonder whether tinkering
with mtime is really such a good idea...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816045
Title:
secureboot-db: release upgrade from 16.04 to 18.04 modifies
changelog.gz but resets mtime
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/secureboot-db/+bug/1816045/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891515] [NEW] ucf overwrites diverted configuration file breaking unattended upgrades - upstream fix available
Public bug reported: An unattended security upgrade (package dovecot-core) failed, interrupting mailbox service. The cause was ucf replacing a custom configuration file which had been diverted (using dpkg-divert) by a custom configuration package. Excerpt from /var/log/apt/term.log: --- Setting up dovecot-core (1:2.2.33.2-1ubuntu4.6) ... Replacing config file /etc/dovecot/dovecot.conf.custom with new version ucfr: Attempt from package dovecot-core to take /etc/dovecot/dovecot.conf.custom away from package custom-mail-server ucfr: Aborting. dpkg: error processing package dovecot-core (--configure): installed dovecot-core package post-installation script subprocess returned error exit status 4 --- The underlying issue has been fixed upstream in ucf version 3.0040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=43 Affected versions: - Ubuntu 18.04.5 LTS - ucf 3.0038 - Ubuntu 20.04.1 LTS - ucf 3.0038+nmu1 ** Affects: ucf Importance: Unknown Status: Unknown ** Affects: dovecot (Ubuntu) Importance: Undecided Status: New ** Affects: ucf (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #43 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=43 ** Also affects: ucf via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=43 Importance: Unknown Status: Unknown ** Also affects: dovecot (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891515 Title: ucf overwrites diverted configuration file breaking unattended upgrades - upstream fix available To manage notifications about this bug go to: https://bugs.launchpad.net/ucf/+bug/1891515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816045] [NEW] secureboot-db: release upgrade from 16.04 to 18.04 modifies changelog.gz but resets mtime
Public bug reported: During a release-upgrade from Ubuntu 16.04 to 18.04, the file /usr/share/doc/secureboot-db/changelog.gz is modified, but retains its original mtime. This will interfere with incremental backups, which will fail to pick up the updated file. The file's first line has changed from: secureboot-db (1.4~ubuntu0.16.04.1) xenial; urgency=medium to: secureboot-db (1.4~ubuntu0.18.04.1) bionic; urgency=medium ... but the file time for both file versions is identical: 2018-10-19 20:20:34.0 +0200 changelog.gz ** Affects: secureboot-db (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816045 Title: secureboot-db: release upgrade from 16.04 to 18.04 modifies changelog.gz but resets mtime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/secureboot-db/+bug/1816045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816045] Re: secureboot-db: release upgrade from 16.04 to 18.04 modifies changelog.gz but resets mtime
Update affected package ** Package changed: man-db (Ubuntu) => secureboot-db (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816045 Title: secureboot-db: release upgrade from 16.04 to 18.04 modifies changelog.gz but resets mtime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/secureboot-db/+bug/1816045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1679627] Re: White/colored noise borders around windows after resume from standby (Nvidia on Xenial with kernel 4.8)
Seems to be fixed in package nvidia-375 version 375.66-0ubuntu0.16.04.1 ** Changed in: nvidia-graphics-drivers-375 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679627 Title: White/colored noise borders around windows after resume from standby (Nvidia on Xenial with kernel 4.8) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1679627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1679627] Re: White/colored noise borders around windows after resume from standby (Nvidia on Xenial with kernel 4.8)
Workaround To remedy the problem without adverse effects (such as logging out), run this command from a terminal window: $ setsid compiz --replace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679627 Title: White/colored noise borders around windows after resume from standby (Nvidia on Xenial with kernel 4.8) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1679627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1679627] Re: White/colored noise borders around windows after resume from standby (Nvidia on Xenial with kernel 4.8)
** Description changed: This happens intermittently on Xenial since upgrading to kernel 4.8: After resuming from standby (S3), white borders with colored dots appear around windows (see screenshot attached). Restarting lightdm (sudo systemctl restart lightdm.service) on a text console fixes the problem (but logs out the graphical desktop user). - NVIDIA GeForce GTX 950 - NVIDIA binary driver - version 375.39 - Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 + GPU: NVIDIA GeForce GTX 950 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-375 375.39-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 4 12:32:10 2017 InstallationDate: Installed on 2014-12-24 (831 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: nvidia-graphics-drivers-375 UpgradeStatus: Upgraded to xenial on 2016-04-22 (346 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679627 Title: White/colored noise borders around windows after resume from standby (Nvidia on Xenial with kernel 4.8) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1679627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1679627] [NEW] White/colored noise borders around windows after resume from standby (Nvidia on Xenial with kernel 4.8)
Public bug reported: This happens intermittently on Xenial since upgrading to kernel 4.8: After resuming from standby (S3), white borders with colored dots appear around windows (see screenshot attached). Restarting lightdm (sudo systemctl restart lightdm.service) on a text console fixes the problem (but logs out the graphical desktop user). NVIDIA GeForce GTX 950 NVIDIA binary driver - version 375.39 Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-375 375.39-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 4 12:32:10 2017 InstallationDate: Installed on 2014-12-24 (831 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: nvidia-graphics-drivers-375 UpgradeStatus: Upgraded to xenial on 2016-04-22 (346 days ago) ** Affects: nvidia-graphics-drivers-375 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "Screenshot-after-Resuming-from-Suspend-To-RAM.png" https://bugs.launchpad.net/bugs/1679627/+attachment/4854195/+files/Screenshot-after-Resuming-from-Suspend-To-RAM.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679627 Title: White/colored noise borders around windows after resume from standby (Nvidia on Xenial with kernel 4.8) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1679627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59
Tested Ubuntu 4.4.0-63.84-generic 4.4.44 on a desktop system with a workload which previously led to Chrome processes being OOM-killed. Situation with 4.4.0-62-generic: between 8 and 54 processes OOM-killed per 24-hour period Situation with 4.4.0-63-generic: no OOM-kills during 46 hours of testing Look solved. No negative side-effects encountered. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655842 Title: "Out of memory" errors after upgrade to 4.4.0-59 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59
** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655842 Title: "Out of memory" errors after upgrade to 4.4.0-59 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59
Testing... Enabled proposed (https://wiki.ubuntu.com/Testing/EnableProposed). Installed kernel packages: # apt-get install -s -t xenial-proposed 'linux-headers-4.4.0.63$' 'linux-headers-4.4.0.63-generic$' 'linux-image-4.4.0.63-generic$' 'linux-image-extra-4.4.0.63-generic$' Rebooted. # cat /proc/version_signature Ubuntu 4.4.0-63.84-generic 4.4.44 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655842 Title: "Out of memory" errors after upgrade to 4.4.0-59 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584052] Re: btrfs: file write crashes with false ENOSPC during snapshot creation since kernel 4.4 - fix available
Verified with the test script of #5. Kernel in -proposed solves the problem. Steps used: 1. Verified that release kernel 4.4.0-24-generic still had the problem. 2. Verified that kernel 4.4.0.25 from -proposed contains the resolution: # apt-get install -s -t xenial-proposed 'linux-headers-4.4.0.25$' 'linux-headers-4.4.0.25-generic$' 'linux-image-4.4.0.25-generic$' 'linux-image-extra-4.4.0.25-generic$' # reboot # cat /proc/version Linux version 4.4.0-25-generic (buildd@lgw01-05) (gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1) ) #44-Ubuntu SMP Fri Jun 10 18:19:48 UTC 2016 # ./test-btrfs-write-while-snapshotting.sh [problem did not show up on 10 consecutive runs] Problem solved, changing tag to 'verification-done-xenial'. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584052 Title: btrfs: file write crashes with false ENOSPC during snapshot creation since kernel 4.4 - fix available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584052] Re: btrfs: file write crashes with false ENOSPC during snapshot creation since kernel 4.4 - fix available
Hope the SRU will be accepted quickly. Should be the case, since this issue causes loss of user data as applications will have no reason to retry files writes under out of space conditions. Thanks for the quick and professional cooperation! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584052 Title: btrfs: file write crashes with false ENOSPC during snapshot creation since kernel 4.4 - fix available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584052] Re: btrfs: file write crashes with false ENOSPC during snapshot creation since kernel 4.4 - fix available
Another 24 error-free hours on the server with the test kernel running the MySQL/Icinga2 combination and creating btrfs snapshots every 5 minutes. I'd like to add that this server, which previously experienced frequent false ENOSPC conditions with the Xenial release kernel, used a fairly plain btrfs configuration at all times: - The '-o nodatacow' mount option was *not* used (in contrast to the test script). - Disabling copy-on-write (CoW) on a per-file basis (using chattr +C) was *not* used. # mount | grep /volumes/01 /dev/sda2 on /volumes/01 type btrfs (rw,noatime,nodiratime,ssd,space_cache,subvolid=5,subvol=/) # lsattr /var/lib/mysql/ibdata1 /var/lib/mysql/ibdata1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584052 Title: btrfs: file write crashes with false ENOSPC during snapshot creation since kernel 4.4 - fix available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584052] Re: btrfs: file write crashes with false ENOSPC during snapshot creation since kernel 4.4 - fix available
The Xenial test kernel with a pick of 4da2e26 resolves the bug, no negative side effects were encountered. With the Xenial release kernel, there were 18 MySQL server crashes in a 24 hour period due to false ENOSPC indications. With the test kernel, not a single crash occured in a 24 hour period. Additionally, I've checked with a script derived from https://patchwork.kernel.org/patch/7967161/ (see attachment), which creates a temporary btrfs test image in a plain file. The script provoked ENOSPC errors with the release kernel on most runs (sometimes it missed, presumably due to timing conditions). The script could not provoke a single ENOSPC condition with the test kernel. ** Attachment added: "Test script" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584052/+attachment/4668117/+files/test-btrfs-write-while-snapshotting.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584052 Title: btrfs: file write crashes with false ENOSPC during snapshot creation since kernel 4.4 - fix available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584052] Re: btrfs: file write crashes with false ENOSPC during snapshot creation since kernel 4.4 - fix available
I have now installed the kernel image on a server which previously experienced MySQL crashes every 1 to 2 hours. The server uses MySQL for an Icinga2 monitoring database (so it's frequently writing) and is configured to create btrfs snapshots every 5 minutes. # cat /proc/version Linux version 4.4.0-22-generic (root@gomeisa) (gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) ) #40~lp1584052 SMP Fri May 20 14:34:33 UTC 2016 I'll let it run for 24 hours and report back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584052 Title: btrfs: file write crashes with false ENOSPC during snapshot creation since kernel 4.4 - fix available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584052] Re: btrfs: file write crashes with false ENOSPC during snapshot creation since kernel 4.4 - fix available
There is no matching report in /var/crash. The bug is already diagnosed and fixed upstream, and may be reproduced with the information provided in https://patchwork.kernel.org/patch/7967161/ ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584052 Title: btrfs: file write crashes with false ENOSPC during snapshot creation since kernel 4.4 - fix available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584052] [NEW] btrfs: file write crashes with false ENOSPC during snapshot creation since kernel 4.4 - fix available
Public bug reported: Kernel 4.4 introduced a btrfs bug where a process writing a file while a snapshot creation is underway will receive a false ENOSPC error (No space left on device), even while there is plenty of free space on the file system. On systems where snapshots are created frequently, this leads to frequent database crashes (here with MySQL): 2016-05-19T21:00:01.862106Z 0 [Warning] InnoDB: Retry attempts for writing partial data failed. 2016-05-19T21:00:01.862133Z 0 [ERROR] InnoDB: Write to file ./ibdata1failed at offset 1048576, 16384 bytes should have been written, only 0 were written. Operating system error number 28. Check that your OS a nd file system support files of this size. Check also that the disk is not full or a disk quota exceeded. 2016-05-19T21:00:01.862143Z 0 [ERROR] InnoDB: Error number 28 means 'No space left on device' The problem is well known: http://www.spinics.net/lists/linux-btrfs/msg52672.html A patch is available: https://patchwork.kernel.org/patch/7967161/ The patch has been committed to the Linux Kernel source tree on Feb 18, 2016: https://github.com/torvalds/linux/commits/master/fs/btrfs/file.c Creating snapshots for undo and backup purposes without interrupting database operations is a central aspect of btrfs usage. This bug breaks server operations and should be fixed in the xenial kernel. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: btrfs kernel-fixed-upstream kernel-fs xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584052 Title: btrfs: file write crashes with false ENOSPC during snapshot creation since kernel 4.4 - fix available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1411633] [NEW] man-db's manipulation of index.db mtime timestamp interferes with incremental backups
Public bug reported: It appears that since version 2.7.0, man-db manipulates the mtime timestamp of /var/cache/man/de/index.db in a way that the content may change, while the timestamp is reset to its previous value (see attachment). See https://lists.ubuntu.com/archives/foundations- bugs/2014-September/209326.html This interferes with incremental backups which pick up files via their modification timestamps. Such backups will miss updated files which do not have their mtime timestamps changed accordingly. Automated comparisons between such backups and (btrfs snapshots of) their source data will fail. The integrity of such backups cannot be guaranteed. Release: Ubuntu 14.10 Package: man-db 2.7.0.2-2 ** Affects: man-db (Ubuntu) Importance: Undecided Status: New ** Attachment added: index.db changes without updating mtime https://bugs.launchpad.net/bugs/1411633/+attachment/4299930/+files/index-db-changes.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1411633 Title: man-db's manipulation of index.db mtime timestamp interferes with incremental backups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/man-db/+bug/1411633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
