This bug was fixed in the package glibc - 2.24-7ubuntu2
---
glibc (2.24-7ubuntu2) zesty; urgency=medium
* Disable lock-elision on all targets to avoid regressions (LP:
#1642390)
glibc (2.24-7ubuntu1) zesty; urgency=medium
* Merge with 2.24 from Debian sid, with upstream and
autopkgtest results looked good, released to xenial and yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642390
Title:
Disable lock-elision in glibc pending upstream changes
To manage
This bug was fixed in the package glibc - 2.24-3ubuntu2
---
glibc (2.24-3ubuntu2) yakkety; urgency=medium
* Disable lock-elision on all targets to avoid regressions (LP:
#1642390)
-- Adam Conrad Wed, 16 Nov 2016 13:53:50 -0700
** Changed in: glibc (Ubuntu
This bug was fixed in the package glibc - 2.23-0ubuntu5
---
glibc (2.23-0ubuntu5) xenial; urgency=medium
* Disable lock-elision on all targets to avoid regressions (LP:
#1642390)
-- Adam Conrad Wed, 16 Nov 2016 13:53:50 -0700
** Changed in: glibc (Ubuntu
I want to add a +1 problem solved. No more segfault for me either on an
intel NUC6i7KYK with a Core i7-6770.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642390
Title:
Disable lock-elision in
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642390
Title:
Disable lock-elision in glibc pending upstream changes
To manage
Thanks for this update to glibc. It resolved segmentation fault problems
when running Oracle on a T460p Thinkpad. Even loading the newest
microcode could not resolve the segmentation faults but this version of
glibc makes everything run smoothly. No sideeffects detected.
Thanks!
--
You received
Howdy, I'm the originator of:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1641241
(which points to this bug via
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1640518)
I tested the new ("ubuntu5") libc6 packages from xenial-proposed. They
prevent the crash we were seeing with
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: glibc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642390
Title:
Hello Adam, or anyone else affected,
Accepted glibc into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/glibc/2.23-0ubuntu5 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: glibc (Ubuntu)
Assignee: (unassigned) => Adam Conrad (adconrad)
** Changed in: glibc (Ubuntu Xenial)
Assignee: (unassigned) => Adam Conrad (adconrad)
** Changed in: glibc (Ubuntu Yakkety)
Assignee: (unassigned) => Adam Conrad (adconrad)
--
You received this bug
11 matches
Mail list logo