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 detec
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 u
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
fr
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
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.launchpa
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/167962
** 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
cons
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 pro
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 testin
** 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
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 /pr
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.
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
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 bt
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.
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.
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 notificatio
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, t
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-Se
19 matches
Mail list logo
