Package: reportbug
Version: 3.20
Severity: grave
Justification: causes non-serious data loss

When reportbug is launched, it requires a brief description of the
problem from the user.  I type my problem and hit return, and then,
reportbug tells me the summary is too long, and ask me to input a
shorter description. After that, all the data I previously key in is
lost. I think there should be some limitation on the count of characters to be 
typed in the summary or I don't know whether the summary I wrote is too long or 
not.  Otherwise, if it's too long, reportbug had better save the long 
description for later use, and prompt the user to input a shorter title.  Then, 
reportbug can automatically fill in the content of the final report which is 
opened in editor with previously saved long description.  This is not only 
fool-proof, but it also increase the usability. If newbies use reportbug first 
time, and don't know they should just input a title, and the full description 
can be done later, they will accidentally lost their bug report, and get 
frustrated.  The result may be they don't want to write that bug report again, 
and the bug cannot enter bug reporting system.

-- Package-specific info:
** /home/pcman/.reportbugrc:
reportbug_version "3.20"
mode novice
ui text
realname "Hong Jen Yee (PCMan)"
email "[EMAIL PROTECTED]"
no-cc
header "X-Debbugs-CC: [EMAIL PROTECTED]"
smtphost bugs.debian.org

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-686
Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8)

Versions of packages reportbug depends on:
ii  python2.3                     2.3.5-9.1  An interactive high-level object-o

Versions of packages reportbug recommends:
ii  python2.3-cjkcodecs           1.1.1-1    Python Unicode Codecs Collection f

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to