Issues with Live System Create -- USB disk and Install

I personally hate the apport and I have disabled. Seriously, who read thousands of these error reports? If something is wrong, then I see it anyway.
But anyway, these programs are running normally (after error windows)? GNOME terminal can be opened, Unity is running fine and the volume indicator is displayed?

(A)(1): This existing GRUB menu (and bootloader) is not installed by Systemback, this is from another system. So this behavior is completely normal.

(A)(2): Yes, because you run update-grub command, and you reinstall the system with Systemback. This menu item points to a wrong (non-existing) partition (previous installed system). So this behavior is completely normal.

Please install GRUB with Systemback, and use it instead of this existing one.

(B): So the recognized (by update-grub command) UUID is wrong? But in that case why happens the (A)(2)?

Yeah, I'm with you -- disabling apport probably a good idea.

Yes! After the error windows GNOME terminal works fine, Unity is fine, and volume indicator is displayed. I mentioned it because using ISOs created under previous versions of Systemback, this does not happen (of course, other things in my system changed over that time as well - so it may not be Systemback's changes).

Sorry, but I'm not sure how to install GRUB with Systemback. I did a System Upgrade, which I see does affect GRUB. But I also saw an option for that in System Repair, though I couldn't get it to show the option as "Enabled."

I don't think anything has changed that would cause this. But maybe try again the Live creation, maybe the second time will be good.

I mean, when you install the system with Systemback, then you don't disable the GRUB installation. And if necessary, you can manually set it to where you should be installed. In default (auto value with BIOS), the bootloader will be installed in disk MBR where the root filesystem (or /boot filesystem) is located (so where the system is installed). But if you have two or more hard drive, you need to set the boot order in the BIOS.
If you use this newly installed bootloader and GRUB menu, the copied system will be the first menu item.
So you're using BIOS (or compatible mode) and not UEFI, right? The UEFI is simpler, but the system names may be causing conflicts.

Thanks for the help. I tried a second Live creation, but no go.

Sorry to be dense, but can you please let me know exactly when to install Grub? Let me first state what I am doing.

I boot into the live USB. I open Systemback. Unlike in a non-live system, it starts immediately in the "System Install" option. I put in the user name, login, etc. and press "Next." On the "Partition Settings" panel, I select the partition where I want to install the system (here, /dev/sda9). I then select Moint Point "/", filesystem "ext4", check the "format" box, and hit the backward green arrow. This gives me the "Next" button, which when clicked installs the system.

There IS the "Install GRUB 2 bootloader" option, but it is disabled unless you set the mount point to "/boot/efi." Is that what you are saying I should do -- instead of setting it to "/"?

My concern was that doing so would incorrectly set Partition 9 as the boot sector (is this wrong?), and I just want Partition 9 to be one of 3 linux distributions on 3 separate partitions (here, 5, 7, and 9).

In answer to your last question (I think), I use BIOS to set the boot order, but booting into GRUB from there gets me all of the Linux distributions.

Ok, so these errors are not coincidences, and reproducible. But the GNOME terminal was not runned on Live before these apport windows are showed up. So something happened to him even earlier. Because if something does not run, it can not crash either.

Now, I see your GRUB problem. So you have a machine with UEFI (not BIOS), but you do not install bootloader with Systemback. This is not good. When you select the partitions at installation time, please select the existing EFI partition too (or create a new one, ~100 MiB FAT32), and set '/boot/efi' mount point. This will overwrite the entries of the same name in EFI partition and in UEFI NVRAM. But in theoretically, the newly installed system will start by default (or select the 'Ubuntu' in UEFI boot menu).
Maybe the original (B) problem is happening because you don't install bootloader and the update-grub command was not executed on this new system.

In the meantime, I performed a few tests and I was thinking it over. You original (B) problem is definitely happening because disabled the GRUB installation in Systemback. In this case, the grub.cfg file is not updated, and the source system is loading instead of the copied. This may be a bug as well.
But I can fix this problem, so I do it. After this the copied system will start fine from external GRUB menu. I working on it...

Awesome! Thanks for staying with me on this. I will be happy to test the update if you would like.

I successfully fixed this (B) problem. I tested the new code, and works good.
The new packages (1.1.3.110) are available in stable PPA, and I will update SourceForge files too, just later (currently I get error 500).

I can confirm that (B) is fixed. I created a new Live system. I then wrote it to USB. I then booted into the USB and used Systemback to install the Live system to my /dev/sda9. This all worked. On reboot, the system on /dev/sda9 showed up in my GRUB 2 menu. But when trying to start it, I got the error described in (A)(2) above:

error: no such device:
error: no such partition.
alloc magic is broken at 0x7ba1: 7ba9...
Aborted. Press any key to exit.__.

I then booted into another partition and did a "sudo update-grub." I then rebooted to GRUB2 and, upon selecting my /dev/sda9 system, it booted and works. It did show a few of thos apport errors, but I forgot to disable it.

Thought/question: Does it make sense, and is it feasible, to incorporate an "update-grub" command at the end of the live system installer?

Thanks for working this out! I will mark it as problem solved.

This 'update-grub' command is already here (this is the fix). But this command is executed on copied system, not on your external installation. You have to run it by hand on your other system, or install a bootloader with Systemback. Just like any other Linux installer.