August 2022 - openSUSE Users - openSUSE Mailing Lists

[oS-en]
by Carlos E. R. 27 Sep '22

27 Sep '22

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I get an unknown GPG key warning, twice, when zypper or yast tries to check for updates. I did this: wget https://dl.google.com/linux/linux_signing_key.pub sudo rpm --import linux_signing_key.pub And now I get one warning, so there is another key that is missing: Unknown GnuPG Key The file repomd.xml (http://dl.google.com/linux/chrome/rpm/stable/x86_64) is digitally signed with the following unknown GnuPG key: ID: 4EB27DB2A3B88B8B. This means that a trust relationship to the creator of the file cannot be established. Using the file may put the integrity of your system at risk. Use it anyway? [ ] Do not show this message again. Where can I download that missing key from? Or is the command secuence I run incomplete or incorrect? (Leap 15.3) - -- Cheers Carlos E. R. (from 15.3 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYvKibxwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVaJEAoInpGLur54g7iTRWFj6F SrwlFwsfAJ0YFvwAKKzpAe8rTX5jXVzlPqKD9A== =5ups -----END PGP SIGNATURE-----

1 2

15.4 needs cross-arm-none-eabi
by David C. Rankin 29 Aug '22

29 Aug '22

This is both a shout-out and a question by doesn't openSUSE provide the package? gcc provides the cross-arm-none-eabi toolchain used to program microcontrollers (TI, Raspberry, etc..) A build service user provides the packages is reasonable shape: https://download.opensuse.org/repositories/home:/wkazubski/15.4/ But why doesn't openSUSE also provide the packages. The devel:/gcc repo provides the cross-arm-none full packages, but not the eabi sub-packages. This is the difference between as 26M install and an a 1.8G install. For example with the Pi-Pico, there is no need for 1.75G of the devel:/gcc packages. Why not provide the eabi subpackages? The wkazubski packages work fine, just need a bit of maintenance. -- David C. Rankin, J.D.,P.E.

2 7

Make Kwallet behave ?
by Nicolas Kovacs 29 Aug '22

29 Aug '22

Hi, I've been a KDE user since version 2.x on Slackware more than 20 years ago. I really like it for my daily work, but some details are a bit of a PITA. Kwallet is one of them. Here's a few scenarios that happen erratically on my Tumbleweed installations. 1. KDE starts, Kwallet pops up immediately and leaves me about ten seconds to type in my very long GPG password. In the background, applications that need a password to connect (like OwnCloud) fail and have to be restarted. 2. KDE starts, Wi-Fi tries to connect but fails, OwnCloud asks me for the connection password, and after about a minute or so, Kwallet decides to pop up too late to the show. 3. KDE starts, Kwallet pops up, I type in my password fast enough, Wi-Fi connects but OwnCloud asks me for the connection password even though Kwallet has been opened successfully. Any idea how I can make Kwallet behave ? Cheers from the sunny South of France, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12

3 3

tumbleweed setfacl on sddm login mystery
by Michael Hamilton 28 Aug '22

28 Aug '22

I noticed on my existing tumbleweed desktop, when I login a setfacl appears to be setting permissions on /dev/i2c-1 and they are reassigned to sddm on logout. % getfacl /dev/i2c-1 getfacl: Removing leading '/' from absolute path names # file: dev/i2c-1 # owner: root # group: root user::rw- user:michael:rw- group::--- mask::rw- other::--- This appears to happen for all users. But on a recently installed tumbleweed I don't see this behavior - no users have access to the i2c devices, no ACL's are assign on login. There is no i2c related group on either the old or new machine. Both machines are on the latest tumbleweed, both run Nvidia's driver. So I would expect the same behaviour on both. I do see that the nvidia devices have ACL's set on login (so perhaps this is X11 or nvidia related): getfacl /dev/nvidia0 getfacl: Removing leading '/' from absolute path names # file: dev/nvidia0 # owner: root # group: video user::rw- user:michael:rw- group::rw- mask::rw- other::--- It's possible I setup something years ago and have forgotten about it. I think I have used i2c in the past for sensors. More recently I've started using it with ddcutil and vdu_controls (which I wrote) - I was puzzled that they work with no permission changes required on my desktop, but not on this new machine. I'm looking for clues that might throw some light on the situation. Michael

