I used the ‘dd’ command to write the image and I’ve tried installing multiple ways (minimal vs. full-feature vs. manual partitioning) to try and get it to work but alas, I am stumped.
I also noticed that it isn’t allowing me to boot directly from the USB drive if I stop the “normal booting process” and manually select my USB as the disk to boot from, however if I let the “normal booting process” take its course, it boots… What is that about???
Hi, @dlmclaughlin and welcome to the Ubuntu MATE Community!
I see
[ 98.230919] SQUASHFS error: xz decompression failed, data probably corrupt
[ 98.230930] SQUASHFS error: Failed to read block 0x47a724b4: -5
[ 98.231022] SQUASHFS error: xz decompression failed, data probably corrupt
[ 98.231025] SQUASHFS error: Failed to read block 0x47a77aac: -5
[ 98.231685] SQUASHFS error: xz decompression failed, data probably corrupt
[ 98.231690] SQUASHFS error: Failed to read block 0x47a724b4: -5
[ 98.232411] SQUASHFS error: xz decompression failed, data probably corrupt
[ 98.232415] SQUASHFS error: Failed to read block 0x47a724b4: -5
which indicates either a BAD ISO (did you verify it after download) OR a bad write of ISO to your install media.
The image is written as a squashfs, or squashed file-system, and it cannot be read thus the SQUASHFS errors... Whilst there other causes (eg. insufficient RAM is available; VirtualBox has a known problem but their docs report it as a user error in the operator didn't allocate sufficient RAM for virtualbox to run the VM correctly) but the install media itself as been detected as faulty.
I've written a support answer you'll find at
on why i consider checksum validation is worthwhile (super cheap insurance, takes 1-2 secs but saves mins-hours of problem solving), but if you scan that question you'll find another (non-upvoted answer) which tells you what I do on to scan for the the self-validation check messages which I find helpful (added to that question so I'm not providing multiple links; I'm lazy...)
FYI: You mention release (24.04) but not which ISO as a total of 4 Ubuntu-MATE 24.04 ISOs have been released using 3 different kernels (6.8, 6.11 & 6.14)... I'm guessing you're using 24.04.3 based on a systemd package version, but it's helpful if you're specific with details & not requiring that we scan looking for clues hidden in minor details in your post... the older GA kernel (6.8) can be better for older hardware, newer 6.17 stack maybe better for newer hardware; IF your hardware is involved; you gave no details on your hardware but appear to be using the 6.14 kernel media from what I could see.
Thanks for the quick reply yesterday.
I was able to figure it out after a few hours of research and tinkering. I do very my ISOs via the ‘checksum’ method and this one was good. I ended up making a few changes that ultimately cleared the way for the installer to finish its job instead of throwing an error:
I see this every time I reboot, been seeing it for years possibly as far back as 16.04. Can’t think of a more useless popup and anybody fleeing the Windows 11 push will be immediately mystified and thinking they made a mistake. Getting rid of this should be a priority!
Can you please expound on your comment? Are you saying that the thrown error here has no bearing on whether the install was successful or not? If so, how did you reach that conclusion?
I see this every time I reboot, been seeing it for years possibly as far back as 16.04. Can’t think of a more useless popup
It’s not useless, if no one else has reported it. If you don’t want to keep reporting the same bug, or bugs at all it can easily be disabled. It is really up to you.
The crash reports are stored in /var/crash directory in Ubuntu. If you look in to this directory, you should see some files ending with crash.
What I suggest is that you delete these crash reports. Open a terminal and use the following command:
sudo rm /var/crash/*
Permanently get rid of system error pop up in Ubuntu
sudo pluma /etc/default/apport &
The content of the file is:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=1
Change the enabled=1 to enabled=0. Save and close the file. You won’t see any pop up for crash reports after doing this. Obvious to point out that if you want to enable the crash reports again, you just need to change the same file and put enabled as 1 again.
Basically, this notifies you of a crash in your system. Don’t panic by the word ‘crash’. It’s not a major issue and your system is very much usable. It just that some program crashed some time in the past and Ubuntu wants you to decide whether or not you want to report this crash report to developers so that they could fix this issue.
So, we click on Report problem and it will vanish?
No, not really. Even if you click on report problem, you’ll be ultimately greeted with a pop up like this:
Sorry, Ubuntu 16.04 has experienced an internal error.
If you notice further problems, try restarting the computer.
Reporting it:
That’s very thoughtful of you and the right thing to do. But there are two issues here. First, there are high chances that the bug would have already been reported. Second, even if you take the pain of reporting the crash, it’s not a guarantee that you won’t see it again.