Package: reportbug
Version: 6.3.1
Severity: normal
When reportbug is invoked to get the GTK+ interface, it can fail
incorrectly if python-gtk is missing. reportbug only suggests
python-gtk, which is probably a good thing, but this forces reportbug to
expect python-gtk can be missing. When python-gtk is missing, reportbug
seems to have no idea what --ui gtk2 means:
$ reportbug --ui gtk2
Ignored bogus setting for --ui: gtk2
Please enter the name of the package in which you have found a
problem, or type 'other' to report a more general problem. [...]
While this is misleading on the command line, this is worst when using
reportbug's menu item. That quietly fails.
Although fixing the output on the command line shouldn't be a great
challenge, I'm not sure what should be done about the menu item.
Reportbug could launch its text UI as a fallback, but that would need a
x-terminal-emulator. Should the menu item be moved to a new package just
for the UI :-?
--- System information. ---
Architecture: i386
Kernel: Linux 3.1.0-1-amd64
Debian Release: wheezy/sid
990 testing security.debian.org
990 testing ftp.ca.debian.org
500 unstable ftp.ca.debian.org
1 experimental ftp.ca.debian.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
