[Bug 1969376] Re: Installer of Ubuntu 22.04 beta crashes - mutiple bugs

Tue Apr 19 10:29:15 UTC 2022

After my bug report was put in status invalid (i.e. SPAM) I responded politely (and asked
to read this bug report carefully) - which seems to be deleted (censorship? all the calls
I have seen in my life had all deatails by customers in it) - and I was informed via mail:
~~
Thank you for your bug report. To maintain a respectful atmosphere,
please follow the code of conduct - http://www.ubuntu.com/project/about-
ubuntu/conduct. Bug reports are handled by humans, the majority of whom
are volunteers, so please bear this in mind.
~~
I gave a correct bug report and this is all about the installer of the image.
It is interesting that problems in one component - the installer - should be divided into
several bug report - was not the case for IBM, HP, Sun or Red Hat when working in IT business.
And it is insulting when pointing me to 'Reporting Bugs' hints - this is not my first - but
maybe my last one.
As nobody seems to be interested in improving the flagship Ubuntu/Canonical product 22.04 LTS which
is due 21. April ... and it seems that nobody tested it.

Errors still remain (boot image Kubuntu 20.04 LTS beta 18.04.2020):
1) I actually managed to install it - by selecting the / partition (i.e. /dev/sdb5) as boot loader -
   never did this before. The warning was the same as when I just used the default /dev/sda which
   I used a very long time - and now making the installer crash without info or debug data.
   Even if this may be caused by grub, the installer does a really bad job to point out problems.
   A feature request would be to have next to the device for boot loader a point saying "not
   configuring for booting now" or "no booting" in manual, as professional installation will
   not use the youngest OS playing grub master.
2) Keyboard layout does not show all keys - not even using variant setting at all - no longer
   providing a line to type ... this is a big regression!
3) On install type and in manual mode only the first few partitions are given.
   This is a big regression as one must know where to install and could not even check.
   With 20.10 STS and before all partitions were shown correctly.
0) Installing starts with "from this CD - while the image is more than 4 GB. Really?
   At least at the end it was asked to remove the install medium.
-) Only tested with 21.04 STS - but may still be present as nothing was fixed since then -
   no signal on Display Port while also HDMI is present (switched of but powered TV).

So if it was not about switching the installer, why was the installer ruined in so
many ways since 21.04 STS? And why was not one of these 3 points fixed in 1,5 years time?
Maybe it could have to do something with the non-technical tone when reporting bugs.
I could no longer recommend people opening bugs for Ubuntu ... this was not the 1st
experience my help was unwanted and insulting is the only tone one could get.
And a bug report about the installer should be checked by paid Canonical people - not
by 'volunteers' (whatever this may mean).

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to subiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1969376

Title:
  Installer of Ubuntu 22.04 beta crashes - mutiple bugs

Status in subiquity package in Ubuntu:
  Invalid

Bug description:

  * Main error: subiquity crashes without giving any reason or data.    ** BUG1 **
  subiquity is the current desktop installer since 21.04 STS, right?

  What I did:
  I try to install fresh Kubuntu 22.04 and downloaded the fresh installer image dated 18.04.2022
  and put it in an USB stick.
  My system has 2 disks: 2 TB SSD with 9 partitions and 8 TB HDD with 13 partitions.
  My OS partitions have 128 GB size each - so I use manual disk mode to select the partition (sdb5),
  let format with ext4 and  mounted to /, efi and swap seems to be recognized, while efi written
  in partition overview but not mentioned. In former times I could specify sdb2 as /boot/efi -
  but this is no longer possible (or I don't get it) - as I don't want it to be formatted.
  I would like GRUB to be installed, but not configured. But if configured would be still ok.
  May be a reasonable option with the manual partitioning selection. ** FEATURE REQUEST **
  When asked about boot loader I use /dev/sda - should not harm even if wrong - but I think
  one may use efi partition here? Which is no longer selectable from the partition table ...
  When everything is given, the installer crashes - no data.

  All choices I do make when installing (may cause something I am not aware of):
  English as language, German keyboard with layout German (no dead keys),
  normal installation, download updates while installing, install 3rd party SW,
  Disk setup: manual, selecting sdb5 to create ext4 FS and mount as /, was not able
  to mark sdb2 as /boot/grub - but it was recognized as EFI (my system has 2 EFI partitions,
  one on each disk), Boot Loader was left as /dev/sda which creates a warning (but nothing
  about a real problem - only that it may not boot - but I would do it with GRUB master
  manually anyway - so if THIS CAUSES THE CRASH - then the message is misleadingly wrong!).
  So only GRUB configuring may fail - which should in no way cause an installer to crash
  (at least I hope so!), and German time (in former installers this was called Berlin time ...
   little bit strange that this was changed without reason). 
  My HW: Silent Workstation, Ryzen 5 3600 [Zen2], Radeon RX 5700 XT [Navi10/RDNA1], 4k 31.5" BenQ.

  * Other errors/regressions I encountered:

  1) ** BUG2 **
     When selecting keyboard and layout (for me German/no dead keys), one could formerly test it
     by typing. I think that this is important and missing it is a regression.
     But what is really a shame that with no dead keys the given layout is just wrong,
     as the "ALTGR" combinations are missing, e.g. "*/+/~" on one key with "~" just missing ...
     not an unimportant character, is it?
     All 3 versions with subiquity has just a reduced layout for keyboard.
     Does Canonical really want such a regression in the flagship version???

  2) ** BUG3 **
     Using a 4k 31.5" screen I could not see the partition table graphically.
     This worked with the old installer like a charm - now I see only a few partitions,
     not even all sda and of cause nothing of sdb which I have to use.
     I know what I am doing - but still it is a warm feeling to check that I format an
     OLD Ubuntu xv partition no longer in use then just typing in blind!

  3) ** BUG4 **
     When trying to install 21.04 I first had my normal configuration - 4k screen on DP and
     4k TV on HDMI (powered but off - still visible for GNU/Linux) - and I was not presented
     anything.
     After disconnecting HDMI I saw the installer - I hope, this bug has been fixed - not tested
     this again.
     HDMI is a toy and DP is the professional interface ... so I would prefer the same image,
     but if only one port is selected, it should clearly be DP which is to be preferred.

  Background:
  I am an experienced Unix consulant using GNU/Linux since 1994 and Ubuntu right from the start.
  I tried installing Kubuntu 21.04 STS and 21.10 STS - all without success.
  The last success was with 20.10 Groovy - and of cause KDE neon (Focal/20.04 LTS based) before.
  But now the LTS version seems to have this problem, too.
  If I could try something, please send some info and I will come back with my findings.

  Best wishes,
  JMB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1969376/+subscriptions