install successful but crashed with CalledProcessError - subiquity 290

Bug #1960733 reported by corrado venturini
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
subiquity (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Try install from ISO Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220212)
ubuntu-desktop-installer 0+git.55a8a8c 2022-02-10 (290)
on my desktop
Machine:
  Type: Desktop Mobo: Gigabyte model: H87M-D3H v: x.x
    serial: <superuser required> UEFI: American Megatrends v: F3
    date: 04/24/2013
CPU:
  Info: dual core model: Intel Core i3-4130 bits: 64 type: MT MCP
    arch: Haswell rev: 3 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
  Speed (MHz): avg: 798 high: 799 min/max: 800/3400 cores: 1: 799 2: 798
    3: 799 4: 799 bogomips: 27138
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel 4th Generation Core Processor Family Integrated Graphics
    vendor: Gigabyte driver: i915 v: kernel bus-ID: 00:02.0
  Display: wayland server: X.Org 1.21.1.4 compositor: gnome-shell driver:
    loaded: i915 note: n/a (using device driver) resolution: 1680x1050~60Hz
  OpenGL: renderer: Mesa DRI Intel HD Graphics 4400 (HSW GT2)
    v: 4.5 Mesa 21.2.2 direct render: Yes

boot from USB key
select try Ubuntu
connect to internet wifi using hotspot on smartphone
changed keyboard from english to italian
started firefox and try gmail: OK
refresh ubuntu-desktop-installer --edge from 288 to 290
started installer from terminal
taken screenshot of all screens
the slideshow does not proceed after 1St slide
the last screen of the slideshow says:
something went wrong please restart...
a small window asking if sumbit error, reply yes but nothing happens
crash file created in /var/crash
open crash file with 'report a problem'
I see the windows about the problem (screenshots in Pictures.zip)
and the 1St says: install failed crashed with CalledProcessError
click on 'Send' to send problem to developers
I have a window saying:
Problem in subiquity
the problem cannot be reported
this problem report is damaged and cannot be processed
PermissionError(1,'operation not permitted')

restarting the system I have a working system so where is the error?

attached:
crash.zip from /var/crash
log.zip from /var/log
Pictures.zip with screeshots taken

Revision history for this message
corrado venturini (corradoventu) wrote :
Revision history for this message
corrado venturini (corradoventu) wrote :

attaching log.zip

Revision history for this message
corrado venturini (corradoventu) wrote :

attaching Pictures.zip with screenshot of the install windows and of the bug

Revision history for this message
corrado venturini (corradoventu) wrote :

From /log/curtin/install.log install seems ok (and is ok because the generated system works fine)
finish: cmd-install/stage-curthooks/builtin/cmd-curthooks/install-grub: SUCCESS: installing grub to target devices
finish: cmd-install/stage-curthooks/builtin/cmd-curthooks/configuring-bootloader: SUCCESS: configuring target system bootloader
finish: cmd-install/stage-curthooks/builtin/cmd-curthooks: SUCCESS: curtin command curthooks
start: cmd-install/stage-hook/builtin/cmd-hook: curtin command hook
Finalizing /target
finish: cmd-install/stage-hook/builtin/cmd-hook: SUCCESS: curtin command hook
curtin: Installation finished.

but from terminal output i see an error:
flutter: INFO subiquity_client: state: POST_RUNNING => UU_RUNNING
flutter: DEBUG subiquity_client: GET http://localhost/meta/status?cur=%22UU_RUNNING%22
flutter: DEBUG subiquity_client: ==> status("UU_RUNNING") {"state": "ERROR", "confirming_tty": "/dev/tty1", "error": {"state": "INCOMPLETE", "base": "1644671289.296469450.install...
flutter: INFO subiquity_client: state: UU_RUNNING => ERROR

summary: - install crashed with CalledProcessError - subiquity 290
+ install successful but crashed with CalledProcessError - subiquity 290
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in subiquity (Ubuntu):
status: New → Confirmed
Revision history for this message
Dan Bungert (dbungert) wrote :

The error in this case was during unattended-upgrades. I suppose that doesn't need to be a fatal error - unattended upgrades is one of the last steps and the system is, as noted, otherwise fine.
So that explains why the system was usable, but not why unattended-upgrades failed.

Changed in subiquity (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.