lubuntu noble - /usr/libexec/fixconkeys-part2 failed to finish in 30 seconds.

Bug #2060429 reported by Chris Guiver
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
calamares-settings-ubuntu (Ubuntu)
Fix Released
High
ԜаӀtеr Ⅼарсһуnѕkі

Bug Description

install to
- hp dc7700 (c2d-e6230, 7gb, amd/ati rv610/radeon hd2400 pro/xt)
testcase: install using existing partition

Command <i>/usr/libexec/fixconkeys-part2</i> failed to finish in 30 seconds.

(i clicked install at try/install & thus copy of error didn't survive gui start)

this was NOT a clean install (no format) BUT a 'install using existing partition'..
ie. boot & select the SDA1 as / partition without format...
install on that partition was a lubuntu noble install (with some music files & a few basic packages installs such as music player (audacious i think, or clementine)

---
2024-04-08 - 15:43:34 [1]: void Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
2024-04-08 - 15:43:34 [1]: ERROR: Installation failed: "External command failed to finish."
2024-04-08 - 15:43:34 [6]: .. - message: "External command failed to finish."
2024-04-08 - 15:43:34 [6]: .. - details: Command <i>/usr/libexec/fixconkeys-part2</i> failed to finish in 30 seconds.
There was no output from the command.
2024-04-08 - 15:43:34 [6]: void Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
---

install reported failure..

On reboot I can login and everything looks okay (will be passing QA test), BUT /var/log/installer/mediainfo shows 0320.1 ISO which was numerous installs ago & not today's ISO (last install failed, different issue but same type of install thus why numerous installs ago)

viewing / shows many directories date/timestamped matching a new (re-)install, however some system directories do NOT reflect a re-install; ie. calamares reached an error & stopped.... the system booted correctly, but that's no doubt because it was a functional Lubuntu noble system & it's using setup possibly from prior install...

ProblemType: BugDistroRelease: Ubuntu 24.04
Package: calamares 3.3.5-0ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
.etc.calamares.modules.after_bootloader_context.conf:
 ---
 dontChroot: false
 timeout: 120
 firmwareType:
     "*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
.etc.calamares.modules.finished.conf:
 ---
 restartNowMode: user-checked
 restartNowCommand: "systemctl -i reboot"
.etc.calamares.modules.fstab.conf:
 crypttabOptions: luks,keyscript=/bin/cat
 efiMountOptions: umask=0077
.etc.calamares.modules.shellprocess_logs.conf:
 ---
 dontChroot: true
 timeout: 30
 script:
     - calamares-logs-helper ${ROOT}
.etc.calamares.modules.unpackfs.conf:
 ---
 unpack:
     - source: "/cdrom/casper/filesystem.squashfs"
         sourcefs: "squashfs"
         destination: ""
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.495build1
CurrentDesktop: LXQt
Date: Mon Apr 8 15:57:10 2024
LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.3)
RelatedPackageVersions:
 calamares-settings-ubuntu-common 1:24.04.23
 calamares-settings-lubuntu 1:24.04.23
 xfsprogs 6.6.0-1ubuntu2
 btrfs-progs 6.6.3-1.1build2
SourcePackage: calamares
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Chris Guiver (guiverc) wrote :
description: updated
description: updated
Chris Guiver (guiverc)
description: updated
summary: - lubuntu noble install error
+ lubuntu noble - /usr/libexec/fixconkeys-part2 failed to finish in 30
+ seconds.
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/2060429

tags: added: iso-testing
Simon Quigley (tsimonq2)
Changed in calamares (Ubuntu):
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Simon Quigley (tsimonq2)
Revision history for this message
Chris Guiver (guiverc) wrote :

Just experienced this again..

Install to
- dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350)

this is a newer machine (2008) with faster cpu... alas still 'slow' by todays standards...

Revision history for this message
Chris Guiver (guiverc) wrote :

repeated install (using existing partition) to
- dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350)

again this issue....

The install abends (abnormal end) with error & thus doesn't continue/complete install...

/var/log/installer/mediainfo OR all contents in /var/log/installer reflect a prior install (many ago).. but this install type is successful .. after all it's a non-destructive install (no-format) so much data survives from pre-install (date/time stamps of system directories match new install though, as most system directories get wiped)

