Soundsystem Alsa oder/und Pulse?

Deutsch (German) Anwendungen
#1

Hallo,
kann mir jemand sagen welches das aktuelle Sound-System
unter OpenSuse Leap 42.2 -64bit- ist. Ich habe Teile von Alsa
und Teile von Pulse auf meinem Rechner. Sie machen
noch keine Probleme, außer beim Update. Ich muss dazu
sagen, dass ich das System seit einigen Jahren von Version
zu Version upgradet habe.
Kann ich eines von Beiden in die Tonne treten?
Danke für eure Hilfe,
Dieter

#2

Warum in die Tonne treten, funktioniert hier einwandfrei…

https://de.wikipedia.org/wiki/Advanced_Linux_Sound_Architecture
https://de.wikipedia.org/wiki/PulseAudio

#3

AMD 64-Bit System: AMD FX™-4100 Quad-Core Processor – Arbeitsplatzrechner ohne Bluetooth.
Das Systemd Journal und ‘ps’ zeigen folgendes:


 # journalctl --this-boot | grep -iE 'pulse|Alsa'
Jul 06 09:44:48 xxx systemd-udevd[533]: Process '/usr/sbin/alsactl restore 1' failed with exit code 99.
Jul 06 09:44:48 xxx systemd-udevd[506]: Process '/usr/sbin/alsactl restore 0' failed with exit code 99.
Jul 06 09:45:23 xxx rtkit-daemon[2864]: Successfully made thread 2863 of process 2863 (/usr/bin/pulseaudio) owned by 'xx' high priority at nice level -11.
Jul 06 09:45:23 xxx rtkit-daemon[2864]: Successfully made thread 2877 of process 2863 (/usr/bin/pulseaudio) owned by 'xx' RT at priority 5.
Jul 06 09:45:23 xxx rtkit-daemon[2864]: Successfully made thread 2889 of process 2863 (/usr/bin/pulseaudio) owned by 'xx' RT at priority 5.
Jul 06 09:45:23 xxx rtkit-daemon[2864]: Successfully made thread 2897 of process 2863 (/usr/bin/pulseaudio) owned by 'xx' RT at priority 5.
Jul 06 09:45:48 xxx pulseaudio[2863]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jul 06 09:53:51 xxx rtkit-daemon[2864]: Successfully made thread 4123 of process 4123 (/usr/bin/pulseaudio) owned by 'xx' high priority at nice level -11.
Jul 06 09:53:51 xxx rtkit-daemon[2864]: Successfully made thread 4133 of process 4123 (/usr/bin/pulseaudio) owned by 'xx' RT at priority 5.
Jul 06 09:53:51 xxx rtkit-daemon[2864]: Successfully made thread 4148 of process 4123 (/usr/bin/pulseaudio) owned by 'xx' RT at priority 5.
Jul 06 09:53:51 xxx rtkit-daemon[2864]: Successfully made thread 4150 of process 4123 (/usr/bin/pulseaudio) owned by 'xx' RT at priority 5.
Jul 06 09:54:16 xxx pulseaudio[4123]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jul 06 10:01:11 xxx rtkit-daemon[2864]: Successfully made thread 6013 of process 6013 (/usr/bin/pulseaudio) owned by 'yy' high priority at nice level -11.
Jul 06 10:01:11 xxx rtkit-daemon[2864]: Successfully made thread 6031 of process 6013 (/usr/bin/pulseaudio) owned by 'yy' RT at priority 5.
Jul 06 10:01:12 xxx rtkit-daemon[2864]: Successfully made thread 6039 of process 6013 (/usr/bin/pulseaudio) owned by 'yy' RT at priority 5.
Jul 06 10:01:37 xxx pulseaudio[6013]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jul 06 13:38:07 eck001 rtkit-daemon[2864]: Successfully made thread 17828 of process 17828 (/usr/bin/pulseaudio) owned by 'zz' high priority at nice level -11.
Jul 06 13:38:07 eck001 rtkit-daemon[2864]: Successfully made thread 17855 of process 17828 (/usr/bin/pulseaudio) owned by 'zz' RT at priority 5.
Jul 06 13:38:07 eck001 rtkit-daemon[2864]: Successfully made thread 17857 of process 17828 (/usr/bin/pulseaudio) owned by 'zz' RT at priority 5.
Jul 06 13:38:32 eck001 pulseaudio[17828]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
 # 
 # ps -ef | grep -iE 'pulse|Alsa'
xxx       4123     1  0 09:53 ?        00:00:00 /usr/bin/pulseaudio --start --log-target=syslog
root     31574 29080  0 18:15 pts/1    00:00:00 grep --color=auto -iE pulse|Alsa
 #

Also, scheinbar ist Alsa nicht benutzt aber, Abhängigkeiten, Abhängigkeiten, Abhängigkeiten:
beide sind installiert – wahrscheinlich wird irgend eine Paket meckern wenn Alsa entfernt wird . . .

#4

Aktuell:
Hardware—Alsa----Pulseaudio—Programm

Und Alsa wird benutzt…
Man lese meine geposteten Links…
Dann versteht man den Unterschied zwischen pulseaudio und alsa.

Man schaue nur einmal, was z.B. audacity benutzt…

#5

Und Alsa wird benutzt…
Man lese meine geposteten Links…
Dann versteht man den Unterschied zwischen pulseaudio und alsa.

Man schaue nur einmal, was z.B. audacity benutzt…

Hallo “Sauerland”,
ich habe verstanden.
Danke für Deine Hilfe,
Dieter

#6

Jetzt bin ich ganz klein:

Soundquelle → PulseAudio → ALSA-Treiber → Hardware

Eine kurze blick in die Anforderungen der “pulseaudio” Paket ergibt:

libasound.so.2(ALSA_0.9)(64bit)
libalsa-util.so()(64bit)

#7

Auf gut deutsch:
Man kann alles deaktivieren/deinstallieren, nur ob man dann die Probleme beherrscht…

Besser wäre es, das aktuelle Problem zu beheben.