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

Bug#462916: marked as done (apt-get changes dumb terminal parity)

Your message dated Thu, 13 Aug 2015 18:03:24 +0200
with message-id <20150813160324.GA18858@crossbow>
and subject line Re: Bug#462916: Acknowledgement (apt-get changes dumb terminal parity)
has caused the Debian Bug report #462916,
regarding apt-get changes dumb terminal parity
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
462916: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=462916
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: apt
Version: 0.7.9

When I use apt-get at a dumb terminal which is set for odd parity
everything seems OK at first.  But later on after it's fetched
(downloaded) all the packages and begins with "Reading database" I see
error characters that indicate that apt has messed with the terminal
settings for the serial port (using stty or the like) in the computer
and has disabled odd parity.  The "Reading Database" and everything
after this (such as setting up packages) is almost unreadable.  So
characters with no parity are being sent to the terminal and only
about half of them happen to have odd parity, so only those get
displayed since the dumb terminal considers any characters with even
parity to be erroneous and only displays error symbols for them.

Then when apt-get is finished, everything is OK since it must reset
the terminal interface back to odd parity (It likely saved the
original settings and then restores them).  The fix is to just not
to change the parity setting of the interface.  It could be some program
that apt-get calls that is the culprit.

			David Lawyer

--- End Message ---
--- Begin Message --- 
Hi,

On Wed, Jan 30, 2008 at 08:25:19PM -0800, Daniel Burrows wrote:
> On Tue, Jan 29, 2008 at 07:37:31AM -0800, Daniel Burrows <dburrows@debian.org> was heard to say:
> > On Mon, Jan 28, 2008 at 11:05:26AM -0800, David Lawyer <dave@lafn.org> was heard to say:
> > > I tried strace but since strace controls the terminal interface,
> > > parity doesn't get disabled.
> > 
> >   IIRC, running "strace -o <filename> ..." should send output to the
> > given file and leave your terminal alone.
> 
>   David's SMTP server is blocking messages for me, so he hasn't actually
> received this suggestion.

Unreproducible 7 years old bugs usually aren't reproducible now… and
nobody else complained about any such behaviour so I hope if there ever
was a bug with apt (The "Read database" message is from dpkg…) it is
fixed in the meantime even if I can't verify it.

I am therefore closing this bugreport as not actionable. If you can by
some miracle still reproduce this issue, feel free to reopen of course!

Best regards

David Kalnischkies

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: