what is the best thing to do now?

I just discovered, after upgrading my Leap 15.4 that some very critical procps commands such as “ps” and “pgrep” and “pkill” are corrupted, insiduously so. My attempts to use yast2 to reinstall the procps are failing.

For example the ps command is normally /bin/ps… but in my system it is circularly linked “ps → /bin/ps” to itself. Running the md5sum check on both “pgrep” and “pkill” show that they are exactly binary equal, thus they cannot be true nor even be the correct commands. Sysctl is also circularly linked to itself.

I need ps in particularly to work, so what do I need to do? Start with a fresh brand new clean ISO disk and install Leap 15.4 from scratch? Obviously the system is corrupt, perhaps a repository has been compromised?

One more thing, which I just now noticed at root level / on the root drive

/bin links to /usr/bin
/sbin links to /usr/sbin
/lib links to /usr/lib
/lib64 links to /usr/lib64

This appears to have happened on March 7th, 8th and 9th of this year.

I can remove the links and move the folders back to the root / location

But what IS standard for these 4 folders?

  • American Citizen (wondering what to do now??)

It looks like you have seriously incorporated Tumbleweed repos to cause those symlinks, which are standard for TW, but not for 15.4:

# ls -gG /
total 159
drwxr-xr-x   2  4096 Sep 12 01:12 bin
drwxr-xr-x   3 16384 Sep 27 03:26 boot
drwxr-xr-x  19  5320 Oct 18 00:15 dev
drwxr-xr-x 125 20480 Oct 21 09:44 etc
drwxr-xr-x  29  1024 Aug  7 18:12 home
drwxr-xr-x   8  4096 Sep 27 03:06 lib
drwxr-xr-x   5 12288 Sep 27 03:07 lib64
drwx------   2 16384 Jul 31  2018 lost+found
drwxr-xr-x   2  4096 May 22 20:42 media
drwxr-xr-x   2  4096 Mar 15  2022 mnt
drwxr-xr-x   5  4096 Mar 15  2022 opt
dr-xr-xr-x 312     0 Oct  7 00:15 proc
drwx------  25 12288 Oct 22 03:12 root
drwxr-xr-x  33  1000 Oct  8 02:41 run
drwxr-xr-x   2 12288 Sep 27 03:07 sbin
drwxr-xr-x   2  4096 Mar 15  2022 selinux
dr-xr-xr-x   6  1024 Mar 15  2022 srv
dr-xr-xr-x  13     0 Oct  7 00:15 sys
drwxrwxrwt  23   540 Oct 22 03:15 tmp
drwxr-xr-x  12  4096 Mar 15  2022 usr
drwxr-xr-x  11  4096 Mar 30  2022 var

I would not expect extrication from these problems except by: 1-changing all repos to TW and doing a zypper dup; or 2-installing 15.4 afresh. Usrmerge that originally created those symlinks in TW last year is not designed to work in reverse.

What is your output from zypper lr -d?

What do you mean by this? Just “updating an existing 15.4 with the new updates found”, or" upgraded from another version to 15.4?
Remark that updating and upgrading are i general understood here as quite different actions.

And yes, please show

zypper lr -d

Thank you for your replies, they are appreciated.

In regard to my words “upgrade to 15.4” I meant that I ran the upgrade selection on the openSUSE install disk, and it did a 15.4 upgrade to my already existent 15.4 system. Sorry if I was not clear on this. I see that symlinks to the /usr/bin, /usr/sbin, /usr/lib and /usr/lib64 apparently took place on March 7th-9th of this year, but I was not aware of it at the time.

Two days ago I installed the openSUSE factory repo to pick up the dependency of libXcomposite for the Webex rpm install, and that’s when things started falling apart. The system asked to update over 4811 files and instead of stopping that and removing the factory repo, I went ahead and updated, only to discover about 2/3 the way through, that my plasma5 desktop stopped functioning and mouse clicks would NOT open windows or initiate other actions. At this point I knew that my system was in deep trouble. Rebooting brought me to the UEFI firmware bios asking me for the secret password (which I did not have) and I knew that I had an unbootable paritition. Fortunately I did keep a rescue disk and install disk, both 15.4, and was able to run the upgrade three times, since I had a read problem with the rescue disk and each time I ran the upgrade pass, I had to install files. First time, it wanted over 5000 files, the second time 639 files, the third time was to fix problems with the dbus-1 code and the grub2-mkconfig and grub2-initenv which were mysteriously plagued by a mismatch on the glic library version. I was able to finally overcome those two problems, by reinstalling the libdevmapper library.

If I do a fresh install of openSuse 15.4, will this iso be okay? For some reason, I am trying to download https://download.opensuse.org/distribution/leap/15.4/iso/openSUSE-Leap-15.4-NET-x86_64-Current.iso but it keeps switching to https://mirrors.kernel.org/opensuse/distribution/leap/15.4/iso/openSUSE-Leap-15.4-NET-x86_64-Build243.2-Media.iso link instead. See https://download.opensuse.org/distribution/leap/15.4/iso/ page, but I cannot seem to directly download the openSUSE-Leap-15.4-DVD-x86_64-Current.iso image file directly, it keeps switching to the build243-2 media version instead.

The output of zypper lr -d is

owner@localhost:~/Repository> cat repository.list

| Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service

—±---------------------------------±---------------------------------------------------------------------±--------±----------±--------±---------±-------±------------------------------------------------------------------------------±-------
1 | Google-Chrome | Google Chrome | Yes | (r ) Yes | Yes | 98 | rpm-md | https://dl.google.com/linux/chrome/rpm/stable/x86_64 |
2 | Mozilla | Mozilla | Yes | (r ) Yes | Yes | 99 | rpm-md | https://download.opensuse.org/repositories/mozilla/openSUSE_Leap_15.4/ |
3 | Nvidia Repository | Nvidia Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | https://download.nvidia.com/opensuse/leap/15.4 |
4 | Science | Science | Yes | (r ) Yes | Yes | 99 | rpm-md | https://download.opensuse.org/repositories/science/15.4/ |
5 | brave-browser | Brave Browser | Yes | (r ) Yes | Yes | 98 | rpm-md | https://brave-browser-rpm-release.s3.brave.com/x86_64/ |
6 | http-opensuse-guide.org-3de2e448 | Libdvdcss Repository | Yes | (r ) Yes | Yes | 98 | rpm-md | http://opensuse-guide.org/repo/openSUSE_Leap_15.4/ |
7 | lynis | CISOfy Lynis Repository | Yes | (r ) Yes | Yes | 1 | rpm-md | https://packages.cisofy.com/community/lynis/rpm/ |
8 | openSUSE-Leap-15.4-1 | openSUSE-Leap-15.4-1 | No | ---- | ---- | 99 | rpm-md | cd:/?devices=/dev/disk/by-id/ata-hp_CDDVDW_SH-216DB_R96F68DF400NAV |
9 | opera | Opera Packages | Yes | (r ) Yes | Yes | 99 | rpm-md | https://rpm.opera.com/rpm |
10 | packman | Packman Repository | Yes | (r ) Yes | Yes | 97 | rpm-md | https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.4/ |
11 | repo-backports-debug-update | Update repository of openSUSE Backports (Debug) | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.4/backports_debug/ |
12 | repo-backports-update | Update repository of openSUSE Backports | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.4/backports/ |
13 | repo-debug | Debug Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/debug/distribution/leap/15.4/repo/oss/ |
14 | repo-debug-non-oss | Debug Repository (Non-OSS) | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/debug/distribution/leap/15.4/repo/non-oss/ |
15 | repo-debug-update | Update Repository (Debug) | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/debug/update/leap/15.4/oss/ |
16 | repo-non-oss_1 | Non-OSS Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/distribution/leap/15.4/repo/non-oss/ |
17 | repo-oss_1 | Main Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/distribution/leap/15.4/repo/oss/ |
18 | repo-sle-debug-update | Update repository with updates from SUSE Linux Enterprise 15 (Debug) | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/debug/update/leap/15.4/sle/ |
19 | repo-sle-update | Update repository with updates from SUSE Linux Enterprise 15 | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.4/sle/ |
20 | repo-source | Source Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/source/distribution/leap/15.4/repo/oss/ |
21 | repo-update-non-oss_1 | Update Repository (Non-Oss) | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.4/non-oss/ |
22 | repo-update_1 | Main Update Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.4/oss |
23 | skype-stable | Skype (stable) | Yes | (r ) Yes | Yes | 99 | rpm-md | https://repo.skype.com/rpm/stable/ |
24 | snappy | Snappy Repository | Yes | (r ) Yes | Yes | 98 | rpm-md | https://download.opensuse.org/repositories/system:/snappy/openSUSE_Leap_15.4/ |
owner@localhost:~/Repository>

I am guessing that a fresh install of 15.4 will be the best thing to do?

In regard to my words “upgrade to 15.4” I meant that I ran the upgrade selection on the openSUSE install disk, and it did a 15.4 upgrade to my already existent 15.4 system.

Do you mean that you had a running Leap 15.4 system and that you then started the Leap15.4 installation from the DVD/USB-mass-storage and you there selected the Upgrade item?

When yes, I have no idea what that means. It probably depends on what you did after the original installation. If you did update the system (which should be done on e regular base), then I assume that all those updated packaged are now reverted back to the versions that are on the installation medium. I would normally advise to try a zypper up first to get all the updated versions back. When that would not repair the problem, I would advice a zypper dup with all non-standard repos disabled.

But like said above, I doubt that these actions will undo all those symlinks. Because no developers would have imagined that something like that would be needed.

The list (badly readable because of no CODE tags used) seems to contain only 15.4 repos where needed, so that is OK.

Indeed, the link to the 15.4 current redirects to that 432 iso. Strange. Maybe a bug report is needed.
In any case, the current ISO is th same as the original ISO, but with packages updated when the current one was made. So when you after installation do a zypper yp (or YaST Online Update). there will be more to do when the original is used then when the current is used. But the result will be the same.,
I do not know if you have a separate file system for /home, when yes, then of course keep it. When no, then make an extra backup of all in /home to restore after installation.

I come back to the ISO: openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso

That will probably be OK. 243.2 is just the build number. It counts on and on. There is clearly 15.4 there in the name.

I see that I have one openSUSE-Leap-15.3-2-DVD-x86_64-Build24.5-Media.iso
Similar to waht is now, only build 24.5 (and a different LEAP version).

Thanks for the advice, I am going to have to do a fresh install, but I don’t think I have the right iso image file, which I burned last night to a DVD, it is build243.2 media version iso so I don’t think that this is correct. Could you please look into getting the link problem straightened out so that correct x86_64 version is downloadable?

Thank you!

Note: Using the wget command

%wget https://download.opensuse.org/distribution/leap/15.4/iso/openSUSE-Leap-15.4-DVD-x86_64-Current.iso

seems to be working correctly for grabbing this particular iso image, not the media version. My download rate is about 5 megs/sec, so it will take awhile. Hopefully the sha256sum checksum will match.

Using wget is OK, but As I said above, that build number is OK. nd of course it is a medium (plural media).

Well, apparently the two images are exactly the same:

-rw-r--r-- 1 owner users 4083154944 Oct 21 17:55 openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso
-rw-r--r-- 1 owner users        117 Oct 21 18:02 openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso.sha256
-rw-r--r-- 1 owner users 4083154944 May 27 17:56 openSUSE-Leap-15.4-DVD-x86_64-Current.iso
-rw-r--r-- 1 owner users        117 Oct 22 11:45 openSUSE-Leap-15.4-DVD-x86_64-Current.iso.sha256

owner@localhost:~/Downloads> sha256sum -c openSUSE-Leap-15.4-DVD-x86_64-Current.iso.sha256
openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso: OK

owner@localhost:~/Downloads> diff openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso.sha256 openSUSE-Leap-15.4-DVD-x86_64-Current.iso.sha256
 

The match on the sha256 and the identical byte size are two clues that they are the same identical iso image file

As I said several times above.

Thanks, but my browser did NOT show me your key reply at first, which is why I went ahead and checked using the sha256sum. Sorry for the repeats.

No problem. You now are 1000% sure it is the correct and checked ISO. And that is reassuring.

Thank you all for your advice and steering me the right direction. I consider my problem resolved. Hopefully a fresh install on a cleaned up hardrive will resolve this messy problem. In the future I won’t mix Tumbleweed and Leap 15.4 software repositories.

To the op have you tried aria2c for downloading isos.
I use it all the time and never failed.

How is this related to any of the content or topic of this thread?


 > l -d /bin
drwxr-xr-x 2 root root 4096 10. Sep 18:41 /bin/
 > 
 > rpm --query --whatprovides /bin
filesystem-15.0-11.8.1.x86_64
 > 
 > rpm --query --whatprovides /bin/arch 
coreutils-8.32-150400.7.5.x86_64
 > 
 > l -d /sbin
drwxr-xr-x 2 root root 12288 11. Okt 18:33 /sbin/
 > 
 > rpm --query --whatprovides /sbin
filesystem-15.0-11.8.1.x86_64
 > 
 > rpm --query --whatprovides /sbin/agetty
util-linux-2.37.2-150400.8.3.1.x86_64
 > 

Are you trying to emulate Don Quijote?

  • These directories and the files located therein and, the linked files located therein, are installed with properties supplied by basic Linux System packages –
    If the Linux System as such, wishes to locate and link System Files in the manner provided by the System packages, then, that’s the way it is …

Further reading – the Linux Standard Base – <https://refspecs.linuxfoundation.org/lsb.shtml&gt; and, the Linux Filesystem Hierarchy Standard – <https://refspecs.linuxfoundation.org/fhs.shtml&gt;.