Package: reportbug-gtk Version: 7.5.0 Followup-For: Bug #872772 Dear Maintainer,
This bug still persists as of today. Is that the supposed behavior? Luckily, reportbug saves the report in a file /tmp/reportbug-reportbug-gtk-* so one can edit it by opening it, but it'll be really cool to be able to edit it directly within reportbug-gtk. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages reportbug-gtk depends on: ii gir1.2-gtk-3.0 3.24.0-3 ii gir1.2-vte-2.91 0.54.0-1 ii python3-gi 3.28.3-1 ii python3-gi-cairo 3.28.3-1 ii python3-gtkspellcheck 4.0.5-1 ii reportbug 7.5.0 reportbug-gtk recommends no packages. reportbug-gtk suggests no packages. -- no debconf information
