Your message dated Thu, 4 Mar 2010 06:49:09 +1100
with message-id <20100303194909.gb24...@enc.com.au>
and subject line Re: Bug#572172: procps: Can't reproduce; please close
has caused the Debian Bug report #572172,
regarding Input goes haywire with procps update
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 ow...@bugs.debian.org
immediately.)
--
572172: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572172
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: procps
Version: 1:3.2.8-8
Severity: critical
Justification: breaks unrelated software
Upgrading to 3.2.8-8 from 3.2.8-7 causes X software to receive endless
amounts of input. For example, trying to run an email client is
impossible because the password dialog is overwhelmed with input before
I even press a key. Or, opening a text editor causes an endless stream
of whitespace to be entered into the buffer, without me pressing a key.
Downgrading to 3.2.8-7 solves the problem.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (990, 'unstable'), (350, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.33-drt100223-383be5d.100225.desktop.kms (SMP w/4 CPU cores;
PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
On Wed, Mar 03, 2010 at 10:19:37AM -0500, Dave Witbrodt wrote:
> Just now, I upgraded 'procps' again, and input is fine. Sorry for
> the noise. It looks very much like the X server had flaked out
> for some reason, and 'procps' was not to blame. The downgrade
> of procps most likely had nothing to do with fixing the problem,
> and restarting X was what really "fixed" it.
Ah ha. That makes a lot more sense. Ignore my previous email. I'll close
the bug. I'm not sure why mutt didn't thread this reply correctly.
> In the future I will try harder to make sure I am really
> experiencing a bug before filing a bug report, especially one
> that I am going to mark as "critical" in severity.
We've all done it before.
- Craig
--
Craig Small GnuPG:1C1B D893 1418 2AF4 45EE 95CB C76C E5AC 12CA DFA5
http://www.enc.com.au/ csmall at : enc.com.au
http://www.debian.org/ Debian GNU/Linux, software should be Free
--- End Message ---
