I don’t love you any more.
Ah, are you seeing it launch terminals repeatedly? Maybe it’s getting stuck in some sort of loop there. I’m not sure exactly how it works because Josh and Roland took over from me after Monday and the launcher binary was abandoned. Basically just the Linux part of the launcher went into the TUI, so that it could work on Linux, which doesn’t have the same behaviour as macOS/Windows, in terms of launching a terminal instance for a command line binary.
I will always love you @southside when I get my 8 Gbit internet within 2 weeks, whatever you want downloaded/upload to the Network just let me know.
P.s. dear sir, I will always be your student and still got a lot to learn. I admire the kids who write scripts and experiment away to give a glimpse @ the Network. Talking will soon be over and coding and creating apps will be the only…
The entire archive of https://wingsoverscotland.com/ for starters please
I should get proper fibre here myself by the end of the month - hopefully
Are you on an upgrade list too? I’m on one with TalkTalk. I was supposed to get it in March, but they delayed it until June.
I’m going to try it on my own native machine shortly.
Edit: on my own machine I’m not seeing any strange behaviour with lots of terminals being launched. However, I’m on Arch, with alacritty
as the terminal.
This is what I see
wait for it, wait for it
I have a 3 monitor setup - if I move the mouse to another screen, I get a wheen of these terminal windows popping up there as well…
Ah, but you already had an instance running.
Edit: doesn’t seem to make a difference for me if one instance was already running.
Try this - from clicking on the binary in target/release
A couple of things…
- What is your
TERM
variable set to? - Can you try installing
alacritty
?
Just want to try and determine if it’s specific to gnome-terminal
.
willie@gagarin:/var/log$ echo $TERM
xterm-256color
TBH this is the first I have heard ofg alacrity Arch Linux is 99.9% unknown to me.
willie@gagarin:/var/log$ sudo apt install alacrity
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package alacrity
Curses!!! Now I have to DuckDuckGo…
It would help if I could spell alacritty though…
here we go
Yeah, the other terminal is just a test to see whether it was something specific to gnome-terminal
.
Reading TERM
is part of the launching process, but I think that should probably be ditched.
I cargo installed alacritty
Watch the screencast carefully - it looks to me that it starts as expected in alacritty but subsequent instances use use the Ubuntu/Gnome terminal
You don’t need to keep it–it’s just a test.
Note how I get “one for free” at start up …
yes I added the folder it in to path in environmental settings.
I also made a small .bat file to confirm that the folder was in path.
also tried it in path for user and then added to path system wide.
so im out of ideas
I’m not sure exactly what is going on. I think somehow it would need to take into account whether it’s already launched from a terminal session.
I get a lot of build errors.
error[E0658]: use of unstable library feature 'stdsimd'
--> /home/user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/curve25519-dalek-4.1.2/src/backend/vector/ifma/field.rs:26:5
|
26 | _mm256_madd52lo_epu64(z.into(), x.into(), y.into()).into()
| ^^^^^^^^^^^^^^^^^^^^^
|
= note: see issue #48556 <https://github.com/rust-lang/rust/issues/48556> for more information
= help: add `#![feature(stdsimd)]` to the crate attributes to enable
error[E0658]: use of unstable library feature 'stdsimd'
--> /home/user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/curve25519-dalek-4.1.2/src/backend/vector/ifma/field.rs:25:9
|
25 | use core::arch::x86_64::_mm256_madd52lo_epu64;
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: see issue #48556 <https://github.com/rust-lang/rust/issues/48556> for more information
= help: add `#![feature(stdsimd)]` to the crate attributes to enable
error[E0658]: use of unstable library feature 'stdsimd'
--> /home/user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/curve25519-dalek-4.1.2/src/backend/vector/ifma/field.rs:34:5
|
34 | _mm256_madd52hi_epu64(z.into(), x.into(), y.into()).into()
| ^^^^^^^^^^^^^^^^^^^^^
|
= note: see issue #48556 <https://github.com/rust-lang/rust/issues/48556> for more information
= help: add `#![feature(stdsimd)]` to the crate attributes to enable
error[E0658]: use of unstable library feature 'stdsimd'
--> /home/user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/curve25519-dalek-4.1.2/src/backend/vector/ifma/field.rs:33:9
|
33 | use core::arch::x86_64::_mm256_madd52hi_epu64;
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: see issue #48556 <https://github.com/rust-lang/rust/issues/48556> for more information
= help: add `#![feature(stdsimd)]` to the crate attributes to enable
error[E0635]: unknown feature `stdarch_x86_avx512`
--> /home/user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/curve25519-dalek-4.1.2/src/lib.rs:19:13
|
19 | feature(stdarch_x86_avx512)
| ^^^^^^^^^^^^^^^^^^
Some errors have detailed explanations: E0635, E0658.
For more information about an error, try `rustc --explain E0635`.
error: could not compile `curve25519-dalek` (lib) due to 5 previous errors
Launching from the command line I get this
one full-screen instance of the app in Gnome/Ubuntu and a password request in alacritty — buut the command line was simply
willie@gagarin:~/projects/maidsafe/safe_network$ target/release/node-launchpad
no mention of alacritty…
This time its as before but - I get one instance of the app in alacritty and then the multiple spawning of Gnome/Ubuntu instances.
Good news is I can click on the ‘x’ in the alacritty app and kill the child Ubuntu/Gnome instances.
Then Q in the remaining original Gnome/Ubuntu window will close it as expected . Non of the other commands do anything - but I didnt really expect them to anyway.
@MaxSan do you have the pre-reqs? What OS/distro are you using?
For Deb/Ubuntu
apt install cmake pkg-config libfreetype6-dev libfontconfig1-dev libxcb-xfixes0-dev libxkbcommon-dev python3
Did you check you are using stable?
rustup override set stable
rustup update stable