--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: reportbug-gtk: incomplete and thus wrong message after sending re-opend tmp file
- From: Michael Hatzold <m.hatzold@web.de>
- Date: Fri, 19 Nov 2021 14:14:38 +0100
- Message-id: <163732767878.94844.15569766937022509212.reportbug@localhost>
Package: reportbug-gtk
Version: 11.1.0
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Due to SMTP overload reportbug saved the report to a tmp file.
Sending the report based on the re-opened tmp file resulted in a message along
the lines: "bug report written to tmp file etc ...", but nothing about "file
successfully sent". This gives you the impression, the file was *not* sent. So
I re-tried until the SMTP answer stopped me ....
* What outcome did you expect instead?
Please give a informative feedback (file successfully sent and written to....)
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.15.2-4-siduction-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/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.30-3
ii gir1.2-gtksource-4 4.8.2-1
ii gir1.2-vte-2.91 0.66.1-1
ii python3-gi 3.42.0-2
ii python3-gi-cairo 3.42.0-2
ii python3-gtkspellcheck 4.0.5-2
ii reportbug 11.1.0
reportbug-gtk recommends no packages.
reportbug-gtk suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
- To: Michael Hatzold <m.hatzold@web.de>, 1000196-done@bugs.debian.org
- Subject: Re: Bug#1000196: reportbug-gtk: incomplete and thus wrong message after sending re-opend tmp file
- From: Nis Martensen <nis.martensen@web.de>
- Date: Sat, 12 Feb 2022 22:48:10 +0100
- Message-id: <74c9d933-2772-0fea-6652-8ea917e8ef1c@web.de>
- In-reply-to: <507820626.493930.1637409316874@office.mailbox.org>
- References: <163732767878.94844.15569766937022509212.reportbug@localhost> <507820626.493930.1637409316874@office.mailbox.org>
On 20.11.2021 12.55, nis.martensen@web.de wrote:
> control: tags -1 moreinfo
>
> Michael Hatzold hat am 19.11.2021 geschrieben:
>> Due to SMTP overload reportbug saved the report to a tmp file.
>>
>> Sending the report based on the re-opened tmp file resulted in a message along
>> the lines: "bug report written to tmp file etc ...", but nothing about "file
>> successfully sent". This gives you the impression, the file was *not* sent. So
>> I re-tried until the SMTP answer stopped me ....
>>
>> * What outcome did you expect instead?
>> Please give a informative feedback (file successfully sent and written to....)
>
> Please provide the necessary information that could allow us to understand and reproduce the bug:
> - What is your reportbug configuration?
> - How did you invoke reportbug? (complete and exact command line, please)
> - Does the problem also occur if you use the text interface? Or are you saying this is a specific problem with the GTK interface?
> - How did you check whether the mail was sent? What do you mean by "SMTP answer stopped me"?
>
> Since the build-in report submission support provides only basic functionality, you might want to look into reportbug's MUA integration feature for a better user experience.
Closing since no additional information has been provided.
--- End Message ---