Simon Quigley (tsimonq2)
affects: calamares (Ubuntu) → calamares-settings-ubuntu (Ubuntu)
Revision history for this message
Aaron Rainbolt (arraybolt3) wrote :

How long does it usually take to generate an initramfs on that system? The timeout was bumped up to 300 seconds (5 minutes). It seems very strange that it would take *longer* than that to run loadkeys (fast), setupcon (fast), and update-initramfs (slow but grief, not *that* slow I wouldn't think).

Revision history for this message
Chris Guiver (guiverc) wrote :

As requested by Aaron (matrix) I ran a command on dc7700 & reported results... also booted & ran it on d780 (which I'm using now) and results are rather slow.

guiverc@d780-noble:~$ time sudo update-initramfs -c -k all
update-initramfs: Generating /boot/initrd.img-5.11.0-25-generic
update-initramfs: Generating /boot/initrd.img-5.11.0-27-generic
update-initramfs: Generating /boot/initrd.img-5.11.0-44-generic
update-initramfs: Generating /boot/initrd.img-5.13.0-28-generic
update-initramfs: Generating /boot/initrd.img-5.13.0-30-generic
update-initramfs: Generating /boot/initrd.img-5.15.0-41-generic
update-initramfs: Generating /boot/initrd.img-5.15.0-46-generic
update-initramfs: Generating /boot/initrd.img-5.4.0-72-generic
W: zstd compression (CONFIG_RD_ZSTD) not supported by kernel, using gzip
update-initramfs: Generating /boot/initrd.img-5.8.0-41-generic
W: zstd compression (CONFIG_RD_ZSTD) not supported by kernel, using gzip
update-initramfs: Generating /boot/initrd.img-5.8.0-50-generic
W: zstd compression (CONFIG_RD_ZSTD) not supported by kernel, using gzip
update-initramfs: Generating /boot/initrd.img-5.8.0-61-generic
W: zstd compression (CONFIG_RD_ZSTD) not supported by kernel, using gzip
update-initramfs: Generating /boot/initrd.img-5.8.0-64-generic
W: zstd compression (CONFIG_RD_ZSTD) not supported by kernel, using gzip
update-initramfs: Generating /boot/initrd.img-6.2.0-18-generic
update-initramfs: Generating /boot/initrd.img-6.2.0-19-generic
update-initramfs: Generating /boot/initrd.img-6.2.0-26-generic
update-initramfs: Generating /boot/initrd.img-6.2.0-33-generic
update-initramfs: Generating /boot/initrd.img-6.2.0-39-generic
update-initramfs: Generating /boot/initrd.img-6.5.0-9-generic
update-initramfs: Generating /boot/initrd.img-6.8.0-22-generic

real 7m6.659s
user 0m0.007s
sys 0m0.006s

Even though I initially filed this bug report on dc7700; the testcase is listed as an "INSTALL USING EXISTING PARTITION" which is a no-format install; meaning some old stuff can be found.. thus probably this issue..

The copy/paste of command is from a very recent install of noble on this box.

Revision history for this message
Chris Guiver (guiverc) wrote :

This bug is LOW PRIORITY in my view...

- not many people will use the INSTALL USING EXISTING PARTITION (non-destructive install)
- the error occurs which stops the installer, but most of what is required was already done, so system has booted for me each time I've encountered this error (even if some metadata will be invalid; system has been usable).

Changed in calamares-settings-ubuntu (Ubuntu):
status: Confirmed → Fix Committed
assignee: Simon Quigley (tsimonq2) → ԜаӀtеr Ⅼарсһуnѕkі (wxl)
milestone: none → ubuntu-24.04
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package calamares-settings-ubuntu - 1:24.04.37

---------------
calamares-settings-ubuntu (1:24.04.37) noble; urgency=medium

  * Correctly lengthen timeouts for network and initramfs package commands.
    (LP: #2060429)

 -- Aaron Rainbolt <email address hidden> Fri, 19 Apr 2024 18:52:09 -0500

Changed in calamares-settings-ubuntu (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.