Hi: This is odd - Yast wants to update Chromium but then reports nothing supplies the required libxkbcommon.so.0(V_1.0.0)(64bit) - so the only option is to deinstall chromium (or “break” it).
I’ve waited a week or so, but this still happens (and now there are 2 such patches). Search doesn’t reveal much discussion of this, so something’s obviously wrong with my system - ideas how to trouble-shoot? Other updates won’t go without resolving this one.
Thanks,
Patti
#### YaST2 conflicts list - generated 2022-04-20 18:17:14 ####
nothing provides 'libxkbcommon.so.0(V_1.0.0)(64bit)' needed by the to be installed chromium-100.0.4896.127-bp153.2.85.1.x86_64
] Following actions will be done:
do not install patch:openSUSE-2022-112-1.noarch
do not install patch:openSUSE-2022-114-1.noarch
] deinstallation of chromium-99.0.4844.84-bp153.2.75.1.x86_64
] break chromium-100.0.4896.127-bp153.2.85.1.x86_64 by ignoring some of its dependencies
#### YaST2 conflicts list END ###
Looking at the system that I checked, the package “libxkbcommon0” (version 1.3.0-150300.10.3.1) seems to provide the library mentioned. You might see what happens if you try to install just that package.
YaST2 conflicts list - generated 2022-04-20 18:17:14
nothing provides ‘libxkbcommon.so.0(V_1.0.0)(64bit)’ needed by the to be installed **chromium-100.0.4896.127-bp153.2.85.1.x86_64
**
] Following actions will be done:
do not install patch:openSUSE-2022-112-1.noarch
do not install patch:openSUSE-2022-114-1.noarch
] deinstallation of chromium-99.0.4844.84-bp153.2.75.1.x86_64
] break chromium-100.0.4896.127-bp153.2.85.1.x86_64 by ignoring some of its dependencies
It is still unclear where this conflict comes from. This sounds like chromium-99.0.4844.84-bp153.2.75.1 blocks update of libxkbcommon0, but chromium-99.0.4844.84-bp153.2.75.1 requires libxkbcommon.so.0()(64bit) and libxkbcommon.so.0(V_0.5.0)(64bit) which are still provided by libxkbcommon0-1.3.0-150300.10.3.1. It would be interesting to see generated solver debug information (zypper patch --debug-solver, see man zypper for details).
Thank You! Searching in Yast, this is what I find…
# Status Package | Summary | Installed (Available) | 5
[Keep] libxkbcommon0 | Library for handling xkb descriptions | 0.8.2-3.3.1 | 277.4 KiB
[Do Not Install] libxkbcommon0-32bit | Library for handling xkb descriptions | (0.8.2-3.3.1) | 269.8 KiB
I can’t interpret the version number from Yast in relation to your version number, but it is installed. I tried updating libxkbcommon0 in Yast, but afterward chromium still won’t install the Security Patches - same error. When I choose to not update chromium in Online Update in Yast (to try to bypass the problem), then there are no other “Security Updates” listed in “Needed Patches.” But when I select “All Patches,” I see lots of updates, including many security updates. These don’t/won’t install after deselecting the chromium Security Update. This seems odd and unsafe as other listed security updates apparently aren’t being installed. Color me confused.
Thanks much - I’m not sure how to debug but I’ll fiddle with it… What do you think of the idea of deinstalling the old chromium then installing the updated version?
Loading repository data...
Warning: Repository 'openSUSE:Backports:SLE-15-SP3' appears to be outdated. Consider using a different mirror or server.
Reading installed packages...
Resolving package dependencies...
Generating solver test case...
Solver test case generated successfully at /var/log/zypper.solverTestCase.
**linux-lhkc:/home/patti #** cat /var/log/zypper.solverTestCase
cat: /var/log/zypper.solverTestCase: Is a directory
**linux-lhkc:/home/patti #** cd /var/log/zypper.solverTestCase
**linux-lhkc:/var/log/zypper.solverTestCase #** ls
brave-browser.repo.gzopenSUSE_Leap_15.3_1.repo.gzrepo-oss.repo.gz testcase.t
http-download.opensuse.org-327dee1b.repo.gzopenSUSE_Leap_15.3_2.repo.gzrepo-update-non-oss.repo.gz y2log
http-ftp.gwdg.de-4e218b07.repo.gzopenSUSE_Leap_15.3.repo.gzrepo-update.repo.gz zypp-autoinst.yaml
http-opensuse-guide.org-2fd9014a.repo.gzrepo-backports-update.repo.gz solver.result zypp-control.yaml
https-download.opensuse.org-ee923ad5.repo.gzrepo-non-oss.repo.gz@System.repo.gz zypp-modalias.yaml
**linux-lhkc:/var/log/zypper.solverTestCase #** cat solver.result
erase chromium-99.0.4844.84-bp153.2.75.1.x86_64@@System
install patch:openSUSE-2022-114-1.noarch@repo-backports-update
problem 3651721b info nothing provides libxkbcommon.so.0(V_1.0.0)(64bit) needed by chromium-100.0.4896.127-bp153.2.85.1.x86_64
problem 3651721b solution 59b20342 deljob install pkg patch:openSUSE-2022-112-1.noarch@repo-backports-update
problem 3651721b solution 59b20342 deljob install pkg patch:openSUSE-2022-114-1.noarch@repo-backports-update
problem 3651721b solution 5dc2f374 erase chromium-99.0.4844.84-bp153.2.75.1.x86_64@@System
**linux-lhkc:/var/log/zypper.solverTestCase #**
OK. now it is clear what happens. Patch explicitly conflicts with earlier versions of packages that are “patched” thus forcing their removal. So on one hand installing patch removes currently installed chromium (which is exactly what patch is designed to do) but on the other hand newer version of chromium cannot be installed due to missing libxkbcommon0 update.
Well, zypper (or whatever GUI you are using) actually gave you the correct choice of not installing patch. Whether choice of removing existing chromium version without installing update is justified in this case is open to discussion. You may consider opening bug report.
But technically there is no bug and everything behaves as designed. Check mirrors you are using, may be they do not get update for some time.
Well, it does look better now to my inexperienced eyes. I guess I’ll try uninstalling the old version of chromium then reinstalling the latest version. Hmmm… Don’t want to accidentally blow away all my chromium settings.
**linux-lhkc:/var/log/zypper.solverTestCase #** zypper patch --debug-solver
Loading repository data...
Warning: Repository 'openSUSE:Backports:SLE-15-SP3' appears to be outdated. Consider using a different mirror or server.
Reading installed packages...
Resolving package dependencies...
Generating solver test case...
Solver test case generated successfully at /var/log/zypper.solverTestCase.
**linux-lhkc:/var/log/zypper.solverTestCase #** cat solver.result
erase chromium-99.0.4844.84-bp153.2.75.1.x86_64@@System
install patch:openSUSE-2022-114-1.noarch@repo-backports-update
problem 3651721b info nothing provides libxkbcommon.so.0(V_1.0.0)(64bit) needed by chromium-100.0.4896.127-bp153.2.85.1.x86_64
problem 3651721b solution 59b20342 deljob install pkg patch:openSUSE-2022-112-1.noarch@repo-backports-update
problem 3651721b solution 59b20342 deljob install pkg patch:openSUSE-2022-114-1.noarch@repo-backports-update
problem 3651721b solution 5dc2f374 erase chromium-99.0.4844.84-bp153.2.75.1.x86_64@@System
**linux-lhkc:/var/log/zypper.solverTestCase #**
OK, I uninstalled chromium then tried to install the latest version.
#### YaST2 conflicts list - generated 2022-04-21 11:54:54 ####
nothing provides 'libxkbcommon.so.0(V_1.0.0)(64bit)' needed by the to be installed chromium-100.0.4896.127-bp153.2.85.1.x86_64
] break chromium-100.0.4896.127-bp153.2.85.1.x86_64 by ignoring some of its dependencies
] do not install chromium-100.0.4896.127-bp153.2.85.1.x86_64
#### YaST2 conflicts list END ###
17 | repo-sle-update | Update repository with updates from SUSE Linux Enterprise 15 | Ja | (r ) Ja | Ja | 99 | rpm-md | http://download.opensuse.org/update/leap/15.3/sle/ |
You miss SLE updates repository which means you miss updates to core packages (actually most updates are from this repository). I do not know how you managed it (repository definition is installed automatically by openSUSE-release package update) unless you deliberately removed this definition.
There were some packages - for instance, Signal messenger - which wanted other repos for one click install. I’m a little uncomfortable installing but can’t find an Opensuse build of Signal Desktop - I use that constantly. Suggestions for Signal Desktop?
I didn’t remove except maybe by accident, any installer-installed repos (including updates). I’d better fix that right away. Do you know a link to a web page with the latest repos for 15.3? Pages such as:
…and such web pages are pretty confusing since I normally only use a couple of extra repos (packman, science) in addition to the stock installer-installed LEAP repos.
I’m not sure what’s going on here… it’s still absolute magic that anyone can find these sorts of things in some (obscure?) repo. I see this time and time again. Most of the internet searches return nothing useful. Not sure why I have such bad luck. How did you find this repo? For instance, there was also a repo for HAM radio apps which I knew nothing about - an admin here did. Internet searches turned up nothing.
**linux-lhkc:/home/patti #** zypper lr -d Signal
Repository 'Signal' not found by its alias, number, or URI.
Use 'zypper repos' to get the list of defined repositories.
**linux-lhkc:/home/patti #** LANG=C zypper lr -d Signal
Repository 'Signal' not found by its alias, number, or URI.
Use 'zypper repos' to get the list of defined repositories.
**linux-lhkc:/home/patti #**
Still need to solve the chromium noninstall problem.