[Reportbug-maint] Bug#780747: reportbug: -o option is ignored on first run after fresh install

[Robert Munyer]

Control: found -1 6.6.6
Control: tags -1 - moreinfo unreproducible

I encountered this bug on Monday.  Yesterday I was able to reproduce
it while recording a transcript.  I used the ex command "%p" so that
all of the information that reportbug considered to be relevant would
be entered into the transcript.  I will attach the transcript below.

$ reportbug -o rb.txt
Welcome to reportbug! Since it looks like this is the first time you have used
reportbug, we are configuring its behavior. These settings will be saved to the
file "/home/user/.reportbugrc", which you will be free to edit further.
Please choose the default operating mode for reportbug.

1 noviceOffer simple prompts, bypassing technical questions.

2 standard  Offer more extensive prompts, including asking about things that a
moderately sophisticated user would be expected to know about
Debian.

3 advanced  Like standard, but assumes you know a bit more about Debian,
including "incoming".

4 expertBypass most handholding measures and preliminary triage routines.
This mode should not be used by people unfamiliar with Debian's
policies and operating procedures.

Select mode: [novice]
Will reportbug often have direct Internet access? (You should answer yes to
this question unless you know what you are doing and plan to check whether
duplicate reports have been filed via some other channel.) [Y|n|q|?]?
What real name should be used for sending bug reports?
[Debian Live user]>
Which of your email addresses should be used when sending bug reports? (Note
that this address will be visible in the bug tracking system, so you may want
to use a webmail address or another address with good spam filtering
capabilities.)
[user@debian.localdomain]>
Do you have a "mail transport agent" (MTA) like Exim, Postfix or SSMTP
configured on this computer to send mail to the Internet? [y|N|q|?]?
Please enter the name of your SMTP host. Usually it's called something like
"mail.example.org" or "smtp.example.org". If you need to use a different port
than default, use the : alternative format. Just press ENTER if you
don't have one or don't know, and so a Debian SMTP host will be used.
>
Please enter the name of your proxy server. It should only use this parameter
if you are behind a firewall. The PROXY argument should be formatted as a valid
HTTP URL, including (if necessary) a port number; for example,
http://192.168.1.1:3128/. Just press ENTER if you don't have one or don't know.
>
Default preferences file written. To reconfigure, re-run reportbug with the "--
configure" option.
Please enter the name of the package in which you have found a problem, or type
'other' to report a more general problem. If you don't know what package the
bug is in, please contact debian-u...@lists.debian.org for assistance.
> reportbug
Is "reportbug" actually the package you are having problems with [Y|n|q|?]?
*** Welcome to reportbug.  Use ? for help at prompts. ***
Note: bug reports are publicly archived (including the email address of the 
submitter).
Detected character set: UTF-8
Please change your locale if this is incorrect.

Using 'Debian Live user ' as your from address.
Getting status for reportbug...
Checking for newer versions at madison...
Will send report to Debian (per lsb_release).
Querying Debian BTS for reports on reportbug (source)...
175 bug reports found:

Bugs with severity important
1) #532150  reportbug: [regression] no longer supports custom mua commands
2) #564112  Checking status of source packages with many binaries can be sl
3) #709862  reportbug: GTK interface crashes on continue from package selec
4) #711404  reportbug's GTK interface crashes if spelling dictionaries for
5) #712415  reportbug doesn't notice installed foreign-architecture package
6) #717563  reportbug: web access thru proxy not available
7) #803675  reportbug: unable to report bug on kernel
8) #812220  reportbug: Bad Prompt Wording
9) #822522  reportbug: Crash when python-gtkspellcheck is installed
(1-9/175) Is the bug you found listed above [y|N|b|m|r|q|s|f|e|?]?
 Bugs with severity normal: 61 remain
   10) #265554  reportbug: on receiving SIGTERM, should also signal child proce
   11) #412914  reportbug: please add support for SSL protected SMTP communicat
   12) #431402  reportbug: Installed but not installed?
   13) #507600  bug script not ready for scripts
   14) #539157  direct SMTP send violates RFC1652 and sends unencoded 8-bit dat
   15) #539737  reportbug: RFC-1522-encoded headers for mutt
   16) #544485  special-case for severity of reports on linux-2.6
   17) #577278  reportbug: Attach options (-A) is not safe for UTF-8 content
   18) #579324  reportbug: doesn't cope with tr_TR locales
   19) #586680  Misnamed option --tls/smtptls with misleading docs and missing
   20) #590242  should always write realname/email on --configure
   21) #630086  reportbug does 

