Bug#204682: marked as done (glibc: su - segfaults, loggin in as root also fails. sudo works)
Your message dated 26 Aug 2003 12:55:48 +0100
with message-id <1061898947.2724.50.camel@mill.nexus.co.uk>
and subject line Bug#204682: please close this bug-report
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 9 Aug 2003 10:07:25 +0000
>From jurriaan@rivierenland.xs4all.nl Sat Aug 09 05:07:23 2003
Return-path: <jurriaan@rivierenland.xs4all.nl>
Received: from smtpzilla2.xs4all.nl [194.109.127.138]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 19lQd8-0002zI-00; Sat, 09 Aug 2003 05:07:23 -0500
Received: from zeeotter.xs4all.nl (zeeotter.xs4all.nl [80.126.31.149])
by smtpzilla2.xs4all.nl (8.12.9/8.12.9) with ESMTP id h79A7MDF087847
for <submit@bugs.debian.org>; Sat, 9 Aug 2003 12:07:22 +0200 (CEST)
Received: (qmail 3762 invoked from network); 9 Aug 2003 10:06:51 -0000
Received: from unknown (HELO rivierenland.xs4all.nl) (unknown)
by unknown with SMTP; 9 Aug 2003 10:06:51 -0000
Received: (qmail 2331 invoked by uid 1000); 9 Aug 2003 10:06:47 -0000
Date: 9 Aug 2003 10:06:47 -0000
Message-ID: <[🔎] 20030809100647.2330.qmail@middle.of.nowhere>
From: thunder7@xs4all.nl
Subject: glibc: su - segfaults, loggin in as root also fails. sudo works
To: submit@bugs.debian.org
X-Mailer: bug 3.3.10.2
Delivered-To: submit@bugs.debian.org
X-Spam-Status: No, hits=-4.5 required=4.0
tests=BAYES_20,HAS_PACKAGE,NO_REAL_NAME
version=2.53-bugs.debian.org_2003_07_20
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_07_20 (1.174.2.15-2003-03-30-exp)
Package: glibc
Version: N/A
Severity: grave
After updating to the latest glibc this morning as per apt-get upgrade,
I now get a segfault on running su -.
Logging in as root directly also fails, it asks for name/password then
repeats that.
It worked until this morning, all I updated was python, debhelper, glibc,
libart-lgpl, libxml2, python-apt and ucf.
On trying to strace su, it always gives 'authentication failure'. Without
strace, it gives a segmentation fault. This may be an interaction between
glibc and the 2.6 kernel, but I've observed it on 2.6.0-test2 and 2.6.0-test3
both.
Jurriaan
-- System Information
Debian Release: testing/unstable
Kernel Version: Linux middle 2.6.0-test2 #1 Sun Jul 27 21:23:04 CEST 2003 i686 GNU/Linux
---------------------------------------
Received: (at 204682-done) by bugs.debian.org; 26 Aug 2003 11:55:54 +0000
>From pb@nexus.co.uk Tue Aug 26 06:55:50 2003
Return-path: <pb@nexus.co.uk>
Received: from dsl-62-3-66-203.zen.co.uk (crown.nexus.co.uk) [62.3.66.203]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 19rcQP-0004nr-00; Tue, 26 Aug 2003 06:55:49 -0500
Received: from dsl-62-3-66-201.zen.co.uk ([62.3.66.201] helo=mill.nexus.co.uk)
by crown.nexus.co.uk with esmtp (TLS-1.0:RSA_ARCFOUR_MD5:16)
(Exim 4.20)
id 19rcQO-0005hc-Oa
for 204682-done@bugs.debian.org; Tue, 26 Aug 2003 12:55:48 +0100
Subject: Re: Bug#204682: please close this bug-report
From: Philip Blundell <pb@nexus.co.uk>
To: 204682-done@bugs.debian.org
Content-Type: text/plain
Message-Id: <1061898947.2724.50.camel@mill.nexus.co.uk>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.3
Date: 26 Aug 2003 12:55:48 +0100
Content-Transfer-Encoding: 7bit
Delivered-To: 204682-done@bugs.debian.org
X-Spam-Status: No, hits=-5.2 required=4.0
tests=BAYES_20,QUOTED_EMAIL_TEXT,USER_AGENT_XIMIAN
version=2.53-bugs.debian.org_2003_8_17
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_8_17 (1.174.2.15-2003-03-30-exp)
> As can be seen in the bugs on bash-static, bash-static may fail
> without warning whenever a new glibc version is uploaded. To me,
> that doesn't sound like 'static', but hey - at least I can login
> as root again!
>
> Please close this bug, glibc is not at fault.
Thanks for the information. I'm closing this bug as you suggest.
p.
Reply to: