| 2021-11-02 16:10:26 |
Maurice Volaski |
description |
To reproduce this bug, take the following steps
Install Ubuntu 20.04.3.
Boot into it and get past the initial startup screens.
Take a manual recursive zfs snapshot like so
zfs snapshot -r rpool@beforeanything
Now touch a file on the desktop and install a package like htop.
You should see the file and htop should be able to run.
Reboot and hit escape to enter the grub screen. Choose the history menu and choose the snapshot you just created. Then hit enter and then choose the option to revert system and user data and then enter again.
If it were working correctly, everything should be reverted. There’d be no file on the desktop and no trace of htop.
That’s not what occurs. The file on the desktop is still there, and while htop is no longer installed, the package management seems to think it is. |
To reproduce this bug, take the following steps
Install Ubuntu 20.04.3 using a ZFS-based root.
Boot into it and get past the initial startup screens.
Take a manual recursive zfs snapshot like so
zfs snapshot -r rpool@beforeanything
Now touch a file on the desktop and install a package like htop.
You should see the file and htop should be able to run.
Reboot and hit escape to enter the grub screen. Choose the history menu and choose the snapshot you just created. Then hit enter and then choose the option to revert system and user data and then enter again.
If it were working correctly, everything should be reverted. There’d be no file on the desktop and no trace of htop.
That’s not what occurs. The file on the desktop is still there, and while htop is no longer installed, the package management seems to think it is. |
|
