Submitted to bug tracker:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883577 
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883577>

> On 5 Dec 2017, at 11:34, Sophie Loewenthal <sop...@klunky.co.uk> wrote:
> 
> Hi,
> 
> Submitting a bug report via reportbug 7.1.7 programme produced:
> 
> Traceback (most recent call last):
>  File "/usr/bin/reportbug", line 2234, in <module>
>    main()
>  File "/usr/bin/reportbug", line 1107, in main
>    return iface.user_interface()
>  File "/usr/bin/reportbug", line 1225, in user_interface
>    main()
>  File "/usr/bin/reportbug", line 1107, in main
>    return iface.user_interface()
>  File "/usr/bin/reportbug", line 2150, in user_interface
>    package, severity, mode, charset=charset, tags=tags)
>  File "/usr/bin/reportbug", line 182, in handle_editing
>    editor, charset)
>  File "/usr/lib/python3/dist-packages/reportbug/ui/text_ui.py", line 1064, in 
> spawn_editor
>    newmessage = open(filename).read()
>  File "/usr/lib/python3.5/encodings/ascii.py", line 26, in decode
>    return codecs.ascii_decode(input, self.errors)[0]
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 1780: 
> ordinal not in range(128)
> 
> 
> # cat .reportbugrc 
> # reportbug preferences file
> # character encoding: us-ascii
> # Version of reportbug this preferences file was written by
> reportbug_version "7.1.7"
> # default operating mode: one of: novice, standard, advanced, expert
> mode standard
> # default user interface
> ui text
> # offline setting - comment out to be online
> #offline
> # name and email setting (if non-default)
> realname "Sophie L"
> email "withh...@klunky.co.uk"
> # Suppress user ID check for this user
> no-check-uid
> # If nothing else works, remove the # at the beginning
> # of the following three lines:
> #no-cc
> #header "X-Debbugs-CC: withh...@klunky.co.uk"
> #smtphost reportbug.debian.org
> # You can add other settings after this line.  See
> # /etc/reportbug.conf for a full listing of options.
> 
> 
> 
> Full copy and paste from session, but the vi entries are missed:
> 
> # reportbug
> 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 "/root/.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] 2
> 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|?]? y
> What real name should be used for sending bug reports?
> [root]> Sophie L
> 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.)
> [r...@cmx12.klunky.co.uk]> withh...@klunky.co.uk
> 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|?]? 
> reportbug: exiting due to user interrupt.
> root@cmx12:/etc# reportbug
> 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 "/root/.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] 2
> 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|?]? y
> What real name should be used for sending bug reports?
> [root]> Sophie L
> 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.)
> [r...@cmx12.klunky.co.uk]> withh...@klunky.co.uk
> 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|?]? y
> 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.
> Running 'reportbug' as root is probably insecure! Continue [y|N|q|?]? y
> 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-user@lists.debian.org for assistance.
>> redis-server
> *** Welcome to reportbug.  Use ? for help at prompts. ***
> Note: bug reports are publicly archived (including the email address of the 
> submitter).
> Detected character set: us-ascii
> Please change your locale if this is incorrect.
> 
> Using 'Sophie <withh...@klunky.co.uk>' as your from address.
> Getting status for redis-server...
> Will send report to Debian (per lsb_release).
> Querying Debian BTS for reports on redis (source)...
> 6 bug reports found:
> 
> Bugs with severity serious
>  1) #868551  File conflict between redis-server-dbgsym and redis-tools-dbgsym 
>  [RESOLVED]
> Bugs with severity important
>  2) #881682  redis: FTBFS on alpha and sparc64: [err]: Memory efficiency with 
> values in range 16384  [RESOLVED]
>  3) #881683  redis: FTBFS on kFreeBSD: taskset: Command not found  [RESOLVED]
>  4) #881684  redis: FTBFS on hurd-i386: MAXPATHLEN undeclared  [RESOLVED]
> Bugs with severity minor
>  5) #880474  redis-server: Unknown lvalue 'RunTimeDirectory' in section 
> 'Service'
> Bugs with severity wishlist
>  6) #876475  redis-server: Make "apt install redis" work  [RESOLVED]
> (6-6/6) Is the bug you found listed above [y|N|b|m|r|q|s|f|e|?]? n
> Maintainer for redis-server is 'Chris Lamb <la...@debian.org>'.
> Looking up dependencies of redis-server...
> Getting changed configuration files...
> 
> 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).
>> redis-server.service ExecStart=/usr/bin/redis-server /etc/redis/redis.conf 
>> (code=exited, status=226/NAMESPACE)
> Your description is a bit long; please enter a shorter subject. (An empty 
> response will retain the existing subject.)
>> ExecStart=/usr/bin/redis-server /etc/redis/redis.conf (code=exited, 
>> status=226/NAMESPACE)
> Rewriting subject to 'redis-server: ExecStart=/usr/bin/redis-server 
> /etc/redis/redis.conf (code=exited, status=226/NAMESPACE)'
> How would you rate the severity of this problem or report?
> 
> 1 critical        makes unrelated software on the system (or the whole 
> system) break, or causes serious data loss, or introduces a
>                  security hole on systems where you install the package.
> 2 grave           makes the package in question unusable by most or all 
> users, or causes data loss, or introduces a security hole
>                  allowing access to the accounts of users who use the package.
> 3 serious         is a severe violation of Debian policy (that is, the 
> problem is a violation of a 'must' or 'required' directive);
>                  may or may not affect the usability of the package. Note 
> that non-severe policy violations may be 'normal,'
>                  'minor,' or 'wishlist' bugs. (Package maintainers may also 
> designate other bugs as 'serious' and thus release-
>                  critical; however, end users should not do so.). For the 
> canonical list of issues worthing a serious severity you
>                  can refer to this webpage: 
> http://release.debian.org/testing/rc_policy.txt .
> 4 important       a bug which has a major effect on the usability of a 
> package, without rendering it completely unusable to everyone.
> 5 does-not-build  a bug that stops the package from being built from source. 
> (This is a 'virtual severity'.)
> 6 normal          a bug that does not undermine the usability of the whole 
> package; for example, a problem with a particular option
>                  or menu item.
> 7 minor           things like spelling mistakes and other minor cosmetic 
> errors that do not affect the core functionality of the
>                  package.
> 8 wishlist        suggestions and requests for new features.
> 
> Please select a severity level: [normal] 4
> Do any of the following apply to this report?
> 
> 1 d-i       This bug is relevant to the development of debian-installer.
> 2 ipv6      This bug affects support for Internet Protocol version 6.
> 3 l10n      This bug reports a localization/internationalization issue.
> 4 lfs       This bug affects support for large files (over 2 gigabytes).
> 5 newcomer  This bug has a known solution but the maintainer requests someone 
> else implement it.
> 6 patch     You are including a patch to fix this problem.
> 7 upstream  This bug applies to the upstream part of the package.
> 8 none      
> 
> Please select tags: (one at a time) [none] 1
> - selected: d-i
> Please select tags: (one at a time) [done] 
> Spawning vi...
> Traceback (most recent call last):
>  File "/usr/bin/reportbug", line 2234, in <module>
>    main()
>  File "/usr/bin/reportbug", line 1107, in main
>    return iface.user_interface()
>  File "/usr/bin/reportbug", line 1225, in user_interface
>    main()
>  File "/usr/bin/reportbug", line 1107, in main
>    return iface.user_interface()
>  File "/usr/bin/reportbug", line 2150, in user_interface
>    package, severity, mode, charset=charset, tags=tags)
>  File "/usr/bin/reportbug", line 182, in handle_editing
>    editor, charset)
>  File "/usr/lib/python3/dist-packages/reportbug/ui/text_ui.py", line 1064, in 
> spawn_editor
>    newmessage = open(filename).read()
>  File "/usr/lib/python3.5/encodings/ascii.py", line 26, in decode
>    return codecs.ascii_decode(input, self.errors)[0]
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 1780: 
> ordinal not in range(128)

Reply via email to