[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#653163: marked as done (report bug should advise user that their bug report is stored in /tmp upon quitting.)

Your message dated Sun, 5 Apr 2020 09:41:56 +0200
with message-id <d311d739-eec4-7b46-5ad9-4f39d1e7c4d0@web.de>
and subject line Re: report bug should advise user that their bug report is stored in /tmp upon quitting.
has caused the Debian Bug report #653163,
regarding report bug should advise user that their bug report is stored in /tmp upon quitting.
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.)


-- 
653163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653163
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: reportbug
Version: 6.3.1
Severity: wishlist

When using reportbug, if a user mistakenly chooses an option that won't
work, s/he has no choice but to "quit" since there isn't a back button.
At this point it appears to the regular user as if the bug report just
typed in has been lost. There is no indication that reportbug saves this
in /tmp. It appears to the user as if s/he has just lost the report and
would have to start all over again, which contributes to user
frustration and decreases the likelihood of user contribution of bug
reports.

A simple notification upon quitting that the report up to that point has
been saved in /tmp/filename would alleviate this problem.


-j

--- End Message ---
--- Begin Message --- 
Version: 7.6.0

On 24 Dec 2011 josh wrote:
> A simple notification upon quitting that the report up to that point has
> been saved in /tmp/filename would alleviate this problem.

This bug existed only in the GTK interface of reportbug. It has been
fixed in reportbug 7.6.0 which was uploaded in December 2019.

--- End Message ---
Reply to: