17.10 beta installer crash

Bug #1716543 reported by rallen71366
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Crashed as I was trying to use the on-screen keyboard to type in random letters and numbers of the wifi password, because I couldn't select DVORAK keyboard layout yet.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubiquity 17.10.4
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.6-0ubuntu7
Architecture: amd64
CasperVersion: 1.384
Date: Mon Sep 11 19:35:22 2017
InstallCmdLine: file=/cdrom/preseed/ubuntu-mate.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
LiveMediaBuild: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 (20170829.1)
ProcEnviron:
 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
rallen71366 (rallen71366-gmail) wrote :
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thanks for your report.

I cannot reproduce your issue. If you can, can you please provide all the steps to do it.
Besides I noticed the following error message in yor log files:
Sep 12 00:34:50 ubuntu-mate kernel: [ 975.913476] SQUASHFS error: zlib decompression failed, data probably corrupt
Sep 12 00:34:50 ubuntu-mate kernel: [ 975.913486] SQUASHFS error: squashfs_read_data failed to read block 0x711a8b0
Sep 12 00:34:50 ubuntu-mate kernel: [ 975.915603] SQUASHFS error: zlib decompression failed, data probably corrupt
Sep 12 00:34:50 ubuntu-mate kernel: [ 975.915607] SQUASHFS error: squashfs_read_data failed to read block 0x711a8b0

Which suggest that the installation media is corrupted and is more likely te cause of the failure you observed.

Changed in ubiquity (Ubuntu):
status: New → Incomplete
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

I'm closing this report due to the lack of information.

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