May 2023 - openSUSE Support - openSUSE Mailing Lists

No more videos on zdf.de
by Axel Braun 17 May '23

17 May '23

Hello everybody, since recently (dont ask me exactly since when) I cant stream video from german television https://www.zdf.de/live-tv anymore. No video format is supported by your device (the orther channel - daserste.de - is working well) Tried upgrading from ffmpeg-4 to -6 but no success. A bunch of openh264 libs is installed as well. Any idea what to try? Thanks Axel

4 6

Re: New Tumbleweed snapshot 20230512 released!
by Robert Webb 15 May '23

15 May '23

On Sat, 13 May 2023 18:00:44 +0000, Dominique Leuenberger <dimstar(a)suse.de> wrote *To factory(a)lists.opensuse.org*, Message-ID: <168400084471.21846.15478725920013160203@localhost>: > [...] > Packages changed: > [...] > ==== pipewire ==== > Version update (0.3.69 -> 0.3.70) > Subpackages: gstreamer-plugin-pipewire libpipewire-0_3-0 pipewire-alsa pipewire-lang pipewire-libjack-0_3 pipewire-modules-0_3 pipewire-pulseaudio pipewire-spa-plugins-0_2 pipewire-spa-tools pipewire-tools > > - Make pipewire-alsa conflict with alsa-plugins-pulse as both > provide /etc/alsa/conf.d/99-*-default.conf > [...] Making them duke it out. Zypper reacts with: # zypper dup [...] Problem: the to be installed pipewire-alsa-0.3.70-1.1.x86_64 conflicts with 'alsa-plugins-pulse' provided by the installed alsa-plugins-pulse-1.2.7.1-4.4.x86_64 Solution 1: deinstallation of alsa-plugins-pulse-1.2.7.1-4.4.x86_64 Solution 2: deinstallation of pipewire-alsa-0.3.69-2.1.x86_64 Solution 3: keep obsolete pipewire-alsa-0.3.69-2.1.x86_64 Choose from above solutions by number or cancel [1/2/3/c/d/?] (c): c Which one should be uninstalled? -- Robert Webb

3 4

Zypper dup: problem with libsox3, sox
by Robert Webb 12 May '23

12 May '23

I tried to 'zypper dup' from openSUSE Tumbleweed 20230508 to current (20230510): Computing distribution upgrade... 2 Problems: Problem: problem with the installed libsox3-14.4.2-1599.7.pm.137.x86_64 Problem: problem with the installed sox-14.4.2-1599.7.pm.137.x86_64 Problem: problem with the installed libsox3-14.4.2-1599.7.pm.137.x86_64 Solution 1: install libsox3-14.4.2-6.1.x86_64 from vendor openSUSE replacing libsox3-14.4.2-1599.7.pm.137.x86_64 from vendor http://packman.links2linux.de Solution 2: keep obsolete libsox3-14.4.2-1599.7.pm.137.x86_64 Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c/d/?] (c): s Problem: problem with the installed sox-14.4.2-1599.7.pm.137.x86_64 Solution 1: install sox-14.4.2-6.1.x86_64 from vendor openSUSE replacing sox-14.4.2-1599.7.pm.137.x86_64 from vendor http://packman.links2linux.de Solution 2: keep obsolete sox-14.4.2-1599.7.pm.137.x86_64 Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c/d/?] (c): c (4) Thu May 11 12:52:45 PDT 2023 There was nothing in the New Tumbleweed snapshot announcements nor the known defects reports about libsox3 or sox. What to do? Switch vendors? -- Robert Webb

4 8

Problem compiling kernel module for nvidia after dup of Tumbleweed
by Andrea Croci 08 May '23

08 May '23

Dear Community, I'm running OpenSUSE Tumbleweed and I have added the repository for Cuda from the Nvidia Website <https://developer.nvidia.com/cuda-downloads?target_os=Linux&target_arch=x86…>. I also added the "official" nvidia-repository for OpenSUSE <https://download.nvidia.com/opensuse/tumbleweed>, which however is for Leap, not for Tumbleweed. I installed Cuda, which pulled the nvidia-drivers "nvidia-computeG05", "nvidia-gfxG05-kmp-default" and "nvidia-glG05" of the 530 family. Everything was working fine. I recently did a zypper dup. After rebooting, the window manager doesn't start and I'm sent to a console login. The X log tells me, among other things: [ 65.945] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the [ 65.945] (EE) NVIDIA: system's kernel log for additional error messages and [ 65.945] (EE) NVIDIA: consult the NVIDIA README for details. [ 65.945] (EE) No devices detected. [ 65.945] (EE) Fatal server error: [ 65.945] (EE) no screens found(EE) [ 65.945] (EE) dmesg and journalctl have no trace of anything related to nvidia. I tried to look for why the nvidia-driver (graphics card Nvidia GTX 750 Ti) doesn't load, I found that there is no "nvidia*.ko" in the directory /lib/modules/6.3.1-1-default/updates/. I tried to reinstall the drivers in order to see if it would recompile the kernel module against the new kernel, but I got the first error message (please let me know if attaching text files to this list is not appropriate and if you would like it pasted online somewhere instead). I thought that may be because the cuda-repository for Leap is no longer at the same kernel version as Tumbleweed and disabled it. Trying to reinstall the above mentioned nvidia-drivers found only the family 470 and offered me, among other options, to downgrade "x11-video-nvidiaG05-530.30.02-0.x86_64" to "x11-video-nvidiaG05-470.182.03-53.1.x86_64", which I accepted. During the recompilation of the kernel module I got the errors in Error2.txt, which are very similar to the errors I got the first time. I'm out of clue as to what to try next and would appreciate any help. Thank you

2 5

Network Manager and my 'Use Case'
by Charles Rinnoch 01 May '23

01 May '23

Hi All I am currently using Wicked for network connection, but very much aware that this appears to be deprecated and likely to be taken out of the next version of Leap, so I have been looking at Network Manager and hit against some issues. I run several machines on a network with a NAS for shared storage. I import a home drive image with NFS to /import/home and soft link several individual user images into /home to allow user logon to a personal environment on each of several computers on the network. So far, so good - it works really well for my small setup for several years across all Leap 15.x. Moreover, a switch between Wicked and Network Manager is sufficiently slick that I can have some user IDs on the laptop only and use available wifi away from home via Network Manager. Problems come when I try to use Network Manager for the setup at home, in that Network Manager is not invoked [by systemd?] at the same point as Wicked is. So that leaves the NFS shares unconnected when the logon screen becomes available [ie the ID's on NFS don't show up] and it appears that Network Manager is more a per user subsystem for which you need to log in in order to get the connections you want. Now, I can work around this by logging in as root and doing 'mount -a' and there appears to be some options in fstab to make this work, so I am not totally stuck. Thus, my question for anyone who has confronted similar: Is there a 'best' or 'recommended ' way to address this issue and get the NFS shares available with Network Manager before the logon screen displays. Thanks in advance, any and all help on this appreciated CR

13 83