Your message dated Sun, 13 Mar 2016 14:28:51 +0000
with message-id <[email protected]>
and subject line Re: Uncaught exception: Unable to read from stdin: Success
has caused the Debian Bug report #466594,
regarding Uncaught exception: Unable to read from stdin: Success
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 [email protected]
immediately.)


-- 
466594: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466594
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aptitude
Version: 0.4.10-1+b2
Severity: minor

--- Please enter the report below this line. ---
I've been able to consistently crash aptitude by simply pressing B on a 
package, and then the down arrow.  I only tested installed packages.  This 
seems to happen because reportbug isn't installed.  Command line output as 
follows:

$ sudo aptitude
sh: reportbug: command not found
Reporting a bug in ktorrent:
Uncaught exception: Unable to read from stdin: Success
$ sudo aptitude
sh: reportbug: command not found
Reporting a bug in apt:
Uncaught exception: Unable to read from stdin: Success
$ sudo aptitude
sh: reportbug: command not found
Reporting a bug in sudo:
Uncaught exception: Unable to read from stdin: Success
$ sudo aptitude
sh: reportbug: command not found
Reporting a bug in linux-wlan-ng-firmware:
Uncaught exception: Unable to read from stdin: Success

--- System information. ---
Architecture: i386
Kernel:       Linux 2.6.24-1-686

Debian Release: lenny/sid
  500 unstable        www.debian-multimedia.org 
  500 unstable        ftp.debian.org 

--- Package information. ---
Depends                                (Version) | Installed
================================================-+-====================
libapt-pkg-libc6.7-6-4.6                         | 
libc6                                 (>= 2.7-1) | 2.7-8
libcwidget1                                      | 0.5.6.1-3
libgcc1                          (>= 1:4.1.1-21) | 1:4.3-20080202-1
libncursesw5                 (>= 5.6+20071006-3) | 5.6+20080203-1
libsigc++-2.0-0c2a                    (>= 2.0.2) | 2.0.17-2
libstdc++6                          (>= 4.2.1-4) | 4.3-20080202-1




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

2008-02-19 21:02 Lee Braiden:
Package: aptitude
Version: 0.4.10-1+b2
Severity: minor

--- Please enter the report below this line. ---
I've been able to consistently crash aptitude by simply pressing B on a
package, and then the down arrow.  I only tested installed packages.  This
seems to happen because reportbug isn't installed.  Command line output as
follows:

$ sudo aptitude
sh: reportbug: command not found
Reporting a bug in ktorrent:
Uncaught exception: Unable to read from stdin: Success
$ sudo aptitude
sh: reportbug: command not found
Reporting a bug in apt:
Uncaught exception: Unable to read from stdin: Success
$ sudo aptitude
sh: reportbug: command not found
Reporting a bug in sudo:
Uncaught exception: Unable to read from stdin: Success
$ sudo aptitude
sh: reportbug: command not found
Reporting a bug in linux-wlan-ng-firmware:
Uncaught exception: Unable to read from stdin: Success

The bug was tagged as unreproducible shortly after being submitted (and
is not reproducible now), reportbug has been removed now in any case,
the additional messages from other reporters are unrelated and more info
not provided for 3 years.

So closing this report now.


Cheers.
--
Manuel A. Fernandez Montecelo <[email protected]>

--- End Message ---
_______________________________________________
Aptitude-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

Reply via email to