[Reportbug-maint] Bug#849243: reportbug: TypeError: * wants int

Boyuan Yang 073plan at gmail.com
Sat Dec 24 04:05:42 UTC 2016


Package: reportbug
Version: 7.1.1
Severity: grave

Hello,

Reportbug crashed when I was trying to report a bug, even if I am using text 
UI. ( I have to use email to report it :-/ ).

The terminal output is as follow:

% reportbug --ui=text
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 at lists.debian.org for assistance.
> krita
*** 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 'Boyuan Yang <073plan at gmail.com>' as your from address.
Getting status for krita...
Checking for newer versions at madison, incoming.debian.org and http://ftp-master.debian.org/new.html
Will send report to Debian (per lsb_release).
Querying Debian BTS for reports on krita (source)...
2 bug reports found:

Bugs with severity serious
  1) #811432  sid: unable to install, missing deps: libilmbase6 libope
Bugs with severity normal
  2) #813570  krita-1.2.8.5+dfsg-1: Krita crashes by creating a new wo
(2-2/2) Is the bug you found listed above [y|N|b|m|r|q|s|f|e|?]? n
Maintainer for krita is 'Debian Qt/KDE Maintainers <debian-qt-
kde at lists.debian.org>'.
Looking up dependencies of krita...
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).
> segfault on startup
Rewriting subject to 'krita: segfault on startup'

Enter any additional addresses this report should be sent to; press
ENTER after each address. Press ENTER on a blank line to continue.
> 

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] grave
You are reporting a grave bug; which of the following criteria does it
meet?

Traceback (most recent call last):
  File "/usr/bin/reportbug", line 2233, in <module>
    main()
  File "/usr/bin/reportbug", line 1107, in main
    return iface.user_interface()
  File "/usr/bin/reportbug", line 1968, in user_interface
    'Please select the impact of the bug: ', default='unknown')
  File "/usr/lib/python3/dist-packages/reportbug/ui/text_ui.py", line 362, in 
menu
    starttext=('%*d %-*.*s  ' % (digits, i, maxlen_name, maxlen_name, name)))
TypeError: * wants int

--
Sincerely,
Boyuan Yang
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/reportbug-maint/attachments/20161224/9796c35c/attachment.sig>


More information about the Reportbug-maint mailing list