It does seem to make a difference hw this is started
Clicking on the binary in target/release immediately pops up the password request
But if I start from the terminal I get an immediate instance and then the password request on top of it
So yes it DOES need a check on how it is launched.
Yep! think it was on nightly build or something. Works now anyway. Cheers.
Same repeating thing here too.
Same thing happens to me, Mint 21.1, gnome terminal or xterm
start with ./node-launchpad or click on the executable. Just after entering my password:
Lucky escape for @happybeing there 
I was planning to try out on mint after the stages but think ill give it a swerve for now.
Yeah, after the initial thrill of crashing your machine it’s not that entertaining
I have complete confidence that this inadvertent looping will get fixed very soon and we can get down to properly evaluating this tool over the next couple of days.
You’re a saint for doing that multiple times for the video. I also would have launched it from the terminal. Especially if it’s something I compiled and knew I’d be in the terminal anyway.
It does actually work though, by hammering ‘a’ as the windows flash up, it is possible to start nodes -and presumably manage them
Its just that if you dont stop it fast, the only option is to kill the original window, or its a reboot 
So we will soon have a new toy to play with once the looping gets sorted.
It opened one per service?!? That is a bug I haven’t seen before there.
@happybeing looks like the linux terminal start setup is off there.
I think the current sudo requirement might be causing a bunch of issues as it reuqires some jiggerypokery .
I think it may well still end up there.
VM. It shouldn’t matter though really. The main issue is likely how different terminals are launching.
HMmm, i bet I know what’s going on here w/r/t looping. Gimme a mo.
@Southside or @JPL can you try from this branch
I renamed my original safe_network folder and cloned that branch, but got this
willie@gagarin:~/projects/maidsafe$ cd safe_network
willie@gagarin:~/projects/maidsafe/safe_network$ cargo build --bin node-launchpad --release
Updating crates.io index
Downloaded dashmap v5.5.3
Downloaded socket2 v0.5.7
Downloaded serde_derive v1.0.201
Downloaded serde v1.0.201
Downloaded quinn-udp v0.3.2
Downloaded quinn v0.9.4
Downloaded serde_json v1.0.117
Downloaded quinn-proto v0.9.6
Downloaded rcgen v0.9.3
Downloaded qp2p v0.36.4
Downloaded 10 crates (678.5 KB) in 15.86s
error: no bin target named `node-launchpad`.
Available bin targets:
stableset_net
Whats the correct git command to build your branch, please?
I suspect you didn’t check out the specific branch from my repo (what commit were you on?)? Not sure, but i just pushed the code to main on my repo, so if you pull and try again on main that should be it.
Sorry but main appears to be a few hours old, is Github slow to update
Im doing something dumb here, I know
Whats the correct way to handle this
willie@gagarin:~$ git clone https://github.com/joshuef/safe_network.git
Cloning into 'safe_network'...
remote: Enumerating objects: 47911, done.
remote: Counting objects: 100% (3446/3446), done.
remote: Compressing objects: 100% (1184/1184), done.
remote: Total 47911 (delta 2407), reused 3076 (delta 2221), pack-reused 44465
Receiving objects: 100% (47911/47911), 28.78 MiB | 2.26 MiB/s, done.
Resolving deltas: 100% (34846/34846), done.
willie@gagarin:~$ cargo build --bin node-launchpad --release
error: could not find `Cargo.toml` in `/home/willie` or any parent directory
willie@gagarin:~$ cd safe_network/
willie@gagarin:~/safe_network$ cargo build --bin node-launchpad --release
Updating crates.io index
error: no bin target named `node-launchpad`.
Available bin targets:
stableset_net
Sorry for needing spoon-fed.
No worries at all. I think you’re missing cd ing into the dir, as well as a branch change.
git clone https://github.com/joshuef/safe_network.git
cd safe_network
git fetch
git checkout FixSudoLauncher
cargo build --bin node-launchpad --release
Yeah I had a brain fart about the branch change - seems to be working now
My screenshots are taking ages to upload so you’ll just have to trust me
Thank you.
as in the looping is sorted? Just one terminal window?
yep just the one and I can add nodes - unsure about starting them yet
more later
Brilliant, i’ll get this merged into main. Thanks, as ever, for all the testing! 
edit: It’s in main now, so new folk coming should not face this issue now!
Thanks as ever for giving us stuff to test
And sorting it so quickly when we find a problem