sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)
I cannot select a keyboard layout. I have none to choose from? I can use the “Detect Keyboard Layout”; but other than that my go back.
System problem keeps popping up; still opening the text editor, with close button exists on installer…
On exiting & restarting the installer I do get a list of keyboard layouts this time? so I can accept English(US).
I’ll reboot & try this again… (I wonder if I accidentally touched the wrong language at first screen; I tend to use this device for screen QA-test & can mis-touch with my fat fingers).
On restarting system; starting the installer I get the English(US) option offered. No system problem detected so far this boot, and install is progressing - so better this time.
this progressed and crash
on restart of system, it fails to boot (vaio failed to start & offer to boot recovery or BIOS setup)
The error at the end of the installation is probably the one being worked on there, it fails to install some deb packages probably because the system was offline and those are currently missing from the ISO
I may have started the installer BEFORE connection was made; (I’d entered key & it was connecting as I clicked installer icon; not waiting…) so could it have detected no wifi & set a flag to say no internet during installer setup? I did the CtrlAltT & ping of my ISP prior to selecting fields (ie. language, keyboard etc) in installer; so can’t confirm wifi was connected when I clicked start installer.
Thanks, let’s see what the subiquity maintainer say, reading the log the apt source don’t have an online mirror enabled and it ends up failing the same way as during offline installation because of missing deb packages
Updated my canary ISO, wrote to thumb-drive & tried to install on
sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)
boot ISO, connect wifi (hidden wpa2, 5ghz)
ctrl+alt+T to open term & ping ISP, 3 replies so ^C
start installer, go through process…
after entering the user data (me, sysname, password)
I instantly get a "install completed, reboot to use your 22.04.
This was instant install… way too quick in my opinion. I accepted the green message & installer exited
I expected box to reboot; it didn’t… so I restarted installer.
On re-starting installer; it’s at the first Keyboard layout screen again, with NO options available; just “Detect Keyboard Layout” and “Go Back”.
system problem detected - same as last time I gather
likely obvious; but failure to boot system on restart
Refreshed the daily (canary) build for QA-test install on
hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
daily: 2021-11-03 jammy
this box had internet connected (ethernet) & ping to ISP was good.
installer started, no issues for full disk install, I progressed thru till I entered my user details (password etc) & the installer just closed up after that without message. No errors reported.
I don’t know where subiquity logs are stored; the details in /var/crash/ were from a system problem detected (_usr_bin_cloud-init) that appeared at boot time.
fyi: clicking the install icon just re-started the installer…
Refreshed the daily (canary) build for QA-test install on
sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)
daily: 2021-11-04 jammy
I saw fix released on 1949424 so didn’t connect to wifi/internet… and started installer
accepted default ‘english’ & no keyboard layout options exists… just detect keyboard layout or go-back are offered again.
(I see crash files in /var/crash for cloud-init & server-request_fall … but not submitted yet as no internet; as was planning this to be a no-internet install)
exiting installer & starting it again & second time I have keyboard layout options to choose from
Thanks for the testing you are doing. I don’t think the image is changing enough at the moment that it’s worth doing daily testing.
You asked about the log, they are in /var/log/installer for the desktop installer and subiquity and /var/log/curtin for that component
The recent journal log you shared showed an installer hitting a crash in the nouveau video driver which could be workarounded by forcing software rendering, there is WIP work around this on https://github.com/canonical/ubuntu-desktop-installer/pull/286
I hadn’t looked close enough had I… I now see it, so thanks.
I like the tracker as for occasional issues like the keyboard layout not showing; it allows a quick view of when & how often from lp… & I can just tag it on iso.qa & ignore (as not new & known)
Thanks for clue about testing frequency… I currently aren’t worried about Lubuntu’s ISO either… so when I have time currently it’s canary.
I already tested the new installer a few days ago, now to test the new installer, just refresh the snap or must the new ISO canary be reloaded? Thanks.
It’s better to get the current ISO, if most of the work is on the installer snap some fixes like the one for offline installation are on the ISO itself
Try install on existing partition on my disk sda1 where now I have Ubuntu Focal.
The /boot/efi partition is on a different disk /dev/nvmen1p1
Ubuntu 22.04 LTS “Jammy Jellyfish” - Alpha amd64 (20211108)
latest/edge: 0+git.a71b808 2021-11-05 (145) 117MB classic
Here some problems I noted:
Screen Updates and other software:
can select Normal or Minimal install but ‘Other options’ is missing, no choice for ‘Download updates while install’ and ‘Install third-party software’
Screen Installation type:
says: the computer currently has no detected operating systems… while I have 4 different Ubuntu installations on other partitions and if I select ‘Something else’ the partitions are displayed but content not shown.
Screen Allocate disk space:
can not select ‘format partition’ but is automatically selected
… and i want keep my home?
device for boot is not automatically selected
Screen Write changes to disk: partitions to be formatted are not listed
… I abandoned the install
I would really love to test the new installer but the disk image is over 4 Gs and I don’t think that’s acceptable. I don’t have a larger USB stick at the moment and I think I’m not in the minority when I say that nobody would want to use their main drives just to install an OS. It’s not common to have an 8 and 16 GB USB flash drive lying around. Imagine if I had two of them: one 4 G, the other 8 G with some data on it. That means I would have to back it up and format it just because the image was a bit over 4 G? Utter nonsense.
The canary ISO Ubuntu 22.04 LTS “Jammy Jellyfish” - Alpha amd64 (20211108) is just 3.7 GB, I used a 4GB stick to install. More: if you try the install in virtual box you can try directly from the ISO downloaded on your disk.
Previously I’ve provided details in this thread (alas I’m usually not brief so better hidden away on iso.qa)
Is this normal? expected? Why can’t i record test on iso.qa?
Reporting: No testcase available
(errors in cloud-init [going by /var/crash/] had me login & report issue, but on logging into lp I only get “Bad bot, go away! Request aborted.” message)
Install attempt (full disk) failed on
hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
and multiple attempts (clean boot each time) failed to install on
sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)