[Reportbug-maint] Bug#780747: reportbug: -o option is ignored on first run after fresh install

[Sandro Tosi]

control: tags -1 + moreinfo unreproducible

Hello,

On Wed, Mar 18, 2015 at 5:48 PM, Brian Julin bju...@clarku.edu wrote:
 The -o option was supposed to prevent the use of email by the
 reportbug tool and instead generate the file that I could email
 by hand.  The report was automatically submitted by SMTP nonetheless.
 For those that just use reportbug to generate headers and then
 edit the email afterwards, this could result in a lot of blank
 bug reports being filed with the BTS.

 In addition to that, despite the -o option, reportbug prompted for
 details of how to get email off the box (which I don't want to
 happen ever, actually, and it is only luck that it worked at all
 as I have not finished purging all traces of SMTP from this system.)

 This was the first time I had run reportbug on a fresh jessie
 install (from jessie netboot disks).  When I filed this bug,
 the -o option worked as intended and I was able to edit this
 text before pasting it into an email client.

The only thing that might change after a fresh install, is the absence
of the user configuration file ~/.reportbugrc , so I tried to remove
it and run reportbug -o but here it works correctly: I need the full
console output to understand what's going on.

Regards.
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Reportbug-maint mailing list
Reportbug-maint@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint

[Reportbug-maint] Bug#780747: reportbug: -o option is ignored on first run after fresh install

[Brian Julin]

Package: reportbug
Version: 6.6.3
Severity: normal

Dear Maintainer,

To file a previous bug report I invoked:

reportbug --email 'bju...@clarku.edu' -o cust/sensible.bug.txt

The -o option was supposed to prevent the use of email by the
reportbug tool and instead generate the file that I could email
by hand.  The report was automatically submitted by SMTP nonetheless.
For those that just use reportbug to generate headers and then
edit the email afterwards, this could result in a lot of blank
bug reports being filed with the BTS.

In addition to that, despite the -o option, reportbug prompted for
details of how to get email off the box (which I don't want to
happen ever, actually, and it is only luck that it worked at all
as I have not finished purging all traces of SMTP from this system.)

This was the first time I had run reportbug on a fresh jessie
install (from jessie netboot disks).  When I filed this bug,
the -o option worked as intended and I was able to edit this
text before pasting it into an email client.

-- Package-specific info:
** Environment settings:
INTERFACE=text

** /home/bri/.reportbugrc:
reportbug_version 6.6.3
mode standard
ui text
offline
email bju...@clarku.edu
no-cc
header X-Debbugs-CC: bju...@clarku.edu
smtphost reportbug.debian.org

-- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages reportbug depends on:
ii  apt   1.0.9.7
ii  python2.7.8-4
ii  python-reportbug  6.6.3
pn  python:anynone

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail  none
pn  debconf-utils   none
pn  debsums none
pn  dlocate none
ii  emacs24-bin-common  24.4+1-5
ii  file1:5.22+15-2
ii  gnupg   1.4.18-7
pn  postfix | exim4 | mail-transport-agent  none
ii  python-gtk2 2.24.0-4
pn  python-gtkspell none
pn  python-urwidnone
pn  python-vte  none
ii  xdg-utils   1.1.0~rc1+git20111210-7.4

Versions of packages python-reportbug depends on:
ii  apt   1.0.9.7
ii  python-debian 0.1.25
ii  python-debianbts  1.12
pn  python:anynone

python-reportbug suggests no packages.

-- no debconf information

___
Reportbug-maint mailing list
Reportbug-maint@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint