[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#181951: marked as done (libc6: Libc6 doesn't draw "top" screen correctly)

Your message dated Sun, 27 Aug 2006 22:50:04 +0200
with message-id <20060827205002.GA9931@bode.aurel32.net>
and subject line Bug#181951: libc6: Libc6 doesn't draw "top" screen correctly
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)
--- Begin Message --- 
Package: libc6
Version: 2.3.1-11
Severity: normal

When using libc6 2.3.1-11, screen of command "top" is drawn incorrectly,
whereas when version 2.2.5-11.2 is used, top functions in the right way.
With 2.2.5-11.2 the first line of top's output is not shown if the number
of processes is so big that the list of them has to be truncated. 

So the uppermost part of top's screen looks like:
36 processes: 35 sleeping, 1 running, 0 zombie, 0 stopped
CPU states:   4.6% user,   5.2% system,   0.0% nice,  90.2% idle

Whereas the correctly draw screen looks like this:
 17:20:23 up  6:42,  4 users,  load average: 0.08, 0.20, 0.24
36 processes: 35 sleeping, 1 running, 0 zombie, 0 stopped
CPU states:   4.6% user,   5.2% system,   0.0% nice,  90.2% idle

I don't know what part os libc6 is causing the problem, but the problem
appeared when I upgraded from 2.2.5-11.2 to 2.3.1-11.

-- System Information
Debian Release: 3.0
Kernel Version: Linux debian 2.2.20 #1 Sat Apr 20 11:45:28 EST 2002 i586 unknown unknown GNU/Linux

Versions of the packages libc6 depends on:
ii  libdb1-compat  2.1.3-7        The Berkeley database routines [glibc 2.0/2.

--- End Message ---
--- Begin Message --- 
Version: 2.3.6-15

On Wed, Sep 29, 2004 at 10:31:25AM +0900, GOTO Masanori wrote:
> At Mon, 3 Mar 2003 23:56:56 +0200 (EET),
> Joonas Paalasmaa wrote:
> > On Tue, 25 Feb 2003, GOTO Masanori wrote:
> > > I test on VC (TERM=linux), but still I don't look any problem.
> > > Is this really glibc issue?
> > 
> > I upgraded kernel from 2.2.20 to 2.4.20 and the problem disappeared. So
> > this was some kind of a new-glibc-with-oldish-kernel problem.
> > Anyway, if you use 2.2.20 kernel with glibc 2.3.1, there still is the
> > problem. Issues with old kernels are propably not high priority bugs.
> 
> Hmm... I have no idea.  Glibc is always compiled with the newer kernel
> headers.  So it may be affected by kernel side changes.  Or ioctl()
> may not be implemented on 2.2.x, but I don't know the fact because I
> don't have 2.2.x machine.
> 

The support for 2.2.x kernels has been removed in etch, I am therefore
closing the bug.

-- 
  .''`.  Aurelien Jarno	            | GPG: 1024D/F1BCDB73
 : :' :  Debian developer           | Electrical Engineer
 `. `'   aurel32@debian.org         | aurelien@aurel32.net
   `-    people.debian.org/~aurel32 | www.aurel32.net

--- End Message ---
Reply to: