lubuntu jammy install; failure re-using existing partition
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
calamares (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
lubuntu re-install (jammy daily) on
- hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
system directories were mostly erased (all binary directories anyway).
i think the sources included packages.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: calamares 3.2.61-0ubuntu0.1
ProcVersionSign
Uname: Linux 6.2.0-32-generic x86_64
.etc.calamares.
---
restartNowMode: user-checked
restartNowCommand: "systemctl -i reboot"
.etc.calamares.
---
dontChroot: true
timeout: 30
script:
- calamares-
.etc.calamares.
---
unpack:
- source: "/cdrom/
sourcefs: "squashfs"
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckR
CasperVersion: 1.470.3
CurrentDesktop: LXQt
Date: Thu Aug 31 13:33:15 2023
LiveMediaBuild: Lubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230830)
RelatedPackageV
calamares-
calamares-
xfsprogs 5.13.0-1ubuntu2
btrfs-progs 5.16.2-1
SourcePackage: calamares
UpgradeStatus: No upgrade log present (probably fresh install)
Err:6 https:/ /packages. element. io/debian default InRelease /packages. element. io/debian default InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C2850B265AC085BD /packages. element. io/debian default InRelease' is not signed. :ViewManager: :onInstallation Failed( const QString&, const QString&) :doNotify( bool, bool) :doRestart( bool)
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C2850B265AC085BD
...
W: GPG error: https:/
E: The repository 'https:/
2023-08-31 - 13:30:02 [6]: void Calamares:
Calamares will quit when the dialog closes.
2023-08-31 - 13:30:02 [6]: void Config:
Notification not sent; completion: failed
2023-08-31 - 13:33:08 [6]: void Config:
mode= "never" user wants restart? false force restart? false
If that's the only issue here... that is NOT a problem as user mistake... (I didn't comment or remove the 3rd party resource!)