This bug was fixed in the package nmap - 7.80+dfsg1-2ubuntu0.1
---
nmap (7.80+dfsg1-2ubuntu0.1) focal; urgency=medium
* d/p/avoid-assertion-failure-when-unsolicited-arp-response-received.patch:
Check if a timeout clock is running before attempting to stop it.
(LP: #1908223)
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
** Tags removed: removal-candidate
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Hi, I marked the main bug task as Fix Released as this is fixed in >=
Hirsute, at least according to the packages versions. I tried to
reproduce the bug on Focal but as Sergio and Lucas I wasn't able to.
Without a reproducer it's difficult for us to assess the importance of
the bug and verify the f
** Also affects: nmap (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: nmap (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/19
Dear Ubuntu maintainers, do you have any plans of fixing this bug in Ubuntu
20.04 before Ubuntu 22.04 LTS release?
In upstream nmap it is said to be fixed since version 7.90 .
Do you consider importing version 7.92 into Ubuntu Focal ?
--
You received this bug notification because you are a mem
As Sergio, I was not able to reproduce the failure locally in my Focal
system. From the comments in the upstream bug it seems this is not
reliably reproducible, however, to land this fix in Focal and/or Bionic
we would need a set of steps that lead us to the bug.
@Stéphane/@Marek could you provide
I have the same problem.
With root user only.
$ /usr/bin/nmap -sP 192.168.0,10,11,13.*
nmap: Target.cc:503: void Target::stopTimeOutClock(const timeval*): Assertion
`htn.toclock_running == true' failed.
Aborted (core dumped)
It only works when setting "-max-parallelism" to a big value.
$ /usr
Thanks for taking the time to report a bug.
I am unable to reproduce the issue here. I've tried it on a Focal lxd
container, a Focal VM, and a Focal system (native). I'm always able to
execute the following commands:
# sudo nmap -n 192.168.1.1/24
# sudo nmap -4 -vvv -ddd -sn -PR 8.8.8.8
They a
** Changed in: nmap
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908223
Title:
nmap 7.80 crashes with Assertion `htn.toclock_running == true'
To manage not
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1908223
When reporting bugs in the future please use apport by using 'ubuntu-
bu
10 matches
Mail list logo
