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

Bug#1009322: marked as done (reportbug-gtk: sending bugreport via Debian mail fails)

Your message dated Wed, 13 Apr 2022 00:15:13 +0200
with message-id <1e456f02-ec97-f227-9513-1d5a89d86bcf@mailbox.org>
and subject line Re: Bug#1009322: reportbug-gtk: sending bugreport via Debian mail fails
has caused the Debian Bug report #1009322,
regarding reportbug-gtk: sending bugreport via Debian mail fails
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.)


-- 
1009322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009322
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: reportbug-gtk
Version: 11.4.1
Severity: serious
Justification: unusuable

Dear Maintainer,

*** Reporter, please consider answering these questions, where
appropriate ***

   * What led up to the situation?
I tried to file a bugreport against a debian 5.17. trunk kernel. When
*finished* I wanted to send it via the configured  mail provider
     (debian). But it failed (as did nearly all bug reports within the
     last year or so). Additionally the then generated temp file
     containing the report now cannot be opened again for whatever
     reason. This is frustrating for whoever tries to provide usefull
     info. I am NOT going to write several wishbugs now. It is OBVIOUS
     that, if the mail fails, reportbug has to go back to the previous
     menu to then allow one of the other options. Otherwise you (we?)
     lose reports and people who want to participate.

I append the (corrupted?) tmp file with the bug report against the 5.17
trunk kernel.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

I wanted to send a bug report (about 5.17-trunk kernel), but reportbug
prevented me from doing so.


-- 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.17.0-trunk-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_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.33-1
ii  gir1.2-gtksource-4     4.8.3-1
ii  gir1.2-vte-2.91        0.68.0-1
ii  python3-gi             3.42.0-3
ii  python3-gi-cairo       3.42.0-3
ii  python3-gtkspellcheck  4.0.5-2
ii  reportbug              11.4.1

reportbug-gtk recommends no packages.

reportbug-gtk suggests no packages.

-- no debconf information

Attachment: reportbug-linux-image-5.17.0-trunk-amd64-20220411200412-9nrx78r9
Description: Binary data


--- End Message ---
--- Begin Message --- 
On 11.04.2022, Michael Hatzold wrote:
> I tried to file a bugreport against a debian 5.17. trunk kernel. When
> *finished* I wanted to send it via the configured  mail provider
>      (debian). But it failed (as did nearly all bug reports within the
>      last year or so). Additionally the then generated temp file
>      containing the report now cannot be opened again for whatever
>      reason. [...]
Michael, you would receive a better response to your message if you'd
file a proper bug report instead of a complaint.

Since you left out any information that would allow us to reproduce and
investigate the problem, I'm closing this. If there is a real problem,
please learn how to submit a proper report and then try again. Thanks.

Some things you may want to look into:
 - reportbug's --resume-saved option for temporary files
 - reportbug's MUA support
 - "REPORTING: It is useful to include the full transcript of reportbug
   (with text ui) output, so we can see what it's trying to do and
   provide a faster and more precise response."

--- End Message ---
Reply to: