A crash must be fixed, anyway.
I've experienced it myself. It can be easily replicated using a remote shell to
launch gnome-session in an Xvfb display:
Xvfb -ac :100 2> Xvfb.log &
DISPLAY=:100
export DISPLAY
gnome-session --session=ubuntu
After that, gdm crashed. I had gdm debug
Thank you. libnss-ldap-264-2.2ubuntu4.14.04.2 fixed the issue.
On Thu, Nov 10, 2016 at 7:12 PM, Brian Murray wrote:
> The verification of the Stable Release Update for libnss-ldap has
> completed successfully and the package has now been released to
> -updates. Subsequently, the Ubuntu Stable Re
@jon.grimm
I can reproduce after I set up LDAP server and client to use StartTLS.
In plain setup, no write to non-connected socket is issued in the
atfork handlers of child process, so no SIGPIPE is raised.
On Wed, Aug 26, 2015 at 7:45 PM, Jon Grimm wrote:
> @brianquigley, Thanks for responding.
The author posted the source code of nss_ldap 266 (including the fix for
this bug) to https://github.com/PADL/nss_ldap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1397250
Title:
SIGPIPE not caugh
Public bug reported:
Ubuntu version: Ubuntu 14.04.1 LTS
Package version: libnss-ldap_264-2.2ubuntu4
If a process using libnss-ldap calls fork() and SIGPIPE was blocked, the
atfork() handler in the child process failed to catch the SIGPIPE as it was
supposed to do, that is in the call to do_clo
