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 novice Offer 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 expert Bypass 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 <host>:<port> 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 <user@debian.localdomain>' 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 not sign attachments 22) #639527 Use PTS SOAP API 23) #639698 reportbug: STARTTLS failure - continue without TLS 24) #640191 Complaint about non RFC 2822 compliancy 25) #642414 reportbug GUI hangs 26) #646573 UTF-8 characters in subject are passed to MUA encoded 27) #648185 reportbug: ftp.debian.org RM bugs should get X-Debbugs-CC: main 28) #649777 reportbug: high cpu load when displaying progress bar (like sen 29) #651590 reportbug: Reportbug doesn't have a GTK3 interface yet 30) #653738 Configuration routine not run if a package specified on first r 31) #657066 reportbug: Cannot provide extra information for ITP bug reports 32) #659214 reportbug: does not report build-dependencies of source package (10-32/175) Is the bug you found listed above [y|N|b|m|r|q|s|f|e|?]? Bugs with severity normal: 38 remain 33) #664213 Please preserve the order of attachements 34) #669038 GTK+ doesn't handle bug scripts asking questions 35) #687214 python-reportbug: [GTK2 UI] no option to send a bug discussion 36) #690537 reportbug: Package list does not specify arch 37) #694161 reportbug: fails to add patch tag to existing bug (plus one cos 38) #695219 reportbug incorrectly says "Report has not been sent yet" after 39) #695887 reportbug locks terminal, refuses echo, requires "reset" after 40) #698331 reportbug: Pressing enter after starting reportbug causes a gtk 41) #702107 reportbug failed (my error) saved report in /tmp; no obvious wa 42) #703678 reportbug is not derivative-friendly, at least not when using a 43) #704824 reportbug: submitting a followup to a "templated" bug should no 44) #705172 reportbug doesn't run first-time configuration when started wit 45) #707296 Please detect keywords that indicate a likely attachment, and w 46) #708066 reportbug: doesn't always preserve the bug title 47) #712066 reportbug: Add documentation on resending saved reportbug files 48) #712070 reportbug: Add documentation on resending saved reportbug files 49) #720083 reportbug: Gtk interface, when gathering system information, ha 50) #721212 Thinks that packages don't exist 51) #725105 reportbug: Add option to resend saved reportbug file 52) #729415 reportbug: yesno/getkey helper functions assume console 53) #730236 reportbug: After initial config, reportbug should remember its 54) #740124 Reportbug: Unable to send report via SMTP Yahoo server 55) #746021 reportbug: severity == 'does-not-build' selects severity 'serio (33-55/175) Is the bug you found listed above [y|N|b|m|r|q|s|f|e|?]? Bugs with severity normal: 15 remain 56) #748866 reportbug: sometimes assumes src: without being told to 57) #749884 reportbug: doesn't grok :any qualifiers in Depends 58) #751079 reportbug: newer version alert even when only for a different a 59) #763153 reportbug: wrongly reports python:any as uninstalled 60) #763167 reportbug: Reports held package as uninstalled 61) #767182 reportbug: arch-qualification of packages in second pkgs-select 62) #770555 reportbug: Empty dialog while having mail configuration issues 63) #771545 reportbug-gtk hangs while gathering more information 64) #773673 reportbug: I cannot change window size when nano is running ins 65) #777279 reportbug: The graphical UI of Reportbug doesn't check for dupl 66) #777393 reportbug: package status determined from dpkg's desired state 67) #780747 reportbug: -o option is ignored on first run after fresh instal 68) #784696 reportbug ignores -d - sends to Debian anyway 69) #785228 reportbug: Reportbug crashes after selecting gtk in terminal 70) #795517 reportbug: gtk2 frontend is usless with -N 71) #806681 reportbug: Improve feedback "unable to connect to debian.org" a 72) #806682 reportbug should save report on SIGINT 73) #808867 reportbug: Bug against snappy (src:snappy-player) reported agai 74) #809758 reportbug: Adding an attachment with it adds an extra line at t 75) #810944 querybts: Mutt looks garbled after SIGWINCH 76) #811168 Unable to file RFP bug 77) #812112 Reportbug asks to install "python-gtkspellcheck", but after ins 78) #813113 reportbug: incorrect description for www.debian.org (56-78/175) Is the bug you found listed above [y|N|b|m|r|q|s|f|e|?]? Bugs with severity normal 79) #813660 reportbug: very unobvious that a report was NOT sent 80) #813771 reportbug: It can't unselect item in 'Do any of the following a 81) #814454 reportbug: Crash when trying to configure non-ASCII characters 82) #816903 reportbug: package dependencies listed as <none> but they are i 83) #819543 reportbug: doesn't run bug scripts for report-with: packages 84) #819570 reportbug: replyto option in config file ignored 85) #822533 reportbug crash when with a crippled internet connection 86) #822643 reportbug: Should automatically fill Re: $(Previous subject), a 87) #824953 Bug lists show 'pending' for all entries 88) #826534 reportbug xrdp gives: IndexError: list index out of range 89) #828171 /usr/bin/querybts: IndexError race condition soon after filing 90) #831848 Reportbug support for cloud.debian.org pseudo package 91) #836245 GUI of reportbug requires an additional package which isn't shi 92) #838162 reportbug: Fails to retrieve bug information 93) #838598 package: reportbug [RESOLVED] (79-93/175) Is the bug you found listed above [y|N|b|m|r|q|s|f|e|?]? Bugs with severity minor 94) #128092 reportbug: should redisplay on WINCH signal 95) #407531 reportbug: should detect terminal resize when listing bugs 96) #460899 reportbug: Doesn't check for terminal resize 97) #500276 reportbug: Needlessly escapes brackets to \( in realname 98) #502860 use python-apt instead of dpkg for pkgs info 99) #665348 reportbug: RESOLVED information can be hidden due to truncation 100) #671398 reportbug: Does not complain when file for attachment is not fo 101) #678743 reportbug doesn't notice a change in the number of columns afte 102) #685825 reportbug: too noisy even when asking it to be --quiet 103) #685828 reportbug: package version can't be left blank 104) #769584 =?iso-8859-1?q?Do_not_change_the_format_of_the_subject_line_whe 105) #773708 reportbug: scrollbar operation is crude 106) #811193 /usr/share/doc/reportbug/README.Users.gz: Fixing a few trivial 107) #813299 reportbug: newer version alert for security updates 108) #816133 reportbug: Gtk-Message on reportbug start 109) #816375 reportbug: exits badly with --draft= option and non existing di 110) #822691 reportbug: With Mutt 1.6, the -E option should be used so that 111) #825408 reportbug: detect and properly fail if the SMTP server rejected 112) #827002 reportbug: outdated documentation in doc/README.source 113) #827088 reportbug: PATH should be split on ':' instead of '/' 114) #836253 reportbug: Do not hardcode icon in desktop file (94-114/175) Is the bug you found listed above [y|N|b|m|r|q|s|f|e|?]? Bugs with severity wishlist: 38 remain 115) #157283 reportbug: Allow mailing cont...@bugs.debian.org - or at least 116) #171870 reportbug: check packages.d.o for current maintainer? 117) #271084 reportbug and kmail could play more nicely together 118) #295386 reportbug should not ask novice users to pick RC severities by 119) #302234 reportbug: please check binaries for locally installed librarie 120) #317960 reportbug: filter wnpp bugs according to type of submission 121) #319020 reportbug: Could advertise the PTS for packages which are not v 122) #328531 reportbug: provide option to continue with saved report 123) #329298 reportbug: querybts: offer to subscribe users 124) #347425 reportbug: would like --resume option for picking up from an in 125) #365141 reportbug: please add an option to dump to evolution's Drafts f 126) #384287 reportbug: please internationalize the software 127) #407557 reportbug: possibilty to send bugs with kmail 128) #420903 Option in ~/.reportbugrc to X-Debbugs-CC auto-determined email 129) #428257 reportbug: "--query-bts" should override "offline" 130) #431228 reportbug: Ability to filter bug list for submitter 131) #433462 reportbug: Please add "free disk space" as part of the informat 132) #447481 reportbug: When sending feedback to a closed bug then optionall 133) #448493 reportbug: Use 'mailto:' URL from Bugs field as submit address 134) #455653 reportbug: When prompting for version, show available versions 135) #461488 reportbug: Please be more explicit with X-Debbugs-CC 136) #532468 Could have an option to use an external editor in gtk. 137) #544812 reportbug: Show bugs which affect the target package in bug lis (115-137/175) Is the bug you found listed above [y|N|b|m|r|q|s|f|e|?]? Bugs with severity wishlist: 15 remain 138) #548415 reportbug: Package upgrade information in bug reports 139) #549201 force (if possible) English spellcheck in GTK+ GUI 140) #574040 python-reportbug: add debug possiblity in the library for use i 141) #574060 reportbug: Should make a backup/archive copy of bug reports und 142) #599290 consider using apt-cache instead of dpkg --status 143) #607850 reportbug: enable full specification (e.g. otherpkgs) of additi 144) #614011 reportbug: UI should be localized 145) #614149 reportbug: gtk ui: Display package name in window title 146) #614153 reportbug: Use tabs instead of windows 147) #620712 after the initial configuration, reportbug shouldn't quit 148) #624838 reportbug: need full-text search of bug reports 149) #625654 reportbug: Please add support for debbugs.gnu.org GNU bug track 150) #643733 support for sponsorship-requests pseudo package 151) #648552 reportbug: Add pagination while searching for similar-looking f 152) #653163 report bug should advise user that their bug report is stored i 153) #663933 reportbug: Allow user who opened bug to close it 154) #664896 reportbug: Program needs to be localized 155) #674854 querybts: please provide a way to retrieve the bugs without mai 156) #692995 reportbug: unblock requests: set affects src:$PACKAGE and Cc: $ 157) #707725 reportbug: Should complain when the From address matches FROM_D 158) #714896 reportbug: port to python3 159) #742227 reportbug: use ~/.config/ to save personal configuration 160) #743759 reportbug: Please provide a command line flag to provide extra (138-160/175) Is the bug you found listed above [y|N|b|m|r|q|s|f|e|?]? Bugs with severity wishlist 161) #745377 reportbug should check only matching names for wnpp 162) #770128 reportbug: please add a mode for reporting bugs in remote syste 163) #770554 reportbug: Remove "Are you sure you want to quit Reportbug" at 164) #773346 reportbug should provide information about active LSM 165) #777278 reportbug: In the UI, the last step of the wizard only offers Q 166) #779879 reportbug (gtk mode) asks for conformation when quiting from la 167) #783400 reportbug: include package taint information in reportbug repor 168) #787911 reportbug: Read config from XDG_CONFIG_HOME/debian/reportbugrc. 169) #788045 reportbug: please use the xdg-email program to send bugs via th 170) #797534 reportbug: Make use of PGP/MIME signatures 171) #804926 Please add debbugs.gnu.org to SYSTEMS list 172) #806804 Offer to display changelog for newer versions 173) #808972 reportbug: reports include authentication info 174) #810933 Please support connecting to SMTP via a SOCKS proxy 175) #835396 reportbug: detect ITPs on packages that were removed, mention r (161-175/175) Is the bug you found listed above [y|N|b|m|r|q|s|f|e|?]? Maintainer for reportbug is 'Reportbug Maintainers <reportbug-maint@lists.alioth.debian.org>'. Looking up dependencies of reportbug... Getting status for related package python-reportbug... Looking up 'depends' of related package python-reportbug... Looking up 'suggests' of related package python-reportbug... Getting changed configuration files... Common issues with reportbug: EXIM IS CONFIGURED FOR LOCAL DELIVERY: In Debian 4.0 (etch) and later, exim4 is configured by default to only deliver email to addresses on your system. YOUR BUG REPORTS WILL NOT ARRIVE AT THE BUG TRACKING SYSTEM UNLESS YOU FOLLOW ONE OF THE FOLLOWING STEPS: - Reconfigure exim (using 'dpkg-reconfigure -plow exim4') to send mail to the Internet directly or via a smarthost. - Configure reportbug to deliver mail to your ISP's smarthost or reportbug.debian.org directly (using 'reportbug --configure'). - Alternatively, see /usr/share/doc/reportbug/README.Users for instructions on how to use GMail's SMTP server to submit reports. EMAIL ADDRESS SETTING: See the manual page reportbug(1) for how to set your email address (i.e. the address that appears in the "From:" header), if reportbug is unable to correctly figure it out for you. Note that some mail systems will further rewrite the address displayed by reportbug when it starts. EDITORS: See the manual page reportbug(1) for how to choose an editor. --More-- You probably will want to have this setting for other tools as well. As an alternative, some mail programs, such as "mutt", can be configured to be used as the editor for your report, which you may find preferable. REPORTING: It is useful to include the full transcript of reportbug (with text ui) output, so we can see what it's trying to do and provide a faster and more precise response. GTK+ UI: There are some situation when the GTK+ stack crashes, reporting "Floating point exception" or GTK+ stack traces; those are bugs in GTK+ or misconfigurations (for example, using 'testing' suite can lead to such errors) on the current machine. Do not report bugs against reportbug in such situations but consult users support forums. (You may need to press 'q' to exit your pager and continue using reportbug at this point.) Briefly describe the problem (max. 100 characters allowed). This will be the bug email subject, so keep the summary as concise as possible, for example: "fails to send email" or "does not start with -q option specified" (enter Ctrl+c to exit reportbug without reporting a bug). > This is not a real bug report. Rewriting subject to 'reportbug: This is not a real bug report.' Removing release critical severities, since running in 'novice' mode. How would you rate the severity of this problem or report? 1 important a bug which has a major effect on the usability of a package, without rendering it completely unusable to everyone. 2 normal a bug that does not undermine the usability of the whole package; for example, a problem with a particular option or menu item. 3 minor things like spelling mistakes and other minor cosmetic errors that do not affect the core functionality of the package. 4 wishlist suggestions and requests for new features. Please select a severity level: [normal] Gathering additional data, this may take a while... Spawning ex... "/tmp/reportbug-reportbug-20160927-2356-6RUlhL" 74L, 2197C Entering Ex mode. Type "visual" to go to Normal mode. :/^\* *** Reporter, please consider answering these questions, where appropriate *** :c This is not a real bug report. . :/^\* *** End of the template - remove these template lines *** :d :%p Subject: reportbug: This is not a real bug report. Package: reportbug Version: 6.6.6 Severity: normal Dear Maintainer, This is not a real bug report. * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? -- Package-specific info: ** Environment settings: EDITOR="/usr/bin/ex" INTERFACE="text" ** /home/user/.reportbugrc: reportbug_version "6.6.6" mode novice ui text no-cc header "X-Debbugs-CC: user@debian.localdomain" smtphost reportbug.debian.org -- System Information: Debian Release: stretch/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 4.6.0-1-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages reportbug depends on: ii apt 1.3 ii python-reportbug 6.6.6 pn python:any <none> reportbug recommends no packages. Versions of packages reportbug suggests: pn claws-mail <none> pn debconf-utils <none> pn debsums <none> pn dlocate <none> pn emacs23-bin-common | emacs24-bin-common <none> ii file 1:5.28-4 ii gnupg 1.4.20-6 pn postfix | exim4 | mail-transport-agent <none> pn python-gtk2 <none> pn python-gtkspellcheck <none> pn python-urwid <none> pn python-vte <none> pn xdg-utils <none> Versions of packages python-reportbug depends on: ii apt 1.3 ii file 1:5.28-4 ii python-debian 0.1.29 ii python-debianbts 2.6.1 pn python:any <none> python-reportbug suggests no packages. -- no debconf information :wq "/tmp/reportbug-reportbug-20160927-2356-6RUlhL" 73L, 2091C written Report will be sent to "Debian Bug Tracking System" <sub...@bugs.debian.org> Submit this report on reportbug (e to edit) [Y|n|a|c|e|i|l|m|p|q|d|t|s|?]? Saving a backup of the report at /tmp/reportbug-reportbug-backup-20160927-2356-OkBVuZ Connecting to reportbug.debian.org via SMTP... SMTP send failure: (550, 'No valid sender found in the From:, Sender: and Reply-to: headers'). Do you want to retry (or else save the report and exit)? [Y|n|q|?]? n Wrote bug report to /tmp/reportbug-reportbug-20160927-2356-p4g0H5 $ ls -l total 20 -rw-r--r-- 1 user user 20480 Sep 27 21:54 transcript.txt $ # Hmm, where is rb.txt? $ exit
_______________________________________________ Reportbug-maint mailing list Reportbug-maint@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint