New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zenmap closes immediately upon entering password nmap 7.0 #235
Comments
I forgot, here's the command output: Traceback (most recent call last): |
I have encountered this issue on OSX 10.10.5. Log output in /var/log/system.log:
|
http://www.gtk.org/download/macos.php saving this here.
|
Quick hack: Just create the missing file: sudo mkdir -p /Applications/Zenmap.app/Contents/Resources/etc/pango && touch /Applications/Zenmap.app/Contents/Resources/etc/pango/pangorc.in |
@functio Thanks for this workaround! |
@functio ditto workaround! |
@functio thank you very much!it work! |
I believe this bug should be resolved with the 7.01 release. Please try the new .dmg installer at https://nmap.org/download.html#macosx and let us know if it solves this issue for you. |
@dmiller-nmap 7.01 is good! i can use it in OSX 10.11.2 |
I believe this bug should be resolved with the 7.01 release. Yep; sorted thank you. |
Thanks all! Keep scanning and reporting bugs. |
I hate to re-has old issues, but this is happening on a fresh install of 10.11.3 with NMAP 7.0.1 installer. Anything i should be looking for? The workaround listed above also does not work. |
FYI -- im getting a different command line error But the file is there... |
Ditto on failing to closing after entering password. NMap 7.12
Found solution
|
@vinnytroia Please upgrade to Nmap 7.12, which should solve this issue. As @cybernorris points out, you may need to delete the |
All you have to do to open Zenmap if this happens is to open terminal and put this in |
this worked for me. thanks. |
Just installed 7.0 in Yosemite, no previous versions of nmap or zenmap were on this system.
I launch zenmap, put in my password, and it immediately closes.
Thoughts?
The text was updated successfully, but these errors were encountered: