On Wed, Feb 05, 2025 at 02:22:18PM -0300, Renan Rodrigo Barbosa wrote:
> ### Bug Triage ###
> 1778959 <https://bugs.launchpad.net/ubuntu/+source/iptraf-ng/+bug/1778959>
> (iptraf-ng)
> Old bug, ressurrected by a user who sent a crash report on focal. I tried
> to reproduce it on bionic and focal, without success. Tagged as discussion
> - what to do with possible < focal bugs at this point in time?
I'm not a fan of resurrecting bugs via "me too" comments, however this
case might be actionable. As a general rule, I usually ask the new
commenter to open a fresh bug report. It's super common for crashes to
*feel* like the same thing but until there's stack traces available it
means nothing; crash bugs often have similar behaviors but different
causes, and some crashes with the exact same cause can show up in a
variety of ways. So, I like to see crashes reported as distinct bugs
until proper analysis is done. They can always be duped up later,
that's easy.
However, in this case I'm not sure it's worth having the commenter go
through the trouble. The original report never got a crash dump or
stack trace, so probably should have expired due to lack of requested
info, but they did mention this was a well known issue in the
community. From the AskUbuntu link they provided, it sounds like this
was fixed in a newer version that looks to be included in noble but not
in focal. There is a link to a patch but it's 404'd. But googling for
that exact patch name turns up this CentOS changeset:
https://git.dev.centos.org/rpms/iptraf-ng/c/7451319602c3b35c55b9f715d57bea41d9e85f56
I would suggest following this link and looking to see if you can find a
matching upstream bug or discussion that illuminates the problem better.
At the same time, ask the reporter if they are able to reproduce the
crash themselves, and if so, if they'd be willing to perform the testing
if we provide packages of the patch for them to install and test. Since
three triagers have been unable to reproduce the problem, that's really
the only way forward for this issue.
Unfortunately, if they can't reproduce it at will, and can't direct us
on how to reproduce it, it's not going to make it through the SRU
process, and probably should just remain on our backlog. But if they
can trigger the crash, then it may be worth moving forward with
packaging the patch for a PPA and see how things go.
Bryce
--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