2 2

Desktop search on Tumbleweed : Recoll or similar applications
by Nicolas Kovacs 27 Aug '22

27 Aug '22

Hi, A few weeks ago I decided to move all my desktop installations from OpenSUSE Leap to Tumbleweed, since it looks like the latter gets more love from the developers. So far things look good. I only have a small number of details to tackle. Under Leap I've been using Recoll, a nifty desktop search application that's quite powerful, though it's also a bit of a resource hog. https://www.lesbonscomptes.com/recoll/ Under Leap the Recoll package was provided by the KDE:Extra repository. Now I have a few questions. 1) If I want to use Recoll under Tumbleweed, what's the recommended way to install it ? 2) Can you guys recommend a similar desktop search application ? Recoll is great for finding the proverbial needle in the haystack, like for example a single sentence in gigabytes of mail archives, or even a character string in a PDF or even a Word document. But maybe there are other applications out there that do the job well ? Thanks & cheers from rainy Austria, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12

2 2

Tensorflow
by Roger Oberholtzer 24 Aug '22

24 Aug '22

Is anyone using tensorflow/tensorflow2 on Leap 15.3? I can only find tensorflow-lite, which is a scaled down version for things like mobile devices. Has it dropped off the radar? In OBS, it seems to be locked for all targets, and I don't see any previous builds anywhere. I thought maybe it was only available for SLE15. But I don't see those packages. Perhaps I don't know where to look for SLE15 packages that might be compatible with 15.3. IIRC, on a recent Leap release (15.0?), tensorflow and such tools were listed as a big part of what the release added. Is that no longer the case? I have looked at contacting the maintainer (https://build.opensuse.org/package/users/openSUSE:Leap:15.3/tensorflow) but last time I contacted someone listed as a maintainer, I got a surprisingly rude response that they were in fact not the maintainer. Despite what was listed in the project. So I'm asking here first... -- Roger Oberholtzer

2 4

Tumbleweed: prevent SSH client from sending environment variables
by Nicolas Kovacs 22 Aug '22

22 Aug '22

Hi, Up until a few weeks ago, I ran OpenSUSE Leap as my daily driver. I only recently moved to Tumbleweed, which seems to get more attention by the OpenSUSE developers. One of the things I did on my Leap system was reconfigure the SSH client in order to *not* send any environment variables. To do this, I opened /etc/ssh/ssh_config and found the relevant stanza: SendEnv LANG LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES SendEnv LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT SendEnv LC_IDENTIFICATION LC_ALL I simply commented this out and reloaded SSH: # systemctl reload sshd I tried to do this with Tumbleweed, but I don't have an /etc/ssh/ssh_config file. Instead, I only have an empty /etc/ssh/ssh_config.d directory. So I guess my SSH client has all default values defined at build time. What would be an orthodox approach to prevent it from sending any environment variables ? Thanks & cheers from Austria, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12

6 11

TW: boot problem kernel 5.18.9-2 and higher
by Martin /Nightowl/ Byttebier 21 Aug '22

21 Aug '22

