[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#814454: marked as done (reportbug: Crash when trying to configure non-ASCII characters for realname via CLI)



Your message dated Sat, 19 Dec 2020 21:26:36 +0100
with message-id <da9dc25d-ccc7-fa05-8598-51d30fadc4a5@web.de>
and subject line Re: Bug#814454: reportbug: Crash when trying to configure non-ASCII characters for realname via CLI
has caused the Debian Bug report #814454,
regarding reportbug: Crash when trying to configure non-ASCII characters for realname via CLI
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 owner@bugs.debian.org
immediately.)


-- 
814454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814454
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: reportbug
Version: 6.6.3
Severity: normal

Dear Maintainer,

During the initial configuration of reportbug I was prompted for a real name.
Unfortunately using umlauts results in the following exception:

-----
What real name should be used for sending bug reports?
[root]> Linus Lüssing
Traceback (most recent call last):
  File "/usr/bin/reportbug", line 2211, in <module>
    main()
  File "/usr/bin/reportbug", line 1081, in main
    return iface.user_interface()
  File "/usr/bin/reportbug", line 1197, in user_interface
    offer_configuration(self.options)
  File "/usr/bin/reportbug", line 578, in offer_configuration
    realname = realname.decode(charset, 'replace')
  File "/usr/lib/python2.7/encodings/utf_8.py", line 16, in decode
    return codecs.utf_8_decode(input, errors, True)
UnicodeEncodeError: 'ascii' codec can't encode character u'\xfc' in position 7: ordinal not in range(128)
-----

Regards, Linus


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

** /root/.reportbugrc:
reportbug_version "6.6.3"
mode standard
ui text
realname "Linus Luessing"
email "linus.luessing@c0d3.blue"
no-check-uid
no-cc
header "X-Debbugs-CC: linus.luessing@c0d3.blue"
smtphost reportbug.debian.org

-- System Information:
Debian Release: 8.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i586)

Kernel: Linux 3.16.0-4-586
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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.8.2
ii  python            2.7.9-1
ii  python-reportbug  6.6.3
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.22+15-2+deb8u1
ii  gnupg                                    1.4.18-7
ii  msmtp-mta [mail-transport-agent]         1.4.32-2
pn  python-gtk2                              <none>
pn  python-gtkspell                          <none>
pn  python-urwid                             <none>
pn  python-vte                               <none>
pn  xdg-utils                                <none>

Versions of packages python-reportbug depends on:
ii  apt               1.0.9.8.2
ii  python-debian     0.1.27
ii  python-debianbts  1.12
pn  python:any        <none>

python-reportbug suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 6.6.6

On Tue, 22 Mar 2016 Linus Lüssing wrote:
Hi Sandro,

On Fri, Mar 04, 2016 at 09:39:53PM +0000, Sandro Tosi wrote:
> I've uploaded to backports version 6.6.6 of reportbug which should
> address this bug: please install that and report back if that's fixed.

Just tried and 6.6.6 works like a charm on the same device, issue
seems to be fixed in there :).

Thanks. Closing.

--- End Message ---

Reply to: