Note that this is https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=831390.
We have been running with a custom build of the package, that adds
__thread to the relevant variables as suggested in that bug, and haven't
seen any crashes in this module since.
> On 13 Dec 2016, at 16:30, ChristianEhrh
See also the thread at https://lists.gnu.org/archive/html/qemu-
devel/2016-11/msg02634.html which appears to be about the same issue,
and references two commits that might fix this if cherry-picked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
This is with:
$ dpkg-query -W qemu-system-x86
qemu-system-x86 1:2.5+dfsg-5ubuntu10.6
$ qemu-system-x86_64 --version
QEMU emulator version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.6), Copyright (c)
2003-2008 Fabrice Bellard
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
See updates at the end of #1612089. Sample error message:
Dec 05 14:41:07 zbk130713 libvirtd[29690]: internal error: early end of file
from monitor, possible problem:
2016-12-05T14:41:07.903932Z qemu-system-x86_64: VQ 2 size 0x80 < last_avail_idx
0x9 - used_idx 0xa
2016-12-
Looks like s10 never did file a separate bug for the regression, but we
got hit by the same issue, so I filed
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1647389.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Public bug reported:
lsblk from util-linux in xenial is affected by this bug:
https://github.com/karelzak/util-linux/issues/321
This means that lsblk may return the same identifier for different
devices, because it always uses the short WWN, while some devices are
only identified uniquely by the
I'm pretty sure this bug is actually in libnss-extrausers (see top of
stack trace).
libvirtd is trying a getgrouplist, which is calling out to the various
NSS modules through glibc.
In libnss-extrausers, this construct in group.c:
static FILE *groupsfile = NULL;
[...]
enum nss_status _nss_extr
Is it intentional that this is set Invalid and therefore hidden in the
bug overview? That's pretty much why I accidentally duped it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565585
Title:
Old
Public bug reported:
The script has a hardcoded assumption that i18n files are bzip2 packed:
2476 next if $filename !~ /bz2$/;
But archive.ubuntu.com only ships .gz and .xz these days:
http://archive.ubuntu.com/ubuntu/dists/xenial/main/i18n/
Should be a trivial fix. This report should also
It isn't though, looks like my optimism regarding the upstream
maintainer was misplaced.
The "fix" in Debian's -5 upload is to add "| true" to the grep call
which is of course nonsense, he must have meant "|| true".
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
Fixed in Debian by -5: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=818116
Should be fine if you just refresh from sid.
** Bug watch added: Debian Bug tracker #818116
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818116
--
You received this bug notification because you are a member
We've been able to confirm an out of bounds write in fuse_direct_io with
the slub_debug boot option on linux-lts-wily.
** Attachment added: "Screen Shot 2016-01-26 at 10.00.03.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1505948/+attachment/4557543/+files/Screen%20Shot%202016-01-2
We've been able to confirm an out of bounds write in fuse_direct_io with
the slub_debug boot option on linux-lts-wily.
** Attachment added: "Screen Shot 2016-01-26 at 10.00.03.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1505948/+attachment/4557544/+files/Screen%20Shot%202016-01-2
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1398465 also
appears to be the same issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505948
Title:
Memory allocation failure crashes kernel
** Summary changed:
- Please backport 3.2+ to trusty
+ Please backport xfsprogs 3.2+ to trusty
** Package changed: xfsprogs (Ubuntu) => trusty-backports
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Public bug reported:
bcache is a production-relevant feature. An upload to trusty-backports
would be appreciated.
** Affects: bcache-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
XFS has new features starting with kernel 3.14. trusty includes an
official backport of the utopic kernel (3.16), but the new robustness
features can't be used unless the file system is created with a newer
version of mkfs.xfs. Please consider backporting utopic xfsprogs to
tr
17 matches
Mail list logo
