Verified that the update package produces the expected results on
Trusty:
root@crest4:~# dpkg -l util-linux
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name
Public bug reported:
[Impact]
Running 'lscpu' on a system with discontinuous NUMA nodes (such as some IBM
Power 8 hardware) will only display the continuous NUMA nodes. Users may be
confused due to incorrect information.
[Test Case]
On a system with discontinuous NUMA nodes, just run the
This was fixed upstream (http://git.kernel.org/cgit/utils/util-linux
/util-linux.git/) by commit e9074a167cb485fea91be2cb20f68e137b6d3246.
There have been many changes, so I don't think updating to the new
version is appropriate for a SRU. To backport this, I had to also pull
in code from
Hi Adam- Is this SRU appropriate to target for the 14.04.2 milestone?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387594
Title:
init: symbol lookup error: /lib/powerpc64le-linux-
Hi Adam- Is this SRU appropriate to target for the 14.04.2 milestone?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libnss-ldap in Ubuntu.
https://bugs.launchpad.net/bugs/1387594
Title:
init: symbol lookup error:
I ran tests on an IBM 8247-22L using both Utopic and Trusty for ppc64el.
Details of the test follow, but the new packages in
[utopic,trusty]-proposed fix the segfault issue.
For Utopic
root@crest2:~# lsb_release -rc
Release:14.10
Codename: utopic
# Current working version
I ran tests on an IBM 8247-22L using both Utopic and Trusty for ppc64el.
Details of the test follow, but the new packages in
[utopic,trusty]-proposed fix the segfault issue.
For Utopic
root@crest2:~# lsb_release -rc
Release:14.10
Codename: utopic
# Current working version
Anything I can do to help this SRU along? This is affecting our Trusty
and Utopic boxes. Right now, I've manually pulled in a Vivid package so
I actually have working systems. It would be nice to get this into the
*-updates repos.
--
You received this bug notification because you are a member
Anything I can do to help this SRU along? This is affecting our Trusty
and Utopic boxes. Right now, I've manually pulled in a Vivid package so
I actually have working systems. It would be nice to get this into the
*-updates repos.
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1387594 ***
https://bugs.launchpad.net/bugs/1387594
** This bug has been marked a duplicate of bug 1387594
init: symbol lookup error: /lib/powerpc64le-linux-gnu/libnss_ldap.so.2:
undefined symbol: __libc_lock_lock
--
You received this bug notification
coreutils (6.10-3) and the ubuntu patches (6.10-3ubuntu2), seem to make
the issue go away.
Although I would still recommend Ubuntu sync libnss-ldap with upstream,
this is not a critical bug anymore.
--
wrong id behaviour on a system with LDAP
https://bugs.launchpad.net/bugs/191884
You received
As a workaround for other experiencing the problem, here are the steps to
upgrade libnss-ldap on your own:
sudo apt-get install build-essential libldap2-dev
wget http://www.padl.com/download/nss_ldap.tgz
tar -zxvf nss_ldap.tgz
cd nss_ldap-260
./configure
./make
sudo make install
--
wrong id
I cannot get ldap authentication to work in Hardy with this bug (using
just Ubuntu packages). This needs to be fixed before Hardy's release- I
would consider this a critical bug.
Would the maintainer look into upgrading libnss-ldap ?
--
wrong id behaviour on a system with LDAP
13 matches
Mail list logo
