Opensuse-sle-15-4-2023-796 (1)

I have a security update for Leap pending called opensuse-sle-15-4-2023-796 (1) this update has allot of information to install and I would like to know the following

  1. how can I find details on the update? The screen shows description but it is not easy to read and I can’t copy the description information to a text reader.

  2. the date on the title suggest it is for the date April-15-2023 it is currently March-17-2023, why a future date is it a valid update ?

Please provide input/output from sudo zypper lr -d. Good chance you have an inappropriate repo enabled.

A separately good chance is that the problem will disappear if you do:

	sudo zypper ref
	sudo zypper up

It’s a kernel update. And there are already several reports of problems with the kernel it provides. I recommend that you do not use this update.

The “2023” part refers to the year. But the “15-4” refers to Leap 15.4 or SLE 15 service pack 4. You have misinterpreted that as a date.

Such update does not exist.

zypper info -t patch openSUSE-SLE-15.4-2023-796

This is a fresh install just yesterday of Leap 15.4 ISO. The repos are default. I noticed that Bluetooth from the directory /usr/bin does not exist. I will not change anything yet I will run the other 2 commands later.

zypper lr -d

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

1 | openSUSE-Leap-15.4-1 | openSUSE-Leap-15.4-1 | Yes | (r ) Yes | No | 99 | rpm-md | cd:/?devices=/dev/disk/by-id/usb-HL-DT-ST_DVDRAM_GP65NW60_M08JCQL1856-0:0 |
2 | repo-backports-debug-update | Update repository with updates for openSUSE Leap debuginfo packages from openSUSE Backports | No | ---- | ---- | 99 | NONE | |
3 | repo-backports-update | Update repository of openSUSE Backports | Yes | (r ) Yes | Yes | 99 | rpm-md | |
4 | repo-debug | Debug Repository | No | ---- | ---- | 99 | NONE | |
5 | repo-debug-non-oss | Debug Repository (Non-OSS) | No | ---- | ---- | 99 | NONE | |
6 | repo-debug-update | Update Repository (Debug) | No | ---- | ---- | 99 | NONE | |
7 | repo-debug-update-non-oss | Update Repository (Debug, Non-OSS) | No | ---- | ---- | 99 | NONE | |
8 | repo-non-oss | Non-OSS Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | |
9 | repo-oss | Main Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | |
10 | repo-sle-debug-update | Update repository with debuginfo for updates from SUSE Linux Enterprise 15 | No | ---- | ---- | 99 | NONE | |
11 | repo-sle-update | Update repository with updates from SUSE Linux Enterprise 15 | Yes | (r ) Yes | Yes | 99 | rpm-md | |
12 | repo-source | Source Repository | No | ---- | ---- | 99 | NONE | |
13 | repo-update | Main Update Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | |
14 | repo-update-non-oss | Update Repository (Non-Oss) | Yes | (r ) Yes | Yes | 99 | rpm-md | |

I will also enclose the GPG public keys.

Your repos are OK…

The exact file name is Opensuse-SLE-15.4-2023-796 (1) which your command zypper info -t patch Opensuse-SLE-15.4-2023-796 (1) will not work. Removing (1) at the end it works. Is the update invalid because of the (1)?

No, it is not. Even disregarding (1).
You shouldn’t apply this patch as it will update to a kernel version which has some problems. Fix is on the way. Kernel will be retracted soon. Use forum search for more information regarding the kernel problem…

1 Like

Can you tell me how you know its invalid ?

Simple check all the message about it here in the Install/boot/logon sections . definite problem. :sob:

The patch openSUSE-SLE-15.4-2023-796 got already retracted, so it is not available anymore for installation.

I asked how do you know there is a problem with the security patch?

If this patch is already installed what happens ?

Can a view of all security patches installed be viewed through Software management ?

There are already several threads and bug reports about this update.

If it is working for you, then you need not be concerned. For some people, the new kernel fails to boot their computer. I’m pretty sure you would have noticed if the affected you.

I have installed both on a virtual machine and a physical machine. I hav enoticed the problem with booting that is why I am asking about the details of this issue.

I was the one that asked about that security patch and was told there is a problem and the users of this post asked me form a confirmation of my workstation information so the forum member was also not aware.

Can you provide me with the details of this security patch issue? I have a Virtual machine that has the security patch installed and would like to know how can I view existing installed security patches. How is this security patch which had about 30 items installed be removed ?

I don’t have the patch installed here. And it is now retracted.

I did check, and from memory it was a kernel update. That would include:


If you installed 30 updates, some of them were from different patches. You can look at “/var/log/zypp/history” to see what was installed at that time.

Another thought on this.

Use Yast Software Management.

Click on “View” and select “Package Classification”

Then click on “Retracted Installed Packages”. That should list what installed from this now-retracted patch. It doesn’t show anything here, because I have not installed that patch on this system.

If your system is booting normally, then I would not do anything until there is a newer kernel update. If your system is not booting normally, then you can boot from the previous kernel, follow the above steps and remove all of those retracted installed packages. To boot the previous kernel, use the “Advanced …” line in the grub boot menu.

The name of the security update does not show in the package retraction and I see it installed in the history log.

What is a user to do if they installed this bad security patch ?

Goto Version in your Picture, scroll down the Version list and the last one is the bad kernel.
You can delete this by clicking in the green field of the Versions list.