Hi.. This is just an observation. I already had 3 half finished drafts to three different threads when a fourth instance of reportbug failure just popped up, as well. Here they are in no particular order:
1) Re: reportbug and remapped "edit"; 2017.01.12 (consensus of two individuals momentarily pondering whether thread's subject matter caused reportbug failure) https://lists.debian.org/debian-user/2017/01/msg00454.html 2) Dependency problem with virtualbox-guest-x11; 2017.01.10 (reportbug crashing unrelated to thread's subject matter) https://lists.debian.org/debian-user/2017/01/msg00377.html 3) Re: Re: iio-sensor-proxy fills my syslog on debian testing; 2017.01.22 (reportbug crashing unrelated to thread's subject matter) https://lists.debian.org/debian-user/2017/01/msg00751.html 4) Errors were encountered while processing python3.5 etc; 2017.01.21 (OP suspects python3.5* upgrade killed reportbug, but maybe not k/t the three other instances above?) https://lists.debian.org/debian-user/2017/01/msg00723.html A critical malfunction of the otherwise ever increasingly user friendly reportbug is a huge, nasty disruption in the forward motion of successful Debian maintenance and releases. The catch-22 is that Debian users need... reportbug... to report an apparent bug with.... reportbug. :) Just lurking out loud... :) Cindy -- Cindy-Sue Causey Talking Rock, Pickens County, Georgia, USA * runs with duct tape *
