Explore >> Select a destination
|
You are here 
|
roneo.org | ||
| | | | |
themythicalengineer.com
|
|
| | | | | Blog about Software Engineering | |
| | | | |
codebenchers.com
|
|
| | | | | Learn how to set up an anonymous, private web development environment using Tails OS, VSCodium and Node.js. Leverage the security of Tails OS to safeguard your online anonymity. | |
| | | | |
bisco.org
|
|
| | | | | Because the topic comes up every now and then, I thought I'd write down how to install and run Signal on Tails. These instructions are based on the 2nd Beta of Tails 4.0 - the 4.0 release is scheduled for October 22nd. I'm not sure if these steps also work on Tails 3.x, I seem to remember having some problems with installing flatpaks on Debian Stretch. The first thing to do is to enable the Additional Software feature of Tails persistence (the Personal Data feature is also required, but that one is enabled by default when configuring persistence). | |
| | | | |
dht.is
|
|
| | | SOLVED posts detail solutions to problems I could not find anywhere else. After installing axe-cli in my Ubuntu/Windows 11 environment using Windows Subsystem for Linux (WSL), I got the following error whenever I tried to run it: Chrome failed to start: crashed (unknown error: DevToolsActivePort file doesn't exist) (The process started from chrome location [file path] is no longer running, so ChromeDriver is assuming that Chrome has crashed.) This can be caused by a lot of things (and I tried most of them), but in my case it was caused by Chrome not being installed in my WSL environment, which makes sense because I only use it for command line programs. | ||
