March 2025 - openSUSE Support - openSUSE Mailing Lists

Two dnf related zypper dup conflicts:
by -pj 23 Mar '25

23 Mar '25

Hi openSUSE Tumbleweed 20250319 installed on machine. There are two dnf package related conflicts shown when attempting upgrade as follows: # zypper dup Refreshing service 'openSUSE'. Loading repository data... Reading installed packages... Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Computing distribution upgrade... 2 Problems: Problem: 1: the to be installed dnf-4.23.0-1.1.noarch conflicts with 'dnf-plugins-core < 4.7.0' provided by the to be installed dnf-plugins-core-4.4.4-2.4.noarch Problem: 2: the to be installed python3-dnf-4.23.0-1.1.noarch conflicts with 'python3-dnf-plugins-core < 4.7.0' provided by the to be installed python3-dnf-plugins-core-4.4.4-2.4.noarch Problem: 1: the to be installed dnf-4.23.0-1.1.noarch conflicts with 'dnf-plugins-core < 4.7.0' provided by the to be installed dnf-plugins-core-4.4.4-2.4.noarch Solution 1: Following actions will be done: keep obsolete dnf-4.18.0-6.3.noarch keep obsolete dnf-data-4.18.0-6.3.noarch Solution 2: Following actions will be done: deinstallation of dnf-4.18.0-6.3.noarch keep obsolete dnf-data-4.18.0-6.3.noarch Solution 3: deinstallation of dnf-plugins-core-4.4.4-2.3.noarch - # zypper packages --unneeded i | @System | dnf | 4.18.0-6.3 | noarch - # zypper remove -u dnf Reading installed packages... Resolving package dependencies... The following 22 packages are going to be REMOVED: dnf dnf-data dnf-plugins-core hawkey-man libcomps0 libdnf2 librepo0 libunbound8 python3-dnf python3-dnf-plugin-snapper python3-dnf-plugins-core python3-dnf-plugins-extras-common python3-hawkey python3-libcomps python3-libdnf python3-libmodulemd python3-unbound python313-distro python313-systemd typelib-1_0-Modulemd-2_0 unbound-anchor yum 22 packages to remove. Package install size change: | 0 B required by packages that will be installed -13.5 MiB | - 13.5 MiB released by packages that will be removed I did not proceed. I would like to ask you how to proceed with this situation. -Thanks

4 3

I need help getting sound to work on Leap 15.6
by J Leslie Turriff 23 Mar '25

23 Mar '25

On two machines, I am unable to get sound working. Strangely, the first is my normal working machine, where sound was working on 15.5; the other one is a Lenovo laptop that I'm setting up for my brother. (I'm getting some static from him about how long it's taking to fix this. :-) The problem does not seem to be openSUSE specific; I have tried installing other distros on the laptop, and the sound doesn't work for any of them.) Here is a possible culprit that I found described online at https://bbs.archlinux.org/viewtopic.php?pid=1446773#p1446773 and some output that might explain my problem: # ls -l /dev/snd total 0 drwxr-xr-x 2 root root 80 2024-11-18 17:36:20 by-path crw-rw----+ 1 root audio 116, 6 2024-11-18 17:36:20 controlC0 crw-rw----+ 1 root audio 116, 10 2024-11-18 17:36:20 controlC1 crw-rw----+ 1 root audio 116, 5 2024-11-18 17:36:20 hwC0D0 crw-rw----+ 1 root audio 116, 9 2024-11-18 17:36:20 hwC1D0 crw-rw----+ 1 root audio 116, 2 2024-11-18 17:38:19 pcmC0D3p crw-rw----+ 1 root audio 116, 3 2024-11-18 17:38:19 pcmC0D7p crw-rw----+ 1 root audio 116, 4 2024-11-18 17:38:19 pcmC0D8p crw-rw----+ 1 root audio 116, 8 2024-11-18 17:38:19 pcmC1D0c crw-rw----+ 1 root audio 116, 7 2024-11-21 16:30:17 pcmC1D0p crw-rw----+ 1 root audio 116, 1 2024-11-18 17:38:19 seq crw-rw----+ 1 root audio 116, 33 2024-11-18 17:36:19 timer The solution in the ArchLinux posting above didn't solve my problem, but maybe gets me closer to a fix; the output I get now is: $ cat ~/.asoundrc defaults.pcm.device 3 rc=0 $ speaker-test -Dplug:front -c2 -l5 -twav -wtest.wav speaker-test 1.2.10 Playback device is plug:front Stream parameters are 48000Hz, S16_LE, 2 channels WAV file(s) ALSA lib confmisc.c:1377:(snd_func_refer) Unable to find definition 'cards.0.pcm.front.3:CARD=0' ALSA lib conf.c:5207:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:5730:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2675:(snd_pcm_open_noupdate) Unknown PCM front Playback open error: -2,No such file or directory rc=1 Apparently, 'No such file or directory' is referring to the audio device, not a file? Leslie -- Platform: Linux Distribution: openSUSE Leap 15.6 - x86_64

