Launchpad has imported 7 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1252570.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2015-08-11T17:54:24+00:00 Nalin wrote: Created attachment 1061638 gdb "where full" results, plus a couple of variables Description of problem: With a working hesiod configuration, and hesiod enabled for group resolution, multiple applications are crashing while initializing a supplemental groups list. Version-Release number of selected component (if applicable): glibc-2.21.90-21.fc23.x86_64 coreutils-8.24-2.fc23.x86_64 used to reproduce the bug How reproducible: Always Steps to Reproduce: 1. cat > /etc/hesiod.conf << EOF lhs=.hs rhs=.devel.redhat.com EOF 2. Add "hesiod" as a source for "group" information in /etc/nsswitch.conf. Mine reads "files hesiod". 3. Run "groups nalin" or similar. Actual results: "groups" segfaults. I'll attach the gdb backtrace. Expected results: The expected groups list. Additional info: Reply at: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1571456/comments/0 ------------------------------------------------------------------------ On 2016-02-05T14:13:21+00:00 Florian wrote: Caused by upstream commit 2212c1420c92a33b0e0bd9a34938c9814a56c0f7. Bug reported upstream. There are various ways to fix this, but which approach is best is unclear. Reply at: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1571456/comments/1 ------------------------------------------------------------------------ On 2016-02-15T11:24:29+00:00 Florian wrote: Reproducer without changing /etc: cat > /etc/hesiod.conf << EOF lhs=.hs rhs=.devel.redhat.com EOF HESIOD_CONFIG=hesiod.conf getent -s hesiod group 0 0 I'm reverting the upstream commit which introduced this bug. Reply at: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1571456/comments/2 ------------------------------------------------------------------------ On 2016-02-16T16:08:11+00:00 Fedora wrote: glibc-2.22-9.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-0f9e9a34ce Reply at: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1571456/comments/3 ------------------------------------------------------------------------ On 2016-02-17T06:26:43+00:00 Fedora wrote: glibc-2.22-9.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-0f9e9a34ce Reply at: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1571456/comments/4 ------------------------------------------------------------------------ On 2016-02-17T14:20:20+00:00 Fedora wrote: glibc-2.22-9.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report. Reply at: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1571456/comments/5 ------------------------------------------------------------------------ On 2016-02-17T18:48:28+00:00 Florian wrote: Due to this change, a glibc update to the fixed versions *without* a reboot (or process restart) may cause name resolution failures. Reply at: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1571456/comments/6 ** Changed in: glibc (Fedora) Status: Unknown => Fix Released ** Changed in: glibc (Fedora) Importance: Unknown => Undecided -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571456 Title: id crashed with SIGSEGV in sock_eq() To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1571456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
