Yast has disappeared from my system and no bootable snapshots are available

English Install/Boot/Login
1

My system has been unstable since I upgraded from Leap 15.4 to 15.5. Problems include system freezing and not responding to any mouse activity and keyboard on works for Alt-PrntScr-B. When running I have had instances of the system restarting with no input from me.

I thought I would try reverting to an earlier snapshot and checked what snapshots to look for. Here is the result of my command:-

alastair@HP-Z640-1:~> sudo snapper --iso list
   # | Type   | Pre # | Date                | User | Cleanup  | Description        | Userdata     
-----+--------+-------+---------------------+------+----------+--------------------+--------------
  0  | single |       |                     | root |          | current            |              
  2  | single |       | 2023-07-22 16:00:37 | root | timeline | timeline           |              
  3  | single |       | 2023-07-22 16:00:37 | root | timeline | timeline           |              
 13  | pre    |       | 2023-07-23 19:06:59 | root | number   | zypp(zypper)       | important=yes
 14  | pre    |       | 2023-07-23 19:13:10 | root | number   | zypp(zypper)       | important=yes
 15  | post   |    14 | 2023-07-23 20:07:30 | root | number   |                    | important=yes
 16  | pre    |       | 2023-07-23 20:09:01 | root | number   | zypp(zypper)       | important=yes
 17  | post   |    16 | 2023-07-23 20:09:33 | root | number   |                    | important=yes
 72  | pre    |       | 2023-07-29 19:24:52 | root | number   | zypp(zypper)       | important=yes
 73  | post   |    72 | 2023-07-29 19:29:14 | root | number   |                    | important=yes
 94  | pre    |       | 2023-08-02 12:10:55 | root | number   | zypp(zypper)       | important=yes
 95  | post   |    94 | 2023-08-02 12:13:09 | root | number   |                    | important=yes
 98  | pre    |       | 2023-08-03 17:58:38 | root | number   | zypp(zypper)       | important=yes
 99  | post   |    98 | 2023-08-03 18:00:47 | root | number   |                    | important=yes
100  | pre    |       | 2023-08-03 18:03:30 | root | number   | zypp(zypper)       | important=yes
101  | post   |   100 | 2023-08-03 18:04:05 | root | number   |                    | important=yes
108  | pre    |       | 2023-08-04 13:59:08 | root | number   | yast sw_single     |              
109  | pre    |       | 2023-08-04 13:59:49 | root | number   | zypp(ruby.ruby2.5) | important=no 
110  | post   |   109 | 2023-08-04 14:02:01 | root | number   |                    | important=no 
112  | post   |   108 | 2023-08-04 14:29:33 | root | number   |                    |              
114  | pre    |       | 2023-08-04 16:17:57 | root | number   | yast nfs           |              
115  | post   |   114 | 2023-08-04 16:26:50 | root | number   |                    |              
116  | pre    |       | 2023-08-04 16:26:54 | root | number   | yast nfs           |              
117  | post   |   116 | 2023-08-04 16:28:57 | root | number   |                    |              
122  | pre    |       | 2023-08-04 16:45:26 | root | number   | yast nfs           |              
125  | post   |   122 | 2023-08-04 16:54:55 | root | number   |                    |              
130  | pre    |       | 2023-08-04 18:32:30 | root | number   | yast sw_single     |              
131  | pre    |       | 2023-08-04 18:33:16 | root | number   | zypp(ruby.ruby2.5) | important=no 
132  | post   |   131 | 2023-08-04 18:33:19 | root | number   |                    | important=no 
133  | post   |   130 | 2023-08-04 18:33:26 | root | number   |                    |              
134  | pre    |       | 2023-08-05 14:36:38 | root | number   | zypp(zypper)       | important=no 
135  | post   |   134 | 2023-08-05 14:37:25 | root | number   |                    | important=no 
136  | pre    |       | 2023-08-05 15:02:53 | root | number   | yast sw_single     |              
137  | pre    |       | 2023-08-05 15:03:27 | root | number   | zypp(ruby.ruby2.5) | important=no 
138  | post   |   137 | 2023-08-05 15:03:48 | root | number   |                    | important=no 
139  | post   |   136 | 2023-08-05 15:03:51 | root | number   |                    |              
alastair@HP-Z640-1:~>

It seems snapper is running but when I re-boot I am unable to find any snapshots as described in the manual:-

Boot the system. In the boot menu choose Bootable snapshots and select the snapshot you want to boot. The list of snapshots is listed by date—the most recent snapshot is listed first.

I then thought I would check the snapshots using Yast and Yast is not present. I cannot find it anywhere in my Application Menu.
I tried cli:-

alastair@HP-Z640-1:~> sudo yast2
[sudo] password for root: 
sudo: yast2: command not found
alastair@HP-Z640-1:~>

I am stuck. I have no idea how I can have lost Yast or what is going wrong.
Any ideas?

2 
zypper in yast2
3

Brief and pragmatic. Thanks!

4

OK thanks. My mistake was removing fdupes as it took all the ruby dependencies out and yast2 and several yast patterns. Careless of me. All restored now thanks. I have also installed jdupes so I can try later but I think you identified the problem and fdupes is probably fine.

Also I am still looking into the absence of snapshots in my boot screen. Will check the manual as I see what I have missed as requirements have changed a bit between 15.4 and 15.5. I shall post a new thread if I get stuck.
Thanks again,

5

@Budgie2:

 > rpm --erase --test yast2
error: Failed dependencies:
        yast2 >= 4.2.67 is needed by (installed) yast2-vpn-4.5.1-150500.1.1.noarch
        yast2 >= 4.1.3 is needed by (installed) yast2-sysconfig-4.5.0-150500.1.1.noarch
        yast2 is needed by (installed) yast2-support-4.5.0-150500.1.1.noarch
        yast2 >= 3.1.180 is needed by (installed) yast2-sound-4.5.0-150500.1.5.x86_64
        yast2 >= 4.1.60 is needed by (installed) yast2-snapper-4.5.1-150500.1.1.x86_64
        yast2 is needed by (installed) yast2-slp-4.5.0-150500.1.2.x86_64
        yast2 is needed by (installed) yast2-scanner-4.5.1-150500.1.2.x86_64
        yast2 is needed by (installed) yast2-proxy-4.5.0-150500.1.1.noarch
        yast2 is needed by (installed) yast2-pam-4.5.0-150500.1.1.noarch
        yast2 >= 4.0.39 is needed by (installed) yast2-nfs-server-4.5.0-150500.1.1.noarch
        yast2 >= 3.1.117 is needed by (installed) yast2-journal-4.5.3-150500.1.1.noarch
        yast2 >= 4.4.38 is needed by (installed) yast2-firewall-4.5.0-150500.1.1.noarch
        yast2 is needed by (installed) yast2-auth-server-4.5.1-150500.1.1.noarch
        yast2 is needed by (installed) yast2-auth-client-4.5.4-150500.1.1.noarch
        yast2 >= 2.21.22 is needed by (installed) yast2-auth-client-4.5.4-150500.1.1.noarch
        yast2 >= 4.1.3 is needed by (installed) yast2-tftp-server-4.5.0-150500.1.1.noarch
        yast2 >= 4.3.10 is needed by (installed) yast2-services-manager-4.5.1-150500.1.1.noarch
        yast2 >= 3.1.183 is needed by (installed) yast2-printer-4.5.2-150500.1.2.x86_64
        yast2 is needed by (installed) yast2-control-center-4.5.0-150500.1.5.x86_64
        yast2 >= 2.21.0 is needed by (installed) yast2-online-update-configuration-4.5.1-150500.1.1.noarch
        yast2 >= 4.4.19 is needed by (installed) yast2-online-update-4.5.3-150500.1.1.noarch
        yast2 >= 4.4.38 is needed by (installed) yast2-nfs-client-4.5.2-150500.1.1.noarch
        yast2 is needed by (installed) yast2-metapackage-handler-4.5.0-150500.1.1.noarch
        yast2 >= 4.1.3 is needed by (installed) yast2-iscsi-client-4.5.7-150500.1.1.noarch
        yast2 >= 4.2.57 is needed by (installed) yast2-country-4.5.5-150500.1.1.x86_64
        yast2 >= 4.5.16 is needed by (installed) yast2-bootloader-4.5.8-lp155.1.5.x86_64
        yast2 >= 4.0.39 is needed by (installed) yast2-samba-client-4.5.3-150500.1.1.noarch
        yast2 >= 4.4.38 is needed by (installed) yast2-ntp-client-4.5.3-150500.1.2.noarch
        yast2 >= 2.21.22 is needed by (installed) yast2-nis-client-4.5.0-150500.1.2.x86_64
        yast2 is needed by (installed) yast2-ldap-4.5.0-150500.1.3.x86_64
        yast2 >= 3.0.4 is needed by (installed) yast2-vm-4.5.0-150500.1.1.x86_64
        yast2 >= 4.2.67 is needed by (installed) yast2-tune-4.5.1-150500.1.1.x86_64
        yast2 >= 4.4.47 is needed by (installed) yast2-security-4.5.6-150500.1.1.noarch
        yast2 >= 2.21.22 is needed by (installed) yast2-sudo-4.5.0-150500.1.1.noarch
        yast2 >= 4.1.0 is needed by (installed) yast2-samba-server-4.5.0-150500.1.1.noarch
        yast2 >= 4.0.39 is needed by (installed) yast2-mail-4.5.0-150500.1.1.noarch
        yast2 >= 4.4.42 is needed by (installed) yast2-installation-4.5.16-150500.1.2.noarch
        yast2 >= 4.4.25 is needed by (installed) yast2-update-4.5.3-150500.1.1.x86_64
        yast2 >= 4.4.19 is needed by (installed) yast2-add-on-4.5.4-150500.1.1.noarch
        yast2 >= 4.2.57 is needed by (installed) yast2-ftp-server-4.5.0-150500.1.1.noarch
        yast2 is needed by (installed) patterns-yast-yast2_basis-20220411-lp155.2.4.x86_64
        yast2 > 3.3.2 is needed by (installed) yast2-apparmor-4.5.1-150500.3.3.1.noarch
        yast2 >= 4.4.38 is needed by (installed) yast2-packager-4.5.17-150500.3.3.1.x86_64
        yast2 >= 4.5.12 is needed by (installed) yast2-network-4.5.21-150500.3.3.1.noarch
        yast2 is needed by (installed) autoyast2-installation-4.5.14-150500.3.3.1.noarch
        yast2 >= 2.16.36 is needed by (installed) autoyast2-installation-4.5.14-150500.3.3.1.noarch
        yast2 >= 4.4.38 is needed by (installed) yast2-storage-ng-4.5.24-150500.3.5.1.x86_64
        yast2 >= 4.4.18 is needed by (installed) yast2-users-4.5.7-150500.3.8.1.x86_64
 >

Please note the dependency to “patterns-yast-yast2_basis” – which seem to have any dependencies:

 > rpm --erase --test patterns-yast-yast2_basis
 >

Therefore, assuming that, you also erased/removed “patterns-yast-yast2_basis”, executing “zypper verify” possibly wouldn’t have raised any errors …

6

Hi Don,
Sorry but I cannot follow this. --erase is a command and --test is an option for this but I do not recall installing any test. Is it something I had tried and forgotten (which is easier these days!) or is it lurking somewhere, in which case where?

7

“rpm --erase --test «Package Name»” is a means of determining which dependencies any given package has.

  • If a given package, such as “patterns-yast-yast2_basis”, has no dependencies, then if that package is removed, there won’t be any Package Manager complaints about broken dependencies.

AFAICS, there’s no other means to really find out what will happen – due to dependencies – if a package is removed or erased.

8

OK, and thanks. I have been doing my housekeeping slowly and I am content to leave as now and then remove any orphans one at a time using test.
Thanks again,
Alastair.