well great, i got the gui to compile in the new VM but its not usable

the rotating globe screen is flashing and i can't click on the buttons

this is ubuntu 18 in a VM on a win10 host

ok, seemd to have fixed it.

for some reason the mouse integration in virtualbox is fuct right now. if i turn it off it works fine

so you can't change the wallet type settings after creating a wallet huh

and im getting all sorts of red errors no connection to daemon

but there's no way to tell what the daemon is doing in this simple mode.

it says daemon is syncronized. i did simple with bootstrap

i guess it picked a random remote node from dsc_'s server?

and now im trying to close the wallet to stop this thing from syncing

and i got closing wallet spinny circle of fun

ginger is spiraling out of control

hopefully he was able to pull out of it

"i guess it picked a random remote node from dsc_'s server?" -> nope

it is using automatic public node discovery

so it is picking a random node running in --public-node mode

gingeropolous: ^

05:19 <gingeropolous> so you can't change the wallet type settings after creating a wallet huh <-- you can change it

selsta, do you mean i have to restore from seed? or is there an easier way?

gingeropolous: close the wallet (not gui) and you'll see change wallet mode button

ah ok. dunno why i couldn't see that last night. those orange buttons look like navigation buttons, not option buttons perhaps

ok, so you can use auto when doing a bootstrap, but when using a remote node, you have to enter one manually?

or use local node with --bootstrap-daemon-address auto

or use simple mode

or use simple mode (bootstrap)

"or use local node with --bootstrap-daemon-address auto" -> even better

use local node and just set "Bootstrap Address" to "auto"

in the gui

yeah.

i wonder if there's a way to speed up daemon initialization

what do you mean exactly?

i get that "waiting for daemon to start" spinny circle and its just frustrating

that might require modifying monerod itself, because the daemon *does* take a while to load

exactly

heh. well, when you change mode after starting a daemon, there's no way to stop the daemon less you go back to the advanced mode eh

Could you provide the steps you did?

i think i started a wallet in simple-bootstrap mode. then closed it. then re-opened it in simple mode

without stopping the daemon

cause i guess there's no way to control the daemon in simple mode

even with the bootstrap option

which i guess could be fine

GUI controls it automatically

well, not if you close the wallet and decide you want simple mode with no bootstrap

it apparently keeps the daemon running

even though the user wanted no more bootstrap

" it apparently keeps the daemon running" -> nope

it restarts the daemon with appropriate flags

ah thats why i see long periods of spinny circles of death

huh. the daemon restarted like 3 times during that last thing i did

which was just switch from bootstrap mode to simple mode

great, works as expected

its gotta restart 3 times?

it might restart more if there is a connection issue or the daemon fails to discover any public remote node

in the typical case there wil be just one restart

i also have the daemon spitting out stacktrace nonsense. thats prolly more on my end