Hello. I became aware of a problem on August 31, 2023, probably while my computer was connected to the Internet, after I was informed that a Security update for webkit2gtk3, associated with openSUSE-SLE-15.5-2023-3419-1, was available online for installation. But after agreeing to the installation of that update I was informed that “the installed WebKit2GTK-4.1-lang-2.38.6-150400.4.42.4.noarch requires WebKit2GTK-4.1=2.38.6, but this requirement cannot be provided.” Please look at the Screenshot_2023-08-31_19-46-32.png, Portable Network Graphics (.png) file from a picture I took of the installed and available WebKit2GTK-related software packages for my installation of a 64-bit, openSUSE, Leap 15.5, Linux operating system, probably while my computer was connected to the Internet. And please inform me which ones of the various WebKit2GTK- or webkit2GTK-related software packages I should keep or update and which ones among them I should delete. Notice that the software package libwebkit2gtk3, version 2.38.6-150200.72.1, has its version in red-colored text. I found that it was installed on June 16, 2023 when I upgraded Leap 15.4 to Leap 15.5; and for its “Distribution” I saw “SUSE Linux Enterprise 15”. That software package might have come from within my Leap-15.4 installation among 587 updates to my Leap-15.4 installation that I installed prior to upgrading that same day from Leap 15.4 to Leap 15.5. In contrast the software package WebKit2GTK-4.0-lang, version 2.38.6-150400.4.42.4, was installed in my Leap-15.5 installation on June 28, 2023, 12 days after I upgraded from Leap 15.4 to Leap 15.5. For its “Distribution” I saw “SUSE Linux Enterprise”. When my computer was not connected to the Internet each of the software packages libwebkit2gtk3, version 2.38.6-150200.72.1, and WebKit2GTK-4.0-lang, version 2.38.6-150400.4.42.4, was listed as a so-called “orphaned” software package among numerous other software packages. However, later when my computer was connected to the Internet neither one of those software packages
was listed as “orphaned”; and the list of “orphaned” software packages might have been shorter than when my computer was not connected to the Internet. And no matter whether my computer was connected to the Internet or not, neither one of those software packages was listed among a short list of “Unneeded Packages” in YaST (Yet another Software Tool) Software. Seeing versions 3, 4.0, and 4.1 of some WebKit2GTK-related software packages installed in my Leap-15.5 installation makes me think that I may have too many WebKit2GTK-related software packages installed in my Leap-15.5 installation. So again please inform me which ones among the various WebKit2GTK- or webkit2GTK-software packages I should keep or update and which ones among them I should delete.
Thank you very much, poster hui, for kindly and promptly taking some time to read and respond to my posting here! I followed poster Michael Balzer’s successful procedure in the bugzilla report-number 1214640 on 1214640 – Dependency issue with WebKit2GTK in patch:openSUSE-SLE-15.4-2023-3419-1.noarch on the Internet, which was to delete or uninstall the software packages WebKit2GTK-4.1-lang, version 2.38.6-150400.4.42.4.noarch, and WebKit2GTK-4.0-lang, version 2.38.6-150400.4.42.4.noarch, and afterward to install probably the “Security update for webkit2gtk3”, associated with openSUSE-SLE-15.5-2023-3419-1. And gratefully Michael Balzer’s procedure worked for me as well, even in uninstalling libwebkit2gtk3-lang with the previous, red-text version number 2.38.6-150200.72.1! So that makes me think that my earlier suspicion, that that latter software package could have been left over from my previous, Leap-15.4 installation before upgrading it to Leap 15.5, could have been incorrect. Now my list of installed and some available WebKit-related software packages is in my included, new picture taken with Leap 15.5’s application “Screenshot”. Notice in that picture that just below my list of installed, WebKit-related software packages are the names of the two software packages WebKit2GTK-4.0-lang and WebKit2GTK-4.1-lang, with each of them of version version 2.38.6-150400.4.42.4, that I uninstalled today, according to Michael Balzer’s procedure, and that the names of those software packages are not quite the same as the names of the two software packages WebKitGTK-4.0-lang and WebKitGTK-4.1-lang at the top of the list of my now-installed, WebKit-related software packages; yet the version number for each of these latter two software packages is the higher number 2.40.5-150400.4.45.3. So Michael Balzer’s thinking that there may have been a name change in two WebKit-related software packages from perhaps version 2.38.6-150400.4.42.4 to 2.40.5-150400.4.45.3 looks likely.
And he wondered whether such a name change might have caused the earlier problem that at least he and I probably had while attempting to install the “Security update for webkit2gtk3,” associated with “openSUSE-SLE-15.5-2023-3419-1”. Not being well acquainted with any of the relevant computer codes, I cannot write that that was the cause of the earlier problem. But with ignorance of the details of the relevant computer codes, as an “outsider” it appears to me that Michael Balzer’s wondering or guess of that possible cause for the earlier problem may be reasonable. And, assuming that there was a name change, it even seems possible to me that such a change in a name, in part from WebKit2GTK to WebKitGTK, might not have even been intentional. But, of course, I could be incorrect in such a speculation.
(Updating with a direct solution because this might be the 1st result on Google for most people)
The issue is the package was renamed, but there are apparently lingering references to the old package.
As I understand it, there is a hands-off patch in the works from openSUSE, but apparently the fix they already came up with itself requires another fix. It’s been so long that I was no longer willing to wait.
Given this situation, you can easily solve this by following this thread:
To summarize, first check first if you have the renamed package installed already (it should be called something like WebKitGTK-4.1-lang). See sample output below where I checked this with zypper patch:
andrew@localhost:~> zypper se -s webkit2gtk webkitgtk | grep -i lang
| WebKit2GTK-4.0-lang | package | 2.38.6-150400.4.42.4 | noarch | Update repository with updates from SUSE Linux Enterprise 15
| WebKit2GTK-4.0-lang | package | 2.38.6-150400.4.39.1 | noarch | Main Repository
| WebKit2GTK-4.1-lang | package | 2.38.6-150400.4.42.4 | noarch | Update repository with updates from SUSE Linux Enterprise 15
| WebKit2GTK-4.1-lang | package | 2.38.6-150400.4.39.1 | noarch | Main Repository
| WebKit2GTK-5.0-lang | package | 2.38.6-150400.4.42.4 | noarch | Update repository with updates from SUSE Linux Enterprise 15
| WebKit2GTK-5.0-lang | package | 2.38.6-150400.4.39.1 | noarch | Main Repository
i | WebKitGTK-4.0-lang | package | 2.40.5-150400.4.48.1 | noarch | Update repository with updates from SUSE Linux Enterprise 15
v | WebKitGTK-4.0-lang | package | 2.40.5-150400.4.45.3 | noarch | Update repository with updates from SUSE Linux Enterprise 15
i | WebKitGTK-4.1-lang | package | 2.40.5-150400.4.48.1 | noarch | Update repository with updates from SUSE Linux Enterprise 15
v | WebKitGTK-4.1-lang | package | 2.40.5-150400.4.45.3 | noarch | Update repository with updates from SUSE Linux Enterprise 15
| WebKitGTK-6.0-lang | package | 2.40.5-150400.4.48.1 | noarch | Update repository with updates from SUSE Linux Enterprise 15
| WebKitGTK-6.0-lang | package | 2.40.5-150400.4.45.3 | noarch | Update repository with updates from SUSE Linux Enterprise 15
(Note, this may already be installed almost universally for people, but it’s always worth checking in advance).
If you have it, then proceed to run
sudo zypper patch
and when prompted, choose the option “deinstallation of WebKit2GTK-4.1-lang-2.38.6-150400.4.42.4…”.
It’s been so long that I was no longer willing to wait.