Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
From: Joshua Winkler <josh@bemoty.dev>
To: tools@kernel.org
Cc: Joshua Winkler <josh@bemoty.dev>
Subject: [PATCH] Replace dead distro bug report links
Date: Thu, 12 Nov 2026 20:10:00 +0100	[thread overview]
Message-ID: <20261112191000.162374-1-josh@bemoty.dev> (raw)

The Ubuntu help page returns 503, Arch moved to GitLab, and the old
Linux Mint page doesn't resolve at all. The new links should give
users a good place to start for bug reports.

Signed-off-by: Joshua Winkler <josh@bemoty.dev>
---
 content/faq.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/content/faq.rst b/content/faq.rst
index 82753d2..1f16b13 100644
--- a/content/faq.rst
+++ b/content/faq.rst
@@ -118,10 +118,10 @@ If you are running a kernel that came with your Linux distribution, then
 the right place to start is by reporting the problem through your
 distribution support channels. Here are a few popular choices:
 
-- `Ubuntu <https://help.ubuntu.com/stable/ubuntu-help/report-ubuntu-bug.html.en>`_
+- `Ubuntu <https://ubuntu.com/project/docs/contributors/qa-and-testing/report-a-bug/>`_
 - `Fedora Project <https://docs.fedoraproject.org/en-US/quick-docs/howto-file-a-bug/>`_
-- `Arch Linux <https://bugs.archlinux.org/>`_
-- `Linux Mint <https://projects.linuxmint.com/reporting-an-issue.html>`_
+- `Arch Linux <https://wiki.archlinux.org/title/Bug_reporting_guidelines>`_
+- `Linux Mint <https://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/>`_
 - `Debian GNU/Linux <https://www.debian.org/Bugs/Reporting>`_
 - `Red Hat <https://bugzilla.redhat.com/>`_
 - `OpenSUSE <https://bugzilla.opensuse.org/>`_
-- 
2.56.1


             reply	other threads:[~2026-11-12 19:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-12 19:10 Joshua Winkler [this message]
2026-11-12 19:28 ` [PATCH] Replace dead distro bug report links Konstantin Ryabitsev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20261112191000.162374-1-josh@bemoty.dev \
    --to=josh@bemoty.dev \
    --cc=tools@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox