Hi Arvin, I installed snapper-0.10.3-8.1.x86_64.rpm from the location you provided into a test VM which also had the same problem as the host machine. Running /usr/lib/snapper/systemd-helper --cleanup running cleanup for 'home'. running number cleanup for 'home'. running timeline cleanup for 'home'. running empty-pre-post cleanup for 'home'. running cleanup for 'root'. running number cleanup for 'root'. quota not working (preparing quota failed) running timeline cleanup for 'root'. running empty-pre-post cleanup for 'root'. That got rid of the error messages although not sure why it says quota is not working because 'snapper -c home ls' shows the space used by each snapshot and it would not if quota was not enabled. So that resolves the 'Failure (error.something).' message that was coming from /usr/lib/snapper/systemd-helper --cleanup but when I look at /var/log/snapper.log it seems that it is still having issues with that latest snapper rpm as it has: 2022-12-05 11:06:00 WAR libsnapper(3345) Snapper.cc(prepareQuota):791 - THROW: preparing quota failed 2022-12-05 11:06:00 WAR libsnapper(3345) Client.cc(dispatch):1921 - CAUGHT: preparing quota failed 2022-12-05 11:06:00 WAR libsnapper(3398) errors.cc(convert_exception):39 - CAUGHT: dbus error exception 2022-12-05 11:06:00 WAR libsnapper(3398) errors.cc(convert_exception):47 - THROW: preparing quota failed 2022-12-05 11:06:00 WAR libsnapper(3398) cleanup.cc(is_quota_aware):264 - CAUGHT: preparing quota failed 2022-12-05 11:06:00 MIL libsnapper(3345) Snapper.cc(queryFreeSpaceData):899 - size:527636103168 free:487053434880 2022-12-05 11:06:00 MIL libsnapper(3345) Snapper.cc(queryFreeSpaceData):899 - size:527636103168 free:487053434880 2022-12-05 11:06:00 MIL libsnapper(3345) Comparison.cc(Comparison):60 - num1:4 num2:5 2022-12-05 11:06:00 MIL libsnapper(3345) Comparison.cc(load):272 - num1:4 num2:5 2022-12-05 11:06:00 MIL libsnapper(3345) Comparison.cc(load):256 - read 7 lines 2022-12-05 11:06:30 MIL libsnapper(3345) Snapper.cc(~Snapper):142 - Snapper destructor 2022-12-05 11:06:30 MIL libsnapper(3345) Snapper.cc(~Snapper):142 - Snapper destructor 2022-12-05 11:07:00 MIL libsnapper(3345) snapperd.cc(main):315 - exiting So it would appear the original issue is fixed but now there is a bug regarding quota. Or possibly it was not getting to the quota part of the code with the initial bug. Despite the error it still seems to be properly cleaning up the timeline snapshots. Joe