July 2024 - openSUSE Support - openSUSE Mailing Lists

can’t install PMDA for postfix
by chandan 18 Jul '24

18 Jul '24

Hello While installing pcp-pmda-postfix on Leap 15.6 i get the following error : cd /var/lib/pcp/pmdas/postfix/ ❯ la drwxr-xr-x root root 54 B Sun Jul 14 21:28:26 2024  . drwxr-xr-x root root 946 B Thu Jul 18 11:39:18 2024  .. lrwxrwxrwx root root 48 B Sun Jul 14 21:28:26 2024  Install ⇒ ../../../../../usr/lib/pcp/pmdas/postfix/Install lrwxrwxrwx root root 55 B Sun Jul 14 21:28:26 2024  pmdapostfix.pl ⇒ ../../../../../usr/lib/pcp/pmdas/postfix/pmdapostfix.pl lrwxrwxrwx root root 47 B Sun Jul 14 21:28:26 2024  Remove ⇒ ../../../../../usr/lib/pcp/pmdas/postfix/Remove ❯ sudo ./Install [sudo] password for root: Can't load '/usr/lib/perl5/vendor_perl/5.26.1/x86_64-linux-thread-multi/auto/PCP/PMDA/PMDA.so' for module PCP::PMDA: /usr/lib/perl5/vendor_perl/5.26.1/x86_64-linux-thread-multi/auto/PCP/PMDA/PMDA.so: undefined symbol: pmdaFetch at /usr/lib/perl5/5.26.1/x86_64-linux-thread-multi/DynaLoader.pm line 193. at -e line 1. Compilation failed in require at -e line 1. BEGIN failed--compilation aborted at -e line 1. Perl PCP::PMDA module is not installed, install it and try again Loading However i see perl-PCP-PMDA installed as below. repository data... Reading installed packages... S | Name | Summary | Type ---+---------------------+------------------------------------------------------------------------+-------- i+ | perl-PCP-LogImport | Performance Co-Pilot Perl bindings for importing external archive data | package i+ | perl-PCP-LogSummary | Performance Co-Pilot Perl bindings for processing pmlogsummary output | package i+ | perl-PCP-MMV | Performance Co-Pilot (PCP) Perl bindings for PCP Memory Mapped Values | package i | perl-PCP-PMDA | Performance Co-Pilot (PCP) Perl bindings and documentation | package Thanks Chandan

2 1

How to for setting up Virtual Machine Manager?
by ASSI 15 Jul '24

15 Jul '24

Is there a how-to for what to do so that virtual machine manager works without asking for root permissions every time it starts up? I guess my user should either be in some groups that confer the correct rights or that some configuration needs to be set up elsewhere. Related but probably a different problems: even when started as root it's not possible to hand through a USB stick to the VM with spice-client-glib-usb-acl-helper, which complaines about missing access rights. I have been able to attach a USB stick manually using virsh as root, though. If it matters, I use KVM as the hypervisor. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Samples for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra

2 1

[TW] No video in certain programs since upgrade of Mesa packages
by Bob Williams 14 Jul '24

14 Jul '24

Since the latest upgrades of the Mesa drivers, I have not been able to playback mp4 video files in mpv or web browsers (firefox). The audio channels work OK, and not every video viewer is affected, eg. VLC and Dragon can playback both video and audio. My video card is a Radeon RX 550 / 550 Series, system is Tumbleweed, display is wayland. Interestingly the same thing happens with Kdenlive. When I add a clip, only the audio channel is editable, the video channel is not loaded/available. Is this a known problem? Any suggested solutions? -- Bob Williams No HTML please. Plain text preferred. https://useplaintext.email/ http://www.catb.org/~esr/faqs/smart-questions.html

3 6

NetworkManager: conflict detected for IP address
by mh＠mike.franken.de 14 Jul '24

14 Jul '24

Hi *, recently I get NetworkManager: device (enp62s0): conflict detected for IP address 192.168.1.42 with host 38:14:28:F7:B5:B7 on boot. System is openSUSE Tumbleweed 20240711. $ ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever 2: enp62s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 64:4b:f0:10:7b:ce brd ff:ff:ff:ff:ff:ff inet 192.168.1.42/24 brd 192.168.1.255 scope global dynamic noprefixroute enp62s0 valid_lft 85744sec preferred_lft 85744sec inet6 fe80::7927:f93f:27df:dc99/64 scope link noprefixroute valid_lft forever preferred_lft forever 3: wlp0s20f3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 22:21:51:48:1f:45 brd ff:ff:ff:ff:ff:ff permaddr 20:1e: 88:d2:9f:5b 4: enp63s0u2u3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 38:14:28:f7:b5:b7 brd ff:ff:ff:ff:ff:ff So this is the ip from device enp62s0 and the mac from device enp63s0u2u3. But why does NM assume, enp63s0u2u3 has the same ip address? There is no entry in my arp cache or a dhcp lease pointing to that mac. Where does NM look for this mac/ip combination? TIA. Bye. Michael.

