[packman] Kodi 21.0 Omega - Update against sound issues on Leap

[Masaru Nomiya]

Hello,

In the Message; 

  Subject    : Re: [packman] Kodi 21.0 Omega - Update against sound issues on Leap
  Message-ID : <26380588.1r3eYUQgxm at komascript.de>
  Date & Time: Wed, 01 May 2024 12:32:16 +0200

[MK] == Markus Kohm <markus.kohm at gmx.de> has written:

MK>  Am Mittwoch, 1. Mai 2024, 12:16:16 MESZ schrieb Manfred Hollstein:
MH>  > As I wrote several times before, I cannot reproduce what you see!

MK>  I've had a similar issue (but not with kodi) on one of my tumbleweed 
MK>  installations after a partial update. Only some packages have
MK>  been replaced by pipewire packages and some were still pulseaudio
MK>  packages → no sound with some applications. After installation
MK>  of all relevant pipewire packages i.e. pipewire-pulseaudo
MK>  everything was fine.

Manfred is mistaken, what they are encountering with their build of
kodi is a problem with the pipewire API, not with pipewire itself.

MK>  @Masaro Nomiya maybe it would help, if you would show the result of:

MK>  zypper search -i pipewire pulseaudio

S  | Name                               | Summary                                                                  | Type
---+------------------------------------+--------------------------------------------------------------------------+--------
i  | bumblebee-status-module-pulseaudio | Widget for pulseaudio                   
i+ | gstreamer-plugin-pipewire          | Gstreamer Plugin for PipeWire           
i+ | kpipewire6-imports                 | QtQuick bindings for kpipewire6         
i+ | libKPipeWire6                      | PipeWire integration for KDE Plasma - mai+ | libKPipeWireDmaBuf6                | PipeWire integration for KDE Plasma - DMi+ | libKPipeWireRecord6                | PipeWire integration for KDE Plasma - re
i+ | libpipewire-0_3-0                  | A Multimedia Framework designed to be an
i+ | libpipewire-0_3-0-32bit            | A Multimedia Framework designed to be an
i+ | pipewire                           | A Multimedia Framework designed to be an
i  | pipewire-alsa                      | PipeWire media server ALSA support      
i+ | pipewire-devel                     | Development Files For PipeWire, A Multim
i+ | pipewire-doc                       | PipeWire media server documentation     i+ | pipewire-dspsettings               | Gui Tool to force Pipewire metadata quaii+ | pipewire-lang                      | Translations for package pipewire       
i+ | pipewire-libjack-0_3               | PipeWire libjack replacement libraries  
i+ | pipewire-module-x11-0_3            | X11 support For PipeWire, A Multimedia F
i+ | pipewire-modules-0_3               | Modules For PipeWire, A Multimedia Frame
i+ | pipewire-modules-0_3-32bit         | Modules For PipeWire, A Multimedia Frame
i  | pipewire-pulseaudio                | PipeWire PulseAudio implementation      
i+ | pipewire-spa-plugins-0_2           | Plugins For PipeWire SPA                
i+ | pipewire-spa-plugins-0_2-32bit     | Plugins For PipeWire SPA                
i+ | pipewire-spa-plugins-0_2-jack      | SPA Plugin to use PipeWire as jack clien
i+ | pipewire-spa-tools                 | The PipeWire SPA Tools                  
i+ | pipewire-tools                     | The PipeWire Tools                      
i+ | pulseaudio-bash-completion         | PulseAudio Bash completion              
i+ | pulseaudio-setup                   | Set-up script for PulseAudio            
i+ | pulseaudio-utils                   | PulseAudio utilities                    
i+ | pulseaudio-utils-32bit             | PulseAudio utilities                    
i+ | pulseaudio-zsh-completion          | PulseAudio zsh completion               


I can't understand the use of the zypper command when there are
sometimes hundreds of updates.

By the way, are you using kodi?
If so, run as follows;

   $ kodi > kodi.log 2>&1

then show us the resulting kodi.log.

Kind Regards.

---
┏━━┓彡  Masaru Nomiya                       mail-to: nomiya @ lake.dti.ne.jp
┃＼／彡
┗━━┛	"Microsoft is overhauling its cybersecurity strategy, called the
		Secure Future Initiative, to incorporate key security features
		into its core set of technology platforms and cloud services. "
	  
-- Microsoft overhauls cyber strategy to finally embrace security by default --