How to remove a snapshot that cannot be deleted: "org.freedesktop.DBus.Error.Failed"

Hi!

There is one snapshot on my system which cannot be removed by Yast.

This is on Opensuse Tumbleweed - I never had a problem like this before…

The description of the snapshot is: "writable copy of #3868

It’s the only one that is described as “writable copy” on my system.

If I use the Yast snapshot management module I get the following error:

org.freedesktop.DBus.Error.Failed; caused by 3 sender=:1.1208 -> dest=:1.1209 serial=33 reply_serial=44 path=; interface=; member= error_name=error.something

I am really helpless here - I can copy it (made a backup just in case) but cannot remove it…

I think I really have to get rid of it - it seems to create serious lagging after system boot. Which would make sense as it deviates a lot from the latest snapshots. It’s over 9 month old - the oldest snapshot in the list. The next one - the second oldest - is only 3 month old.

Is there any solution?

Thx for helping,
jhhh

I’d be inclined to take a look at dmesg to see if there’s a hardware issue going on.

The other thing you can try doing is open a terminal window and then run sudo snapper list (to list the snapshots out) and then sudo snapper rm <n> where “” is the number of the snapshot you want to remove.

The console commands might provide more output - but you probably will need to run them as root unless you’ve specifically given your user the rights to manage snapshots.

Start with providing the full output of snapper list, not some random messages out of blue sky.

Thanks for your hint!

I just solved it!

I used a rollback to the state of yesterday and after the system was up running again I could use Yast to remove it just as every other snaphot - then I re-applied the package updates with zypper dup and the snapper list is showing with all the expected entries.

Cheers!

1 Like

Thx.

I will do so if I have a snapshot problem again.

Obviously I am not as experinced as you are that’s why I have asked here.
I assumed that the error message thrown by Yast would would be a good starting point regarding this matter…

But for now I could solve it (see my other post if you are interested).

Happy Easter!

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.