On 2024-03-19 03:10, Roger Oberholtzer wrote:
>
>
> On Mon, Mar 18, 2024 at 5:43 PM Darryl Gregorash <raven@accesscomm.ca
> <mailto:raven@accesscomm.ca>> wrote:
>
> Why are you talking about this now? Andrei and I have been making
> suggestions of what you can try now, but all you have done is run
> commands Andrei suggested so we can get an idea what your system
> looks like right now.
> Doing a reinstall is the very last resort, and we are nowhere near
> there yet.
>
>
> The suggestion was to try the rollback. I did that and reported that it
> did not succeed. Did I miss another suggestion that was not perhaps
> going to totally mess up the filesystem? I also want to be sure I have
> collected all useful information off the system before trying a possibly
> destructive command. I've not had a chance to do that yet. Day job and
> all that.
>
Here is what you said in your first post:
> I have a strange (to me) situation on a Tumbleweed system with btrfs filesystems. Due to issues updating to KDE6, I had to rollback. And the rollback did not really roll back. So I snapper rm'd the various pre/post items so that the snapshot before the attempted update was the default one. It is now sorted so that it boots into the snapshot that I want.
So the rollback did not succeed (I am quite amazed that it did not,
assuming you did it correctly). We have no idea what procedure you used,
or what causes you to say the rollback failed, because you saw fit not
to report this to us.
I thought I had. I guess it got edited away. After the rollback, the SDDM login was still borked, complaining about missing kde/plasma 6 things. I cannot in any way see how that is possible if it had rolled back. So I thought I would just get rid of the update and try again.
Next you say you deleted all the snapshots that were made later than the
one you want as the default. If that rollback really did fail, then, I'm
not certain, but this is possibly the very last thing you wanted to do
at this stage.
After I did the rollback and rebooted, and the kde6/plasma6 things remained, I decided to set the last good snapshot to the current one. Upon reflection, the thing to have done at that point is a rollback to that specific snapshot. Live and learn.
<snip>
>
>
> I was thinking something similar. But I guess I cannot make 1405 (a
> zypper pre) the default and boot into that. And then rollback 1406.
> Would I need to rollback 1405?
Before resorting to this, try Andrei's suggestion. When he first posted
it, he suggested "snapper rollback --ambit=classic", or something like
that. The ambit option was in the wrong place (it certainly is a global
option), so the command did not run.
In his next post, he corrected this and showed the output from his
system. So run
snapper --ambit=classic rollback
I have reported exactly this elsewhere in this thread. (Spoiler alert: issue now solved).