Your message dated Sat, 8 Feb 2020 03:10:28 +0000 (UTC)
with message-id <1653395131.47366.1581131428...@mail.yahoo.com>
and subject line Re: Bug#947744: installation-reports: Debian Live Testing LXQt
+ nonfree - install fails with: "Bad unsquash configuration" Date: Wed, 1 Jan
2020 04:54:06 +0000 (UTC)
has caused the Debian Bug report #947744,
regarding installation-reports: Debian Live Testing LXQt + nonfree - install
fails with: "Bad unsquash configuration"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
947744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947744
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: grave
Justification: renders package unusable
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Scott Jacobs <scott092...@aol.com>
To: Debian Bug Tracking System <sub...@bugs.debian.org>
Subject: installation-reports: Debian Live Testing LXQt + nonfree - install
fails with: "Bad unsquash configuration"
Bcc: Scott Jacobs <scott092...@aol.com>
Message-ID:
<157765450239.2521.4290165524983598064.reportbug@ASUS-PRIME-B350M-A-CSM>
X-Mailer: reportbug 7.5.3
Date: Sun, 29 Dec 2019 16:21:42 -0500
X-Debbugs-Cc: scott092...@aol.com
Dear Maintainer,
Twice, I tried to install the Debian Testing Live LXQt + nonfree .iso, with the
Calamares installer, and twice received the error window with:
"Installation Failed
Bad unsquash configuration
The source filesystem "/run/live/medium/live/filesystem.squashfs" does not
exist"
The .iso s from 12/11/2019 and 12/23/2019 failed exactly the same way.
These came from:
"https://cdimage.debian.org/images/unofficial/non-free/images-including-
firmware/weekly-live-builds/amd64/iso-hybrid/"
My SSD has boot/efi and swap partitions, a /data partition, and 5 20GB
partitions for OS installations.
This is being written from my current Debian Testing LXQt install, which dates
from March of this year, and has been upgraded. (I also sometimes use an old
Lubuntu 17.10 install when I need to scan, as I cannot use my printer/scanner
to scan with Debian, for some reason...)
The install proceeds normally, past the manual install stage (where I mark the
new OS partition for formatting, and keep all others unformatted and labelled
for access from the new install)
Shortly afterwards, the error window appears.
I know the root fs formatting succeeds, at least as far as assigning it a new
UUID - I was unable to boot THIS install until I edited my fstab to comment out
the mount line referring to the old install partition with its old UUID)
-- Package-specific info:
Boot method: USB
Image version: Debian Testing Live LXQt + nonfree .iso 12/11/2019 AND
12/23/2019
Date: 29, December 2019, ~1pm, ~2pm
Machine: ASUS Prime B350M-A(CSM) + AMD A12e processor and Sapphire Pulse Radeon
RX560 Graphics Card - 16GB RAM -1TB Crucial MX500 SSD
Partitions: <df -Tl will do; the raw partition table is preferred>
scott@ASUS-PRIME-B350M-A-CSM:~$ sudo /sbin/fdisk -l
[sudo] password for scott:
Disk /dev/sda: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: CT1000MX500SSD1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: E1ECFEC6-A297-4DC2-ADF3-37DEB7895D97
Device Start End Sectors Size Type
/dev/sda1 4096 1052671 1048576 512M EFI System
/dev/sda4 1052672 34605055 33552384 16G Linux swap
/dev/sda5 34605056 76546047 41940992 20G Linux filesystem
/dev/sda6 76546048 118487039 41940992 20G Linux filesystem
/dev/sda7 118487040 160428031 41940992 20G Linux filesystem
/dev/sda8 160428032 202369023 41940992 20G Linux filesystem
/dev/sda9 202369024 244310015 41940992 20G Linux filesystem
/dev/sda10 244314112 1953521663 1709207552 815G Linux filesystem
Disk /dev/sdb: 14.46 GiB, 15510536192 bytes, 30294016 sectors
Disk model: USB 2.0 FD
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 10A8A066-4BF3-4204-8D1E-DA561980E241
Device Start End Sectors Size Type
/dev/sdb1 18087936 30291967 12204032 5.8G Microsoft basic data
/dev/sdb2 2048 4095 2048 1M BIOS boot
/dev/sdb3 4096 503807 499712 244M EFI System
/dev/sdb4 503808 5881855 5378048 2.6G Linux filesystem
/dev/sdb5 5881856 18087935 12206080 5.8G Linux filesystem
Partition table entries are not in disk order.
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot: [ O]
Detect network card: [ ]
Configure network: [ ]
Detect media: [ O]
Load installer modules: [ O]
Clock/timezone setup: [ O]
User/password setup: [ O]
Detect hard drives: [ O]
Partition hard drives: [ E?]
Install base system: [ E?]
Install tasks: [ ]
Install boot loader: [ ]
Overall install: [ E]
Comments/Problems:
<Description of the install, in prose, and any thoughts, comments
and ideas you had during the initial install.>
--
Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.
Once you have filled out this report, mail it to sub...@bugs.debian.org.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Since the problem was caused by an non-standard live media setup,
(even though it seems to indicate Calamares being a bit fragile)
I assume that this bug should be considered closed.
--- End Message ---
