Path: csiph.com!goblin2!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From: =?ISO-8859-1?Q?=C1ngel?= <angel@16bits.net>
Newsgroups: gnu.bash.bug
Subject: Re: Is this a bug?
Date: Fri, 21 Aug 2020 00:07:09 +0200
Lines: 41
Approved: bug-bash@gnu.org
Message-ID: <mailman.578.1597961236.2469.bug-bash@gnu.org>
References: <1361377909.989786.1596736417780.ref@mail.yahoo.com> <1361377909.989786.1596736417780@mail.yahoo.com> <0d88a4ca-9eca-62b4-91bd-d2e4083190f3@case.edu> <1312274972.4025864.1597785278610@mail.yahoo.com> <6575997b-0217-046a-8ef1-0437571475ca@case.edu> <1699062943.4171052.1597809756404@mail.yahoo.com> <16e6944b-9707-a80c-3602-e76edcca64ec@case.edu> <630008166.4463802.1597857290469@mail.yahoo.com> <054462f1-e801-bdcc-8f0d-b880ef8eab79@case.edu> <300430358.4632420.1597870535904@mail.yahoo.com> <1597961229.3809.8.camel@16bits.net>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-15"
Content-Transfer-Encoding: quoted-printable
X-Trace: usenet.stanford.edu 1597961237 21666 209.51.188.17 (20 Aug 2020 22:07:17 GMT)
X-Complaints-To: action@cs.stanford.edu
To: bug-bash@gnu.org
Envelope-to: bug-bash@gnu.org
In-Reply-To: <300430358.4632420.1597870535904@mail.yahoo.com>
Received-SPF: pass client-ip=199.195.249.9; envelope-from=angel@16bits.net; helo=mailer.hiddenmail.net
X-detected-operating-system: by eggs.gnu.org: First seen = 2020/08/20 18:07:11
X-ACL-Warn: Detected OS   = Linux 3.11 and newer [fuzzy]
X-Spam_score_int: -18
X-Spam_score: -1.9
X-Spam_bar: -
X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no
X-Spam_action: no action
X-BeenThere: bug-bash@gnu.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/bug-bash>
List-Post: <mailto:bug-bash@gnu.org>
List-Help: <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
X-Mailman-Original-Message-ID: <1597961229.3809.8.camel@16bits.net>
X-Mailman-Original-References: <1361377909.989786.1596736417780.ref@mail.yahoo.com> <1361377909.989786.1596736417780@mail.yahoo.com> <0d88a4ca-9eca-62b4-91bd-d2e4083190f3@case.edu> <1312274972.4025864.1597785278610@mail.yahoo.com> <6575997b-0217-046a-8ef1-0437571475ca@case.edu> <1699062943.4171052.1597809756404@mail.yahoo.com> <16e6944b-9707-a80c-3602-e76edcca64ec@case.edu> <630008166.4463802.1597857290469@mail.yahoo.com> <054462f1-e801-bdcc-8f0d-b880ef8eab79@case.edu> <300430358.4632420.1597870535904@mail.yahoo.com>
Xref: csiph.com gnu.bash.bug:16789

On 2020-08-19 at 20:55 +0000, George R Goffe wrote:
> Chet,
>=20
> I tried several times to create the problem. I think I succeeded. I did i=
nstall the "debuginfo" files I could find but it looks like libnss_sss.so's=
 debuginfo isn't built properly? It's supplied by sssd-client. I tried inst=
alling sssd-client-debuginfo but it is already installed. I don't remember =
doing that. Sigh... Somehow libnss_sss.so is referenced by bash? That's wha=
t gdb thinks.
>=20
> Anyway, I tried causing the problem. ls -al zzz<tab-key> and then ctrl-c =
with seemingly no response. I'll have to try running gdb in another konsole=
 so I can watch what happens when I <ctrl-c>... I'll do that now. Stand by.=
=20
>=20
> ....
>=20
> I'm still not certain that I'm doing it right. When I entered ls -al zzz<=
tab key> bash froze. I went to the gdb konsole and typed in where but nothi=
ng happened. Tried several times. Tried ctrl-c on the gbb console. Got gdb'=
s attention. Entered where. Here's the results:
>=20
> Please let me know if this helps or if you need me to do something differ=
ent.
>=20
> Regards,
>=20
> George...

Since you mention sssd, and it is apparently loaded by bash, are the
users and groups list from a remote server (such as LDAP)?

That could cause bash (or whatever program which tries to determine the
name of a user/group) to freeze if its cache expired and it needs to
refetch those  from a remote server (e.g. it may be downloading the list
of all the users in the company).


Best regards