Hello, wmfinck, thanks for reaching out. I have looked at the Focal (20.04) crash report you sent, and indeed it does appear to be the same bug as reported before for Bionic (18.04).
There is still time to get stable release updates (SRUs) for Focal, and this does look to be a valid bug worth fixing, however to get an SRU accepted usually requires exact steps to reproduce the issue. Unfortunately, neither I or others could reproduce the bug to verify the solution on Focal. Perhaps there is some extra step, or environment condition, or something else that triggers the bug? @wmfinck, are you able to easily trigger the crash? Or does it happen frequently enough that you could tell for certain if it is still happening or resolved? We found a possible patch, available at https://git.dev.centos.org/rpms/iptraf- ng/c/7451319602c3b35c55b9f715d57bea41d9e85f56 - this was applied upstream in version 1.2.0, which is included in Jammy (22.04). We've not been able to locate a matching bug report (all of the pointers are returning a 404...) We'll have have more luck getting an SRU accepted if the dots can be connected with upstream's analysis, so any help locating where that work was discussed may help move things forward. ** Tags removed: log server-triage-discuss -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778959 Title: error floating point exception To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptraf-ng/+bug/1778959/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