2 10

slowroll kernel removal voodoo
by Felix Miata 11 Jul '24

11 Jul '24

Sometime after booting 20240605 in order to upgrade, 5 locked kernel-defaults disappeared without any known action on my part to cause it: 6.3.9, 6.4.12, 6.5.9, 6.6.11 & 6.7.9. The only clues I can find that they were ever installed are their existing immutable initrds, and their backups, in /boot/. I've looked in /var/log/zypper.log, /var/log/zypp/history, journalctl, .bash_history and found not so much as a clue what could have made them disappear. Before I started the zypper dup process, I remember having somewhere around 85% of / in use. At the time I discovered the absence, it had dropped to 73%, proving they really had gone during the day, not some previous session. # zypper ll | grep kern 23 | kernel-de* | package | (any) | 24 | kernel-lo* | package | (any) | # grep "rpm -e" .bash_history | grep kernel rpm -e kernel-default-5.3.12-1.1 rpm -e kernel-default-5.3.12-1.1 time rpm -e /nfs/00srv/pub/Linux/Suse/Factory/kernel-default-5.18.11-1.1.x86_64.rpm time rpm -e /nfs/00srv/pub/Linux/Suse/Factory/kernel-default-5.18.11-1.1 time rpm -e /nfs/00srv/pub/Linux/Suse/Factory/kernel-default-5.18.11-1 time rpm -e kernel-default-5.18.11-1.1 time rpm -e /nfs/00srv/pub/Linux/Suse/Factory/kernel-default-5.18.11-1.1.x86_64.rpm time rpm -e /nfs/00srv/pub/Linux/Suse/Factory/kernel-default-5.18.11-1.1 time rpm -e /nfs/00srv/pub/Linux/Suse/Factory/kernel-default-5.18.11-1 time rpm -e kernel-default-5.18.11-1.1 # grep rm .bash_history | grep kernel zypper rm --clean-deps purge-kernels-service zypper rm purge-kernels-service chattr -i initrd-5.18.12-1-default; zypper rm kernel-default-5.18.12 chattr -i initrd-5.18.12-1-default; zypper rm kernel-default-5.18.12 zypper rm kernel-default-5.4.14 zypper rm kernel-default-5.4.14 zypper rm kernel-default-5.5.13 zypper rm kernel-default-5.6.14 zypper rm kernel-default-5.5.13 zypper rm kernel-default-5.6.14 dfh /; time zypper rm kernel-default-5.7.11 ; dfh / dfh /; time zypper rm kernel-default-5.8.15 ; dfh / dfh /; time zypper rm kernel-default-5.9.14 ; dfh / dfh /; time zypper rm kernel-default-5.7.11 ; dfh / dfh /; time zypper rm kernel-default-5.8.15 ; dfh / dfh /; time zypper rm kernel-default-5.9.14 ; dfh / zypper rm kernel-default-5.10.16 zypper rm kernel-default-5.10.16 time zypper rm kernel-default-6.1.8 time zypper rm kernel-default-6.1.8 time zypper rm kernel-default-6.1.8 time zypper rm kernel-default-6.1.8 zypper rm kernel-default-5.11.16 time zypper rm kernel-default-5.12.13 zypper rm kernel-firmware-sound kernel-firmware-platform kernel-firmware-media kernel-firmware-network zypper rm kernel-default-5.13.12 zypper rm kernel-default-5.11.16 time zypper rm kernel-default-5.12.13 zypper rm kernel-firmware-sound kernel-firmware-platform kernel-firmware-media kernel-firmware-network zypper rm kernel-default-5.13.12 zypper rm kernel-default-6.2.8 zypper rm kernel-default time rpm -ivh /nfs/00srv/pub/Linux/Suse/Factory/kernel-longterm-6.6.21-1.1.x86_64.rpm time rpm -ivh /nfs/00srv/pub/Linux/Suse/Factory/kernel-longterm-6.6.21-1.1.x86_64.rpm time rpm -ivh /nfs/00srv/pub/Linux/Suse/Factory/kernel-longterm-6.6.25-1.1.x86_64.rpm time rpm -ivh /nfs/00srv/pub/Linux/Suse/Factory/kernel-longterm-6.6.25-1.1.x86_64.rpm time rpm -ivh /nfs/00srv/pub/Linux/Suse/Factory/kernel-longterm-6.6.31-1.1.x86_64.rpm time rpm -ivh /nfs/00srv/pub/Linux/Suse/Factory/kernel-longterm-6.6.31-1.1.x86_64.rpm # lsattr /boot/initrd-6* ----i---------e------- /boot/initrd-6.3.9-1-default ----i---------e------- /boot/initrd-6.4.12-1-default ----i---------e------- /boot/initrd-6.5.9-1-default ----i---------e------- /boot/initrd-6.6.11-1-default ----i---------e------- /boot/initrd-6.6.21-1-longterm ----i---------e------- /boot/initrd-6.6.25-1-longterm ----i---------e------- /boot/initrd-6.6.31-1-longterm ----i---------e------- /boot/initrd-6.7.9-1-default ----i---------e------- /boot/initrd-6.8.9-1-default # ls -Ggl /boot/vmlinuz-6* /boot/initrd-6* -rw------- 1 17586190 Aug 11 2023 /boot/initrd-6.3.9-1-default -rw------- 1 15380244 Oct 13 2023 /boot/initrd-6.4.12-1-default -rw------- 1 15942348 Nov 15 2023 /boot/initrd-6.5.9-1-default -rw------- 1 16281120 Jan 24 22:22 /boot/initrd-6.6.11-1-default -rw------- 1 16146376 Mar 9 22:17 /boot/initrd-6.6.21-1-longterm -rw------- 1 16301820 Apr 16 00:09 /boot/initrd-6.6.25-1-longterm -rw------- 1 16386552 May 22 22:59 /boot/initrd-6.6.31-1-longterm -rw------- 1 16454412 Jun 13 23:31 /boot/initrd-6.7.9-1-default -rw------- 1 16514788 Jul 10 23:45 /boot/initrd-6.8.9-1-default lrwxrwxrwx 1 44 Mar 9 22:17 /boot/vmlinuz-6.6.21-1-longterm -> ../usr/lib/modules/6.6.21-1-longterm/vmlinuz lrwxrwxrwx 1 44 Apr 16 00:09 /boot/vmlinuz-6.6.25-1-longterm -> ../usr/lib/modules/6.6.25-1-longterm/vmlinuz lrwxrwxrwx 1 44 May 22 22:59 /boot/vmlinuz-6.6.31-1-longterm -> ../usr/lib/modules/6.6.31-1-longterm/vmlinuz lrwxrwxrwx 1 42 Jul 10 23:45 /boot/vmlinuz-6.8.9-1-default -> ../usr/lib/modules/6.8.9-1-default/vmlinuz # ls -gGld /usr/lib/modules drwxr-xr-x 7 1024 Jul 10 23:45 /usr/lib/modules # ls -gGl /usr/lib/modules total 5 drwxr-xr-x 2 1024 Jan 29 2023 5.5.13-1-default drwxr-xr-x 3 1024 Mar 9 22:17 6.6.21-1-longterm drwxr-xr-x 3 1024 Apr 16 00:09 6.6.25-1-longterm drwxr-xr-x 3 1024 May 22 22:59 6.6.31-1-longterm drwxr-xr-x 3 1024 Jul 10 23:45 6.8.9-1-default # systemctl list-unit-files | grep purge purge-kernels.service masked enabled # ls -gGl /etc/systemd/system/purge* lrwxrwxrwx 1 9 May 5 2019 /etc/systemd/system/purge-kernels.service -> /dev/null # rpm -qa | egrep 'nel-def|nel-lon' kernel-longterm-6.6.21-1.1.x86_64 kernel-longterm-6.6.25-1.1.x86_64 kernel-longterm-6.6.31-1.1.x86_64 kernel-default-6.8.9-1.1.x86_64 # journalctl | grep 'rpm -e' # journalctl | grep zypper Apr 15 23:37:58 gx780 [RPM][1851]: erase zypper-1.14.68-1.3.x86_64: success Apr 15 23:37:58 gx780 [RPM][1851]: install zypper-1.14.70-1.1.x86_64: success Apr 15 23:37:59 gx780 [RPM][1851]: erase zypper-1.14.68-1.3.x86_64: success Apr 15 23:37:59 gx780 [RPM][1851]: install zypper-1.14.70-1.1.x86_64: success Apr 15 23:53:13 gx780 [RPM][24779]: erase zypper-log-1.14.68-1.3.noarch: success Apr 15 23:53:13 gx780 [RPM][24779]: install zypper-log-1.14.70-1.1.noarch: success Apr 15 23:53:13 gx780 [RPM][24779]: erase zypper-log-1.14.68-1.3.noarch: success Apr 15 23:53:13 gx780 [RPM][24779]: install zypper-log-1.14.70-1.1.noarch: success May 22 22:41:15 gx780 [RPM][1428]: erase zypper-1.14.70-1.1.x86_64: success May 22 22:41:15 gx780 [RPM][1428]: install zypper-1.14.73-1.2.x86_64: success May 22 22:41:16 gx780 [RPM][1428]: erase zypper-1.14.70-1.1.x86_64: success May 22 22:41:16 gx780 [RPM][1428]: install zypper-1.14.73-1.2.x86_64: success May 22 22:50:49 gx780 [RPM][12448]: erase zypper-log-1.14.70-1.1.noarch: success May 22 22:50:49 gx780 [RPM][12448]: install zypper-log-1.14.73-1.2.noarch: success May 22 22:50:49 gx780 [RPM][12448]: erase zypper-log-1.14.70-1.1.noarch: success May 22 22:50:49 gx780 [RPM][12448]: install zypper-log-1.14.73-1.2.noarch: success Jul 10 23:35:33 gx780 [RPM][2495]: erase zypper-log-1.14.73-1.2.noarch: success Jul 10 23:35:33 gx780 [RPM][2495]: install zypper-log-1.14.76-1.1.noarch: success Jul 10 23:35:33 gx780 [RPM][2495]: erase zypper-log-1.14.73-1.2.noarch: success Jul 10 23:35:33 gx780 [RPM][2495]: install zypper-log-1.14.76-1.1.noarch: success Jul 10 23:37:45 gx780 [RPM][2922]: erase zypper-1.14.73-1.2.x86_64: success Jul 10 23:37:46 gx780 [RPM][2922]: install zypper-1.14.76-1.1.x86_64: success Jul 10 23:37:46 gx780 [RPM][2922]: erase zypper-1.14.73-1.2.x86_64: success Jul 10 23:37:46 gx780 [RPM][2922]: install zypper-1.14.76-1.1.x86_64: success # I've obviously self-limited data available by using rpm instead of zypper for most TW & SR kernel installations & removals. Digging through /var/log/zypper.log is a painful, unproductive, noisy process. I have no idea whether what I need to know is hidden in there or not. I searched for various strings I thought could be useful, but came up zip. This is the second time this has happened. The first time I sort of ignored it by reinstalling the removed kernels. Whether it was TW or SR I don't remember, nor when, but probably since last Christmas. Eventually I can probably find it by looking in /usr/lib/modules/ directories for a whole bunch of the same dates for disparate kernel versions, but because I have so many, sprawled across 40+ PCs, it would take quite some time. Anyone else have this happen? Any ideas what could cause unintentional removal of locked kernels? -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata

