crash when installing on used partition for old ubuntu version

Bug #2030513 reported by Jo
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I have ubuntu 21.04 crashed, so I downloaded ubuntu pro , but still not warking with the old partition I used

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity 22.04.19
ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-32-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
CasperVersion: 1.470.2
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 7 16:58:37 2023
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Jo (jofidele) wrote :
Revision history for this message
Paulo Flabiano Smorigo (pfsmorigo) wrote : Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Private Security → Public
Revision history for this message
Paul White (paulw2u) wrote :

From UbiquitySyslog.txt which was added to this bug report:

Aug 7 13:58:29 ubuntu kernel: [ 195.837983] SQUASHFS error: zlib decompression failed, data probably corrupt
Aug 7 13:58:29 ubuntu kernel: [ 195.837989] SQUASHFS error: Failed to read block 0x122f02: -5

It's possible you had a bad write to your installation media or for some other reason its contents could not be read correctly. If you've tried again and are still having problems you should try re-writing the image to your media (and may be re-download the image too).

Changed in ubiquity (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
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.