Bug#1029313: marked as done (reportbug: Reportbug GUI does not have a back button after selecting a package to report)
Your message dated Sat, 21 Jan 2023 12:23:17 +0100
with message-id <b29b3c6d-dfbb-cb72-5444-f1dc1df8562e@mailbox.org>
and subject line Re: Bug#1029313: reportbug: Reportbug GUI does not have a back button after selecting a package to report
has caused the Debian Bug report #1029313,
regarding reportbug: Reportbug GUI does not have a back button after selecting a package to report
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.)
--
1029313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029313
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: reportbug
Version: 7.10.3+deb11u1
Severity: important
X-Debbugs-Cc: iam@heston.ca
Dear Maintainer,
Without a back button, any errors made are difficult to correct.
There is also no way to not select an option on the page "Do any of the
following apply to this report" once an option is selected.
-- Package-specific info:
** Environment settings:
INTERFACE="gtk"
** /home/heston/.reportbugrc:
reportbug_version "7.10.3+deb11u1"
mode standard
ui gtk
realname "Heston Corbeil"
email "iam@heston.ca"
no-cc
list-cc-me
smtphost reportbug.debian.org
-- System Information:
Debian Release: 11.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-12-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages reportbug depends on:
ii apt 2.2.4
ii python3 3.9.2-3
ii python3-reportbug 7.10.3+deb11u1
ii sensible-utils 0.0.14
reportbug recommends no packages.
Versions of packages reportbug suggests:
pn claws-mail <none>
pn debconf-utils <none>
ii debsums 3.0.2
pn dlocate <none>
pn emacs-bin-common <none>
ii exim4-daemon-light [mail-transport-agent] 4.94.2-7
ii file 1:5.39-3
ii gnupg 2.2.27-2+deb11u2
pn python3-urwid <none>
pn reportbug-gtk <none>
ii xdg-utils 1.1.3-4.1
Versions of packages python3-reportbug depends on:
ii apt 2.2.4
ii file 1:5.39-3
ii python3 3.9.2-3
ii python3-apt 2.2.1
ii python3-debian 0.1.39
ii python3-debianbts 3.1.0
ii python3-requests 2.25.1+dfsg-2
ii sensible-utils 0.0.14
python3-reportbug suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On 21.01.2023, Heston Corbeil wrote:
> Without a back button, any errors made are difficult to correct.
The best solution is to close reportbug, start a new instance and
provide your correct inputs there.
With a back button, going back and changing previously input information
might force reportbug to discard information that you may have already
input in a later step of the dialog. This is problematic (bad user
experience), so there are no plans to implement it. Closing.
> There is also no way to not select an option on the page "Do any of the
> following apply to this report" once an option is selected.
This is fixed in newer versions (since reportbug 11.3.0). In older
versions you can unselect an item by holding down the Ctrl key when
clicking.
--- End Message ---
Reply to: