Startup Error on new install
Posted: Wed Aug 02, 2023 9:24 am
Hi, Tim. I have just reclaimed an old laptop that was running intolerably slow under Windows 10, a Lenovo G580 with 4 GB RAM. It was so slow that it was impossible to work on it. After taking many hours to back up all relevant photos, audio, personal files, etc., I installed Linux Lite v6.4, reclaiming the entire hard disk. I have heard it recommended for older, under-powered hardware, so I thought I'd give it a try. Linux Lite is based on Ubuntu 22.02.2 software base and uses the XFCE desktop environment.
The startup worked without any visible errors. I notice that an icon shortcut for Bible Analyzer did not appear anywhere in my start menu, not even under "All Applications". If it weren't for my past experience with BA and knowing that I should look under /opt/bibleanalyzer/ to execute "ba-run.py", I would have been in trouble. The shortcut did start Bible Analyzer.
As soon as it started, I saw the attached error: You see that it is looking for a variable called "editor", which does not exist. Unless I click the blue OK button, BA will not run. But I could not see the error message or the button, because the welcome screen was hiding it.
In a Linux environment, if the default editor should be vim or vi. I can see that this appears to be a JavaScript variable, not and environment variable. Can you look into these two issues? Thanks much for all you do.
One reminder: In Unix/Linux, the EDITOR variable, if it exists, will be in upper-case; environment variable names are case-sensitive; and there is no assurance that this particular variable ought to exist. The EDITOR or VISUAL variables can be defined to serve the console utilities more and less, but they are often undefined.
The startup worked without any visible errors. I notice that an icon shortcut for Bible Analyzer did not appear anywhere in my start menu, not even under "All Applications". If it weren't for my past experience with BA and knowing that I should look under /opt/bibleanalyzer/ to execute "ba-run.py", I would have been in trouble. The shortcut did start Bible Analyzer.
As soon as it started, I saw the attached error: You see that it is looking for a variable called "editor", which does not exist. Unless I click the blue OK button, BA will not run. But I could not see the error message or the button, because the welcome screen was hiding it.
In a Linux environment, if the default editor should be vim or vi. I can see that this appears to be a JavaScript variable, not and environment variable. Can you look into these two issues? Thanks much for all you do.
One reminder: In Unix/Linux, the EDITOR variable, if it exists, will be in upper-case; environment variable names are case-sensitive; and there is no assurance that this particular variable ought to exist. The EDITOR or VISUAL variables can be defined to serve the console utilities more and less, but they are often undefined.