August 2021 - openSUSE Support - openSUSE Mailing Lists

Installing package mate-themes in Leap 15.3
by J Leslie Turriff 11 Aug '21

11 Aug '21

I want to install themes from the Mate desktop in my Leap 15.3 system. software.opensuse.org shows the following possibilities: openSUSE Tumbleweed Leap 15.2 Factory RISCV Backports for SLE 15 SP3 Backports for SLE 15 SP2 Backports for SLE 15 SP1 Backports for SLE 15 Backports for SLE 12 SP4 SUSE SLE-15-SP1 Debian 9.0 (!?) Since there is no package for Leap 15.3, would it be better to install the Leap 15.2 or the Tumbleweed package? Leslie -- Operating System: Linux Distribution: openSUSE Leap 15.3 x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.0.10 tde-config: 1.0

3 5

Leap support for Ryzen 5 5600G?
by Robert Munteanu 09 Aug '21

09 Aug '21

Hi, I have a Leap 15.2 'headless' VM host/NAS running with a Ryzen 5 2600X CPU. An upgrade to a 5600G would mean that I can free the only PCIE slot I have available or repurpose the GPU to VFIO/containerised workloads. I am not sure what the level of support is for Zen 3 APU. Is the 5600G CPU supported in Leap 15.2/15.3 or maybe in a future 15.4? Thanks, Robert

1 0

Leap - adding new qt for LXQt
by Axel Braun 08 Aug '21

08 Aug '21

Hi, has anybody tried to add a recent Qt, e.g. https://download.opensuse.org/repositories/KDE:/Qt5/ to a Leap 15.3 installation using LXQt as DE? My best guess is it will break LXQt.... Ideally I would like to avoid cloning the LXQt project in order to compile it against qt 5.15.x, if there are other options to achieve this - most welcome! Thanks Axel

2 2

[support] last night's 15.2 updates killed NFS server
by Felix Miata 04 Aug '21

04 Aug '21

When my TW, 15.3, Fedora, Debian, Mageia, etc. test boxes on LAN boot I have an alias to connect them manually to my server, this 15.2 PC, as needed, with content taking the form: mount servername:/exportname Since zypper up last night, attempts from clients to connect bring this response: Created symlink /run/systemd/system/remote-fs.target.wants/rpc-statd.service -> /usr/lib/systemd/system/rpc-statd.service. mount.nfs: requested NFS version or transport protocol is not supported Only nfs string on client end in journal is: <date/time> <hostname> kernel: Netfs 'nfs' registered for caching On server, result is similarly uninformative: # journalctl -b | grep nfs Aug 03 01:14:34 00srv systemd[1]: nfs-server.service: Failed with result 'exit-code'. Additional data: # systemctl status nfs-server ● nfs-server.service - NFS server and services Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; vendor preset: disabled) Drop-In: /usr/lib/systemd/system/nfs-server.service.d └─nfsserver.conf, options.conf /run/systemd/generator/nfs-server.service.d └─order-with-mounts.conf Active: failed (Result: exit-code) since Tue 2021-08-03 01:14:34 EDT; 18h ago Aug 03 01:14:34 00srv systemd[1]: nfs-server.service: Failed with result 'exit-code'. # cat /etc/nfsserver.conf cat: /etc/nfsserver.conf: No such file or directory # lsmod | grep nfs nfsd 438272 1 auth_rpcgss 110592 1 nfsd nfs_acl 16384 1 nfsd lockd 114688 1 nfsd grace 16384 2 nfsd,lockd sunrpc 479232 5 nfsd,auth_rpcgss,lockd,nfs_acl # uname -r 5.3.18-lp152.84-default # showmount -e clnt_create: RPC: Program not registered My clients have fstab entries of the form: servername:/exportname <mountpoint> nfs [ro,rw],noauto,nosuid,soft,rsize=8192,wsize=8192 0 0 /etc/exports on server was last written 6 years ago. Today is first failure ever noted. What needs to be changed to fix this? -- 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

3 9

chronyc looses sync
by Marco Calistri 03 Aug '21

03 Aug '21

I already asked but didn't get feedback so far. Why chronyc looses the syncing with external NTP during system st/by and it is necessary to manually re-sync? ^? time.cloudflare.com 0 6 0 - +0ns[ +0ns] +/- 0ns ^? par.cyberbits.eu 0 6 0 - +0ns[ +0ns] +/- 0ns ^? static.102.162.46.78.cli> 0 6 0 - +0ns[ +0ns] +/- 0ns ^? pob01.mulx.net 0 6 0 - +0ns[ +0ns] +/- 0ns ^? ntp.rol.net.mv 0 6 0 - +0ns[ +0ns] +/- 0ns ^? mail.masters-of-cloud.de 0 6 0 - +0ns[ +0ns] +/- 0ns sudo chronyc burst 4/4; sudo chronyc makestep [sudo] password di root: 200 OK 200 OK *^* time.cloudflare.com* 3 6 0 20m -85us[+1906us] +/- 71ms ^- par.cyberbits.eu 2 6 0 20m -4421us[-2430us] +/- 150ms ^- static.102.162.46.78.cli> 2 6 0 20m -15ms[ -15ms] +/- 162ms ^- pob01.mulx.net 2 6 0 20m +261us[ +261us] +/- 130ms ^- ntp.rol.net.mv 3 6 0 20m +1112ns[+1992us] +/- 426ms ^- mail.masters-of-cloud.de 2 6 0 20m +2603us[+2603us] +/- 108ms Thanks. Regards, -- Marco Calistri Build: openSUSE Tumbleweed 20210730 Kernel:5.13.4-1-default Desktop: XFCE (4.16.0)

