Example 6.2 Template generated by
reportbug
Subject: wireshark: does not dissect protocol foobar
Package: wireshark
Version: 3.2.5-1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
146
Kali Linux Revealed
-- System Information:
Distributor ID: Kali
Description:
Kali GNU/Linux Rolling
Release:
2020.3
Codename:
kali-rolling
Architecture: x86_64
Kernel: Linux 5.7.0-kali1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (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 wireshark depends on:
ii
wireshark-qt
3.2.5-1
wireshark recommends no packages.
wireshark suggests no packages.
-- no debconf information
Once you save the report and close the text editor, you return to
reportbug
, which provides many
other options and offers to send the resulting report.
Spawning sensible-editor...
Report will be sent to ”Debian Bug Tracking System”
Submit this report on wireshark (e to edit) [Y|n|a|c|e|i|l|m|p|q|d|t|s|?]? ?
Y - (default) Submit the bug report via email.
n - Don’t submit the bug report; instead, save it in a temporary file (exits reportbug).
a - Attach a file.
c - Change editor and re-edit.
e - Re-edit the bug report.
i - Include a text file.
l - Pipe the message through the pager.
m - Choose a mailer to edit the report.
p - print message to stdout.
q - Save it in a temporary file and quit.
d - Detach an attachment file.
t - Add tags.
s - Add a X-Debbugs-CC recipient (a CC but after BTS processing).
? - Display this help.
Submit this report on wireshark (e to edit) [Y|n|a|c|e|i|l|m|p|q|d|t|s|?]? Y
Saving a backup of the report at /tmp/reportbug-wireshark-backup-20210328-19073-87oJWJ
Connecting to reportbug.debian.org via SMTP...
Bug report submitted to: ”Debian Bug Tracking System”
Copies will be sent after processing to:
buxy@kali.org
147
Chapter 6 — Helping Yourself and Getting Help
If you want to provide additional information, please wait to receive the
bug tracking number via email; you may then send any extra information to
n@bugs.debian.org (e.g. 999999@bugs.debian.org), where n is the bug
number. Normally you will receive an acknowledgement via email including
the bug report number within an hour; if you haven’t received a
confirmation, then the bug reporting process failed at some point
(reportbug or MTA failure, BTS maintenance, etc.).
Filing a Bug Report in another Free Software Project
There is a large diversity of free software projects, using different workflows and tools. This di-
versity also applies to the bug trackers in use. While many projects are hosted on GitHub and use
GitHub issues to track their bugs, there are also many others hosting their own trackers, based
on Bugzilla, Trac, Redmine, Flyspray, and others. Most of them are web-based and require you to
register an account to submit a new ticket.
We will not cover all the trackers here. It is up to you to learn the specifics of various trackers for
other free software projects, but since
GitHub
7
is relatively popular, we will take a brief look at it
here. As with other trackers, you must first create an account and sign in. Next, click the Issues
tab, as shown in Figure
6.5
, “
Main page of a GitHub project
” [page 149].
7
https://github.com/
148
Kali Linux Revealed
|
