Using Systemback

Norbert_X · 14 June 2020 07:03

It may be good, but for now SystemBack is really broken with latest Ubuntu 20.04 LTS version - see

and on

github.com/fconidi/Systemback_source-1.9.4

systemback 1.9.4 is not compatible with file layout of modern Ubuntu 20.04 LTS

opened 09:40PM - 20 May 20 UTC

Thank you for bringing life back to the great SystemBack [project](https://launc…hpad.net/systemback). But I need to say that cloning the freshly installed Ubuntu MATE 20.04 LTS system using [SystemBack 1.9.4](https://francoconidi.it/systemback-1-9-4-per-debian-10-ubuntu-20-04/) results with a system with incorrect file structure and broken D-Bus. The following symlinks are absent: * /bin -> /usr/bin * /lib -> /usr/lib * /lib32 -> /usr/lib32 * /lib64 -> /usr/lib64 * /libx32 -> /usr/libx32 * /sbin -> /usr/sbin and got transformed to regular directories: * /bin * /lib * /lib32 * /lib64 * /libx32 * /sbin See the discussion on [Ubuntu MATE community](https://ubuntu-mate.community/t/caja-python-error-and-systemback-support/21814/3?u=norbert_x) for details. Today I have checked the normal Ubuntu 20.04 LTS with default GNOME Shell. It have the same issues with filesystem and have D-Bus errors in `/var/log/syslog`. Manually installed Caja does not want to start on cloned system.

Restored system misbehaves solidly.