diff options
| author |  glitsj16 <glitsj16@users.noreply.github.com> | 2024-06-14 08:59:38 +0000 |
|---|---|---|
| committer |  GitHub <noreply@github.com> | 2024-06-14 08:59:38 +0000 |
| commit | 386ee003d2c5b780969ab3e5ea98404dfa828ce4 (patch) | |
| tree | fedb5ec3163c4cce431b11f05dc28fca69954ec0 | |
| parent | profiles: hashcat: support newer configuration paths (#6376) (diff) | |
| download | firejail-386ee003d2c5b780969ab3e5ea98404dfa828ce4.tar.gz firejail-386ee003d2c5b780969ab3e5ea98404dfa828ce4.tar.zst firejail-386ee003d2c5b780969ab3e5ea98404dfa828ce4.zip | |
docs: bug_report.md: use absolute path in 'steps to reproduce' (#6382)
We still see lots of issue reports where the user runs `firejail foo`
and ends up running foo's sandbox twice (due to firecfg's symlink
precedence). Try to improve the situation by explicitly using absolute
paths in the 'steps to reproduce' section.
| -rw-r--r-- | .github/ISSUE_TEMPLATE/bug_report.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md index fc74640d4..37056a1ce 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.md +++ b/.github/ISSUE_TEMPLATE/bug_report.md | |||
| @@ -22,7 +22,7 @@ _Describe the bug_ | |||
| 22 | 22 | ||
| 23 | _Steps to reproduce the behavior_ | 23 | _Steps to reproduce the behavior_ |
| 24 | 24 | ||
| 25 | 1. Run in bash `LC_ALL=C firejail PROGRAM` (`LC_ALL=C` to get a consistent | 25 | 1. Run in bash `LC_ALL=C firejail /path/to/program` (`LC_ALL=C` to get a consistent |
| 26 | output in English that can be understood by everybody) | 26 | output in English that can be understood by everybody) |
| 27 | 2. Click on '....' | 27 | 2. Click on '....' |
| 28 | 3. Scroll down to '....' | 28 | 3. Scroll down to '....' |