dvam
eric
Got it!!! And this is really unexpected. Not a bug coming from the code.
I did a test (for x times) to see the code doing exactly the same as you and nothing but:
The size of you terminal is too small and dialog is not able to display properly the horizontal button for the customize menu. Dialog can resize a vertical menu but not an horizontal one.
So increase the size of your terminal and your trouble should go away!
banned_9-26-2021
1 I have nearly 0 experience with efi, but does grub install at /mnt or the /boot partition?
2 If you run a shell or manually chroot into /mnt and use useradd xxx passwd xxx is there a problem? I can't imagine there would be.
3 At the last step, if you hit install again, and grub is already installed, what does it do? It returns back to main screen never asking for customizing/user/pw etc?
4 cat /mnt/etc/fstab has this been created, is this correct?
Yes the main question is why isn't the installer working for you, but also in the meantime between diagnosing and bug fixing you should have a functional system. Already you should be able to boot and login as root. But this is getting to be quite a puzzle.
banned_9-26-2021
eric wroteSo increase the size of your terminal and your trouble should go away!
unf^%^&*ing unbelievable :)
Maybe switch from sakura to lxterminal in the next edition, and have a lxterminal.conf of 120x28 :)
Sakura sucks, sorry for ever mentioning it.
eric
i switched to sakura on the ISO due of some trouble to launch dbus and terminator need dbus by default(it can be not necessary, it just an option to check in the terminator preferences). I don't like sakura (i use terminator, well not really from my discover of mtm-git. Really useful mostly on console and simple to use) but it appeared as a good choice regarding dependency.
Now , we don't have any trouble to launch dbus anymore and i should switch again on another terminal...
EDIT: i wrote a sentence about the size to use to run obarun-install at the wiki
dvam
BINGO!!! ... finally can confirm that at /sdc2 partition of my rig happily run latest Obarun ... thanks!
Maybe you should now consider to give me recommendation to 'zapatista autonomous intergalactic space program' as a Obarun Q/A contributor ...
P.S. Eric, please consider to dismiss latest obarun-install release from git because of ... FREEDOM ... this is LINUX !!!
banned_9-26-2021
Good job, both of yous :)
I tested and squeezed the installer to look like a "dumb"phone screen and it did weird things. When you choose 4 on the main screen it does nothing, it can't open the menu, the same at that last customization screen. Before mounting just by squeezing the screen to be narrow the installer exited, giving some errors about nothing on /mnt
I should have been the 1st to notice making huge fonts so I can sit back and watch the installation from far away (20cm :)
You want an autonomous intergalactic space program? You should construct your own. Any autonomy needs "ground control" .... what can you say about your ground? Is it on lease, rent, contract with the hydra?
dvam
... if you tease Linux ground ... on the Obarun boat until now, you simply don't perceive ... lease, rent, contract with the hydra ... lets hope Eric can hold this boat safe between Scylla and Charybdis ...
banned_9-26-2021
virtual autonomy, on intel or amd closed code hw, on a private network, who knows whose compiler, firmware, using someone's dns service, someone's search/db website finder, ...... and soon facebook's compression building an image of a system in Oracle's virtualization, utilizing intel/amd code to do so, .....
it is the best we can do for now, Obarun! ;)
eric
ok i pushed some change to reduce the size of the horizontal menu, i hope that will allow to avoid this kind of trouble if the user do not launch the installer in full screen mode
banned_9-26-2021
Is there any way that the initial window with instructions can contain an active check of the columns and rows and alert the users that they need at least ??110x25?? screen for the installer to operate properly? Once the menu is open it doesn't complain in shrinking but a new menu seems to refuse to open if the terminal is narrow ??>80??.
banned_9-26-2021
New bug :)
If you run the installer from your own system where you have set through /etc/X11/xorg.d/00-keyboard.conf 2 or more languages switched by a hot-key after the installer starts and you set the installation kbd the hot-key definition is lost, X must be restarted or the setxkbmap __ should be run everytime you want to switch.
I don't think there is a way around this or can be contained within the installer environment to not affect the rest of the system.
eric
Is there any way that the initial window with instructions can contain an active check of the columns and rows and alert the users that they need at least ??110x25?? screen for the installer to operate properly? Once the menu is open it doesn't complain in shrinking but a new menu seems to refuse to open if the terminal is narrow ??>80??.
Yes, it"s possible to check the size of the window with tput for example. I need to investigate it
I don't think there is a way around this or can be contained within the installer environment to not affect the rest of the system.
edit your etc/obarun/install.conf before starting the installer
# check the keyboard layout
KEYBOARDCHECK="no"
banned_9-26-2021
Is the dialog.conf replaced when you reinstall obarun-install or upgrade it? The one I have is the one by marianarlt, is this right?
This only affects color and frames, right?
eric
Is the dialog.conf replaced when you reinstall obarun-install or upgrade it?
yes
The one I have is the one by marianarlt, is this right?
i can't answer for you :)
This only affects color and frames, right?
yes
If you want to use your own, make a copy of /etc/obarun/dialog.conf where you want and change the following variable to suit your needs
# scheme color configuration file
SCHEMECOLOR="/etc/obarun/dialog.conf"
eric
Ok, if the size of the colums is less than 80 the script will warm you and exit.