The first is that the zypper is very slow and significantly slows down the system to the point of freezing it for several ten seconds.
I had several episodes of corrupted journals with systemd-journald.service without knowing if it was this event that created the problem with zypper. But a ‘rm’ on corrupted logs with a restart ‘’ fixed systemd-journald.service without resolving Zypper’s extreme slowness.
I admit that I didn’t have the presence of mind to take a time to quantify what I said.
I take advantage of the chapter to inform you that I have a lot of errors in green writing to indicate that links to files that do not exist are impossible.
By the way, why are the typing errors during compilations missing already installed files?
My most serious problem concerns Bitwarden which no longer works and displays a white window.
Checking for file conflicts: …[done]
( 1/24) Installing: libvdpau_nouveau-23.2.0-1699.360.pm.1.x86_64 …[done]
( 2/24) Installing: Mesa-KHR-devel-23.2.0-1699.360.pm.1.x86_64 …[done]
/sbin/ldconfig: /lib/libhid.so.0.0 is for unknown machine 40.
/sbin/ldconfig: /lib/libhid.so.0 is not a symbolic link
/sbin/ldconfig: /lib64/libhid.so.0.0 is for unknown machine 40.
/sbin/ldconfig: /lib64/libhid.so.0 is not a symbolic link
/sbin/ldconfig: /lib/libhid.so.0.0 is for unknown machine 40.
/sbin/ldconfig: /lib/libhid.so.0 is not a symbolic link
/sbin/ldconfig: /lib64/libhid.so.0.0 is for unknown machine 40.
/sbin/ldconfig: /lib64/libhid.so.0 is not a symbolic link
( 3/24) Installing: libgbm1-23.2.0-1699.360.pm.1.x86_64 …[done]
/sbin/ldconfig: /lib/libhid.so.0.0 is for unknown machine 40.
/sbin/ldconfig: /lib/libhid.so.0 is not a symbolic link
/sbin/ldconfig: /lib64/libhid.so.0.0 is for unknown machine 40.
/sbin/ldconfig: /lib64/libhid.so.0 is not a symbolic link
/sbin/ldconfig: /lib/libhid.so.0.0 is for unknown machine 40.
/sbin/ldconfig: /lib/libhid.so.0 is not a symbolic link
/sbin/ldconfig: /lib64/libhid.so.0.0 is for unknown machine 40.
/sbin/ldconfig: /lib64/libhid.so.0 is not a symbolic link
( 4/24) Installing: Mesa-libglapi0-23.2.0-1699.360.pm.1.x86_64 …[done]
( 5/24) Installing: Mesa-libRusticlOpenCL-23.2.0-1699.360.pm.1.x86_64 …[done]
( 6/24) Installing: Mesa-vulkan-device-select-23.2.0-1699.360.pm.1.x86_64 …[done]
( 7/24) Installing: Mesa-libOpenCL-23.2.0-1699.360.pm.1.x86_64 …[done]
( 8/24) Installing: Mesa-libva-23.2.0-1699.360.pm.1.x86_64 …[done]
( 9/24) Installing: libgbm-devel-23.2.0-1699.360.pm.1.x86_64 …[done]
/sbin/ldconfig: /lib/libhid.so.0.0 is for unknown machine 40.
/sbin/ldconfig: /lib/libhid.so.0 is not a symbolic link
/sbin/ldconfig: /lib64/libhid.so.0.0 is for unknown machine 40.
/sbin/ldconfig: /lib64/libhid.so.0 is not a symbolic link
/sbin/ldconfig: /lib/libhid.so.0.0 is for unknown machine 40.
/sbin/ldconfig: /lib/libhid.so.0 is not a symbolic link
/sbin/ldconfig: /lib64/libhid.so.0.0 is for unknown machine 40.
/sbin/ldconfig: /lib64/libhid.so.0 is not a symbolic link
(10/24) Installing: Mesa-libEGL1-23.2.0-1699.360.pm.1.x86_64 …[done]
/sbin/ldconfig: /lib/libhid.so.0.0 is for unknown machine 40.
/sbin/ldconfig: /lib/libhid.so.0 is not a symbolic link
/sbin/ldconfig: /lib64/libhid.so.0.0 is for unknown machine 40.
/sbin/ldconfig: /lib64/libhid.so.0 is not a symbolic link
/sbin/ldconfig: /lib/libhid.so.0.0 is for unknown machine 40.
/sbin/ldconfig: /lib/libhid.so.0 is not a symbolic link
/sbin/ldconfig: /lib64/libhid.so.0.0 is for unknown machine 40.
/sbin/ldconfig: /lib64/libhid.so.0 is not a symbolic link
(11/24) Installing: libOSMesa8-23.2.0-1699.360.pm.1.x86_64 …[done]
(12/24) Installing: Mesa-libglapi-devel-23.2.0-1699.360.pm.1.x86_64 …[done]
(13/24) Installing: libvulkan_intel-23.2.0-1699.360.pm.1.x86_64 …[done]
(14/24) Installing: Mesa-dri-23.2.0-1699.360.pm.1.x86_64 …[done]
/sbin/ldconfig: /lib/libhid.so.0.0 is for unknown machine 40.
/sbin/ldconfig: /lib/libhid.so.0 is not a symbolic link
/sbin/ldconfig: /lib64/libhid.so.0.0 is for unknown machine 40.
/sbin/ldconfig: /lib64/libhid.so.0 is not a symbolic link
/sbin/ldconfig: /lib/libhid.so.0.0 is for unknown machine 40.
/sbin/ldconfig: /lib/libhid.so.0 is not a symbolic link
/sbin/ldconfig: /lib64/libhid.so.0.0 is for unknown machine 40.
/sbin/ldconfig: /lib64/libhid.so.0 is not a symbolic link
(15/24) Installing: Mesa-23.2.0-1699.360.pm.1.x86_64 …[done]
/sbin/ldconfig: /lib/libhid.so.0.0 is for unknown machine 40.
/sbin/ldconfig: /lib/libhid.so.0 is not a symbolic link
/sbin/ldconfig: /lib64/libhid.so.0.0 is for unknown machine 40.
/sbin/ldconfig: /lib64/libhid.so.0 is not a symbolic link
/sbin/ldconfig: /lib/libhid.so.0.0 is for unknown machine 40.
/sbin/ldconfig: /lib/libhid.so.0 is not a symbolic link
/sbin/ldconfig: /lib64/libhid.so.0.0 is for unknown machine 40.
/sbin/ldconfig: /lib64/libhid.so.0 is not a symbolic link
(16/24) Installing: Mesa-libGL1-23.2.0-1699.360.pm.1.x86_64 …[done]
(17/24) Installing: Mesa-libEGL-devel-23.2.0-1699.360.pm.1.x86_64 …[done]
(18/24) Installing: libOSMesa-devel-23.2.0-1699.360.pm.1.x86_64 …[done]
(19/24) Installing: Mesa-libGL-devel-23.2.0-1699.360.pm.1.x86_64 …[done]
(20/24) Installing: Mesa-gallium-23.2.0-1699.360.pm.1.x86_64 …[done]
(21/24) Installing: Mesa-libGLESv1_CM-devel-23.2.0-1699.360.pm.1.x86_64 …[done]
(22/24) Installing: Mesa-libGLESv2-devel-23.2.0-1699.360.pm.1.x86_64 …[done]
(23/24) Installing: Mesa-dri-devel-23.2.0-1699.360.pm.1.x86_64 …[done]
(24/24) Installing: Mesa-devel-23.2.0-1699.360.pm.1.x86_64 …[done]
There are running programs which still use files and libraries deleted or updated by recent upgrades. They should be restarted to benefit from the latest updates. Run ‘zypper ps -s’ to list these programs.
Given that, Bitwarden is freemium open-source password management service and, there doesn’t seem to be a related package in the openSUSE repositories, you may have to contact Bitwarden Inc. for support.
Please be aware that, if, you haven’t been taking backups of your password keys (such backups have to be stored on a removable device which you normally keep locked away in a physically safe place), you’ll probably experience some pain if you have to reinstall that application …
@hui
your commande :
LC_ALL=C zypper se --provides libhid.so.0
Refreshing service ‘NVIDIA’.
Refreshing service ‘openSUSE’.
Loading repository data…
Reading installed packages…
No matching items found.
my default repositories which were updated with kernel 6.5 :
zypper lr
Repository priorities are without effect. All enabled repositories share the same priority.
Please use the “Preformatted text” feature of the forums posting software. It is the button </> in the toolbar of the post editor. Select your copied/pasted computer text and hit that button.
Please when you want to inform us about a repository list, then use a command that provides the URLs, like
zypper lr -d
Now we have only Names and Aliases that are local to your system. They may hint to what the repos are, but we are not sure.
There was an option informing me that the repositories were going to be updated automatically and the Nvidia driver was compiled without me being asked about this modification.
Besides, there are a lot of errors dracut asks for “menstrack” (from memory) and it is not installed. Same for other modules.
I checked with Yast, they are all installed.
It is completely normal that dracut informs you about missing modules. Only the necessary modules which are needed to talk with your hardware/(software) are installed and used by dracut. All other modules which are not needed for your hardware/(software), are not installed and dracut only issues an informational message whilst building initrd.
At a guess, your system uses the Btrfs filesystem for the system directories and therefore, the Btrfs filesystem command is better suited to determine the amount of free space available –
zypper se bitwarden
Refreshing service 'NVIDIA'.
Refreshing service 'openSUSE'.
Loading repository data...
Reading installed packages...
S | Name | Summary | Type
---+-----------+------------------------------------------------------------+--------
i+ | bitwarden | A secure and free password manager for all of your devices | package