June 2021 - openSUSE Users - openSUSE Mailing Lists

shouldnt sle(s) based packages on 15.3 be not handled via a sp3 named directory instead of sp2?
by cagsm 02 Jun '21

02 Jun '21

hi there, === ( 5/72) Installing: libcurl-devel-7.66.0-4.17.1.x86_64 ................................................................................................................................................................[done] Additional rpm output: warning: /var/cache/zypp/packages/repo-sle-update/sle-sp2/x86_64/libcurl-devel-7.66.0-4.17.1.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 39db7c82: NOKEY ( 6/72) Installing: libcurl4-32bit-7.66.0-4.17.1.x86_64 ...............................................................................................................................................................[done] Additional rpm output: warning: /var/cache/zypp/packages/repo-sle-update/sle-sp2/x86_64/libcurl4-32bit-7.66.0-4.17.1.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 39db7c82: NOKEY === this is happening inside a zypper up on a current leap 15.3 today. shouldnt that var cache directory be named sle-sp3 (which also exists in that folder structures already) and instead? is my understanding of what leap 15.3 and suse linux enterprise 15 sp2 and sp3 are, wrong? ty.

2 1

15.3, firing up konqueror, brings defective startup page, unknown konq protocol
by cagsm 02 Jun '21

02 Jun '21

this 15.3 test system, which came from 15.2 before, maybe even 15.1 before that. pretty much never before having used konqueror on this machine, firing it up today only renders that error message that unknown protocol konq cannot create io-slave === The requested operation could not be completed Cannot Initiate the konq Protocol Technical Reason: Unable to Create io-slave Details of the Request: URL: konq:konqueror Protocol: konq Date and Time: Wednesday, June 2, 2021 Additional Information: klauncher said: Unknown protocol 'konq'. Description: The io-slave which provides access to the <strong>konq</strong> protocol could not be started. This is usually due to technical reasons. Possible Causes: klauncher could not find or start the plugin which provides the protocol.This means you may have an outdated version of the plugin. Possible Solutions: Update your software to the latest version. Your distribution should provide tools to update your software. Contact your appropriate computer support system, whether the system administrator, or technical support group for further assistance. === konqueror-20.04.2-bp153.1.24.x86_64 konqueror-lang-20.04.2-bp153.1.24.noarch konqueror-plugins-20.04.2-bp153.1.24.x86_64 are installed. bug? anyone? ty.

1 0

15.3, packagekit updater shows two libreoffice (?) updates but can not apply them
by cagsm 02 Jun '21

02 Jun '21

my 15.3 testing machine. came from RC candidates, today I applied some gstreamer and shim updates via zypper dup and it als brought in that suse-sles-backport-update repo location config or whatever that was. anyways so the packagekit now shows two more updates for libreoffice, but can not apply them update error, patch: suse-2021-1200-1.noarch conflicts with libreoffice-writer-extensions.x86_64 and such. first bug? anyone? ty.

2 3

Packman and certificates
by Roger Oberholtzer 02 Jun '21

02 Jun '21

If I download a package from Packman and install it directly, I get this warning: libvo-amrwbenc0-0.1.3-pm151.1.4.x86_64 (Plain RPM files cache): Signature verification failed [4-Signatures public key is not available] Of course if I add the repository this is all managed. But if I want to just install the RPM direct, is there a package with the certificates that I can install so this message is not given? -- Roger Oberholtzer

6 8

15.2, restarting firewall service fails, need to restart fail2ban right before it, ordering matters
by cagsm 02 Jun '21

02 Jun '21

15.2 with some recent zypper ps telling me that python stuff wants the firewall service to be restarted PID | PPID | UID | User | Command | Service | Files -----+------+-----+------+-----------+-----------+--------------------------- 1075 | 1 | 0 | root | python3.6 | firewalld | /usr/lib64/libX11.so.6.3.0 sudo systemctl restart firewalld.service Failed to restart firewalld.service: Transaction contains conflicting jobs 'restart' and 'stop' for fail2ban.service. Probably contradicting requirement dependencies configured. sudo systemctl restart firewalld.service fail2ban.service Failed to restart firewalld.service: Transaction contains conflicting jobs 'restart' and 'stop' for fail2ban.service. Probably contradicting requirement dependencies configured. finally sudo systemctl restart fail2ban.service firewalld.service throws no errors. i am a simple user only. bug? why? ty.

1 0