go - liteide setting GOROOT to GOPATH when run -

in middle of development session, stupid behavior started , looks permanent. have no idea happened:

[dtrombley@sleet bin]$ echo $goroot /usr/lib/golang [dtrombley@sleet bin]$ echo $gopath /home/dtrombley/go/ [dtrombley@sleet bin]$ ./liteide 

liteide build error:

 ../../github.com/sirupsen/logrus/writer.go:4:2: cannot find package "bufio" in of: /home/dtrombley/go/src/bufio (from $goroot) /home/dtrombley/go/src/bufio (from $gopath) 

what? why using gopath in place of goroot? used work, , mysteriously switched broken while liteide running, 1 build next, literally few seconds later...

has seen this? there way can inspect/set goroot within liteide?

[edit] further weirdness: thought / @ end of gopath might confusing it, removed that. now:

 [dtrombley@sleet bin]$ echo $goroot  /usr/lib/golang  [dtrombley@sleet bin]$ echo $gopath  /home/dtrombley/go  [dtrombley@sleet bin]$ ./liteide 

...

warning: gopath set goroot (/home/dtrombley/go) has no effect ../../github.com/sirupsen/logrus/writer.go:4:2: cannot find package "bufio" in of: /home/dtrombley/go/src/bufio (from $goroot) ($gopath not set) 

misery.

you can check if goroot set @ in /usr/share/liteide/liteenv/linux*.env (which can issue reported in here)
can check if goroot set in other place well.

finally check if issue persists latest liteide (x27.2.1).

---

the op badzen confirms in comments:

it switched in middle of session because must have stray clicked , switched target linux64 linux32 - linux32.env had buggy goroot entry (goroot=$home/go).