Hardware: Dell XPS 8940 11th Gen Intel i7-11700 (16) @ 4.800GHz NVIDIA GeForce RTX 3060 Ti I'm using latest TW-release with kernel 5.19.0-1-default and NVIDIA driver 515.65.01 installed the hard way. kernel 5.18.9-2 or higher seems to give a (plymouth) problem. The problem doesn't occur with kernel 5.18.9-1-default or lower. Booting up with one of these kernels the plymouth boot screen stops displaying after this line: I915 0000:00:02.0: enabling device (0006 -> 0007) Eventually I get to the KDE login screen. The problem is that I'm using the hard way to install NVIDIA. This makes I can't boot when a new kernel is installed as the boot process ends up with a black screen. Luckely I can access the faulty pc from another pc and install the driver from there. journalctl show me this: Aug 12 18:17:32 dell-desk sddm[1381]: Initializing... Aug 12 18:17:32 dell-desk sddm[1381]: Starting... Aug 12 18:17:32 dell-desk sddm[1381]: Logind interface found Aug 12 18:17:32 dell-desk sddm[1381]: Adding new display on vt 7 ... Aug 12 18:17:32 dell-desk sddm[1381]: Loading theme configuration from "" Aug 12 18:17:32 dell-desk sddm[1381]: Display server starting... Aug 12 18:17:32 dell-desk sddm[1381]: Running: /usr/bin/X -nolisten tcp -auth /run/sddm/{765f2352-11a7-428b-9a7a-55f8fef85402} -background none -noreset -displayfd 17 -seat seat0 vt7 Aug 12 18:17:33 dell-desk sddm[1381]: Failed to read display number from pipe Aug 12 18:17:33 dell-desk sddm[1381]: Attempt 1 starting the Display server on vt 7 failed Aug 12 18:17:35 dell-desk sddm[1381]: Display server starting... Aug 12 18:17:35 dell-desk sddm[1381]: Running: /usr/bin/X -nolisten tcp -auth /run/sddm/{765f2352-11a7-428b-9a7a-55f8fef85402} -background none -noreset -displayfd 17 -seat seat0 vt7 Aug 12 18:17:35 dell-desk sddm[1381]: Failed to read display number from pipe Aug 12 18:17:35 dell-desk sddm[1381]: Attempt 2 starting the Display server on vt 7 failed Aug 12 18:17:37 dell-desk sddm[1381]: Display server starting... Aug 12 18:17:37 dell-desk sddm[1381]: Running: /usr/bin/X -nolisten tcp -auth /run/sddm/{765f2352-11a7-428b-9a7a-55f8fef85402} -background none -noreset -displayfd 17 -seat seat0 vt7 Aug 12 18:17:37 dell-desk sddm[1381]: Failed to read display number from pipe Aug 12 18:17:37 dell-desk sddm[1381]: Attempt 3 starting the Display server on vt 7 failed Aug 12 18:17:37 dell-desk sddm[1381]: Could not start Display server on vt 7 Any idea how I can fix this? Martin

10 49

VirtualBox Puel Crashes After Latest Updates on 15.4 Qt related.
by David C. Rankin 18 Aug '22

18 Aug '22

All, I am running Virtualbox 6.1.36 PUEL version (I need the USB). It has run fine for years and years (since version 3.X). Today I went to start it and it would not load. Starting from the command line as my user, I get: VirtualBox Qt FATAL: FATAL: The application binary appears to be running setuid, this is a security hole. Aborted Huh? WTF? Obviously it is unhappy with Qt or vice versa. This worked fine a couple of weeks ago. What to check to narrow down the issue? I can su and then VirtualBox runs, but since it is running under root, none of my VM's are found. Running with sudo -E I receive: No protocol specified No protocol specified Qt CRITICAL: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb. Now running su'ed to root, Virtualbox starts and the dialog appears, but no vms are shown. The following warning is shown on the command line: Qt WARNING: QStandardPaths: runtime directory '/run/user/1000' is not owned by UID 0, but a directory permissions 0700 owned by UID 1000 GID 1060 What has changed with Qt these past two weeks that is causing VirtualBox to freak out? -- David C. Rankin, J.D.,P.E.

1 1

Permissions of /usr/local/bin
by Siard 17 Aug '22

17 Aug '22

/usr/local/bin is owned by root with permissions 755, so as a user I cannot put a script in there. I can change the ownership, but every time after a reboot it is owned by root again, with permissions 755. Does anyone know where this is set, and/or how I can make /usr/local/bin permanently make writable for a user?

12 25