moth
moth
Hey folks, I just had a similar error on a Kali box but found that running from source fixed the issue. The latest version of the code handles pathing better...
Ran into the same issue as well. Traced the issue down the Pyppeteer itself, though not sure why it's happening yet: https://github.com/pyppeteer/pyppeteer/blob/7486b56c072be469f5d9f7ac797f59ecea2a5c65/pyppeteer/page.py#L1249 [Update 1] I did a kludge patch in...
@weuroi578 in case you're still hoping to use WitnessMe ^ Hope that helps for you.
Hmm, I recall seeing something similar to this a while ago, perhaps. I can look into this.
@william-stearns: This issue only appears upon a first run of the installer. Running the installer a second time does not cause this behaviour. I'm looking into the fix now. [EDIT]:...
Solution will likely be a check in the script to ensure that no PIDs exist for `apt` or `dpkg`. I'm still looking into it.
Cool, thanks for that! I'll roll something similar into branch in the next couple of days and let you know.
This is something I'm working on addressing as part of a wider setup.sh rewrite/refactor, also including support for aarch64.
As promised (for once)
Hey @atharvak95 , thanks for reporting this issue. The output of your setup script seems fine from here. I can think of a few things to try. First, after uninstalling...