3 16

Missing Key in Leap 15.3 (boo#1188475)
by Freek de Kruijf 03 Aug '21

03 Aug '21

Op dinsdag 3 augustus 2021 11:16:27 CEST schreef Andrei Borzenkov: > On Tue, Aug 3, 2021 at 12:02 PM Freek de Kruijf <freek(a)opensuse.org> wrote: > ... > > > > Install or force reinstall openSUSE-signkey-cert, reboot, perform > > > certificate enrollment in MokManager screen. The password MokManager > > > expects is operating system root user password. > > > > > > Or if package is already installed just manually create enrollment > > > request using > > > > > > mokutil --import /etc/uefi/certs/BDD31A9E-kmp.crt > > > > > > it will ask for password to use in MokManager. Reboot, confirm > > > certificate enrollment in MokManager screen. > > > > > > https://en.opensuse.org/openSUSE:UEFI#Enroll_MOK_certificate_with_mokuti > > > l_.2 8x86.2A_only.29 > > > > I tried this procedure, but did not succeed. > > Which of the two procedures listed above? I should have said tried suggestions in this article. > > > Maybe my situation is different. It is: > > Secure multi-boot laptop with openSUSE 15.2, 15.3, Tumbleweed and Windows > > Booting 15.3 gives error, caused by wrong certificate. I used Tumbleweed > > for > > the above procedure. > At which point? BIOS cannot load shim, shim cannot load grub, grub > cannot load kernel, some errors after kernel is loaded and started > (although I am not sure what would display these errors during boot)? When I boot 15.3 I from grub I get window with error ../../grub.......... bad shim signature ..... I used in Tumbleweed: mokutil --import /suse153/etc/uefi/certs/BDD31A9E-kmp.crt mokutil --import /etc/uefi/certs/BDD31A9E-kmp.crt both give: Already in kernel trusted keyring. > Did you verify that certificates are the same? I do not know. But if > you have a problem with 15.3 you should use whatever is delivered with > and for 15.3. > > > Booting 15.2 succeeds also. > > Entering both certificates using "mokutil --import" gives that they are > > already present. See above for both. > Who are "they"? But educated guess is that you are booting using > openSUSE shim which embeds openSUSE certificate which is the reason > mokutil says this certificate is already present. > > > Booting MokManager.efi and choosing Enroll from disk gives > > I never said to choose "enroll from disk" so you must have been > following some other procedure. > > > all kinds of things to choose from; in fact they are folders. I tried all, > > but afterwards I am still unable to boot 15.3. When I list available > > certificates I only see one. > > > > What am I doing wrong? > > It is difficult to understand what you are doing. Anyway, this is out > of place on this list. Post your question to support list and provide > > 1. output of efibootmgr -v BootCurrent: 0000 Timeout: 0 seconds BootOrder: 0000,0001,2001,2002,2003 Boot0000* opensuse-secureboot HD(2,GPT,4b5a9cda-e2ef-4d5f-87ee- a79393267592,0x12c800,0x96000)/File(\EFI\opensuse\shim.efi) Boot0001* Windows Boot Manager HD(2,GPT,4b5a9cda-e2ef-4d5f-87ee- a79393267592,0x12c800,0x96000)/ File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=. {.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d. 4.7.9.5.}.................... Boot2001* EFI USB Device RC Boot2002* EFI DVD/CDROM RC Boot2003* EFI Network RC > 2. mokutil --list-enrolled [key 1] SHA1 Fingerprint: 46:59:83:8c:82:03:fe:15:52:ad:19:e1:86:09:db:21:7e:3a:d2:4f Certificate: Data: Version: 3 (0x2) Serial Number: 1 (0x1) Signature Algorithm: sha256WithRSAEncryption Issuer: CN=openSUSE Secure Boot CA, C=DE, L=Nuremberg, O=openSUSE Project/emailAddress=build(a)opensuse.org Validity Not Before: Aug 26 16:12:07 2013 GMT Not After : Jul 22 16:12:07 2035 GMT Subject: CN=openSUSE Secure Boot CA, C=DE, L=Nuremberg, O=openSUSE Project/emailAddress=build(a)opensuse.org [rest removed...] Only one certificate. > 3. full script of "mokutil --import" including full invocation and all > messages. See above. > 4. Description at which point during boot you get an error and > screenshot/photo of this error (upload to https://susepaste.org/). See above description. > Even better would be a photo of each boot step starting from the very > first screen until you get this error. I get the grub menu and choose Leap 15.3 after that I get a subwindow with the error message mentioned above. When I use c in grub menu I enter: chainloader (hd0,2)/EFI/opensuse/MokManager.efi and boot behind grub> prompt I get the MokManager window asking password, which I enter, but after that I do NOT get Enroll Mok, only boot, enroll from disk, and enroll from hash. -- fr.gr. member openSUSE Freek de Kruijf

2 2