4 12

A start job is running:
by -pj 23 Mar '25

23 Mar '25

Hi, openSUSE Tumbleweed 20250319 KDE 6.3.3 here. Each time when power on or powercycle the machine holds up on matrix at the following message for about 30 seconds. 'A start job is running for Flush Journal to Persistent Storage services' Why is this happening? -Best Hopes

7 28

mozilla repo is hung
by Larry Len Rainey 21 Mar '25

21 Mar '25

1 0

zypper.log very hungry
by Felix Miata 19 Mar '25

19 Mar '25

Is zypper.log's demand for space tunable? Nothing on subject jumps out at me from /etc/zypp/zypper.conf. I just checked its usage. I ran a zypper -v up follow-up to a zypper -v dup after re-enabling disabled Packman, for a total of 3 packages up'd: libx265-209 1.3MiB, libx264-164 568.9KiB, libde265-0 228.1KiB: Size after: 54967K Size before: 49969K Growth: 4998K The size before the dup I don't recall and didn't think to write first, but ISTR around 38000K, which if close would have been growth from 1100 transactions of about 12000K. Writing files of that size imposes a pretty fair size performance hit when not using NVME or SSD, so making it log less verbosely should provide a welcome plus. -- 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

6 18

zypper env variables
by Axel Braun 19 Mar '25

19 Mar '25

Hi, any option where I can look up the currently supported env variables? Could not spot anything in https://github.com/openSUSE/zypper/blob/master/doc/zypper.8.txt Thanks Axel

1 0

Removing python311-base results in additional package removal suggestions:
by -pj 19 Mar '25

19 Mar '25

Hello, Operating System: openSUSE Tumbleweed 20250310 is installed on machine here. When I pass '# zypper -vvv rm -u python311-base' there are many packages shown for removal. A bunch of these packages have names starting with python313, ghc etc. https://paste.opensuse.org/pastes/6e72e009b21f Passing '$ zypper packages --unneeded' lists some python311 packages and no python313 packages are shown. If no action is taken will the future released Tumbleweed snapshots incorporate removal of the python311 related packages (I think probably not)? How would you proceed with action if any?

4 13

default x11 or wayland
by JJM de Faber 18 Mar '25

18 Mar '25

Scope: Leap 15,6 Where is the default defined at the login screen for X11 or Wayland. I want to change the default to Wayland ! Thanks. Hans

4 4

default x11 or wayland
by JJM de Faber 17 Mar '25

17 Mar '25

On 2025-03-17 12:08, Andrei Borzenkov wrote: > On Mon, Mar 17, 2025 at 1:56 PM JJM de Faber <hans.defaber(a)gmail.com> wrote: >> Scope: Leap 15,6 >> >> Where is the default defined at the login screen for X11 or Wayland. >> >> I want to change the default to Wayland ! >> > Is your question about display manager greeter itself or about user > sessions started by display manager? Its the selection at the bottom of a loginscreen. So I think it is the display manager.

4 4

default x11 or wayland
by JJM de Faber 17 Mar '25

17 Mar '25

On 2025-03-17 12:32, Simon Becherer wrote: > Am 17.03.25 um 11:55 schrieb JJM de Faber: > > Scope: Leap 15,6 > > > > Where is the default defined at the login screen for X11 or Wayland. > > > > I want to change the default to Wayland ! > > > > Thanks. Hans > > For login of users > > simply start once a usersession, and then next time > this should be start similar. > (at least here, if you have only one visible user, tumbleweed) > > simoN > > > No, after a reboot its again the default (X11)

1 0