1 0

Akonadi crashing
by bing mybong 09 Jul '24

09 Jul '24

Hi I have previously sent this to the kdepim-users list. I've had increasing issues with this to the point Akonadi does not load any more (only on one of my logins) I'm with BTinternet and increasingly over the last few weeks, it occasionally reports a corruption with the BT internet IMAP but works when you reload kmail. It now doesn't load at all and keeps core dumping. Can anyone tell from this journaltctl log what the problem is? https://paste.opensuse.org/pastes/5bf017867d16 <https://paste.opensuse.org/pastes/5bf017867d16> I think i'm going have to create a new user. thanks regards Ian

2 4

element (matrix client) suddenly drops firefox ESR support, can we please get firefox ESR 128 support early for leap 15.6?
by cagsm 08 Jul '24

08 Jul '24

Support, all of a sudden, todays element (matrix client) drops the inofficial support of Firefox ESR (115.x) that worked just hours (one version of element) ago. <https://github.com/element-hq/element-web/issues/27684> there is a buzz about this on github at their project also affecting current debian which also ships similar 115 firefox ESR as opensuse. any chance we get firefox next ESR (due tomorrow 128.x for the first time) early into leap 15.6? <https://wiki.mozilla.org/Release_Management/Calendar> very odd for matrix/elements project to make such a sudden change and not informing userbase about this. thanks for considering this as a prio. thanks much in advance.

1 0

Intel_vpu firmware
by Michael Bednowicz 04 Jul '24

04 Jul '24

I just installed Tumbleweed on a new laptop. ~> journalctl -b | grep firmware is show an error for one intel_vpu. *ERROR* ivpu_fw_request(): Failed to request firmware: -2 Does this mean that there is no firmware driver for that device? Or does it mean something else? My CPU is a Intel Ultra 185H (MeteorLake). From what I can find, that device has to do with AI functions on the CPU. I know that's new stuff, and support for these CPUs just came out on kernel 6.9. Is there something I need to do to get this firmware?

3 3

Kalpa Question
by Axel Braun 01 Jul '24

01 Jul '24

Hi, during oSC I decided for a test run of Kalpa in a VM. I installed Kontact using Discover, so it probably runs inside a container - how can I find out which container it is? - How can I get inside the container (to run akonadictl)? Thanks Axel

1 0