November 2024 - Alsa-devel - mailman.alsa-project.org

kernel snd seq bugs: SND_SEQ_EVENT_CLIENT_CHANGE & SND_SEQ_EVENT_PORT_CHANGE
by Mark Lentczner 26 Nov '24

26 Nov '24

I'm the author of amidiminder - a utility that keeps track of desired connections between ALSA Seq (MIDI) ports. I've found a bug in the kernel part of the ALSA Sequencer, and am not sure where or how to report it. Summary: The events: * SND_SEQ_EVENT_CLIENT_CHANGE is never sent * SND_SEQ_EVENT_PORT_CHANGE is not sent on common port changes (name and port info) I have a lot of detail on these bugs, what other software causes them to be a problem (PureData), and where the missing code in the kernel sound/core/seq files is. Before I dump all the details in this forum.... where is the right place for me to report and/or discuss this? - Mark

2 3

Build failures with GCC 15 (-std=gnu23)
by GitHub issues - edited 26 Nov '24

26 Nov '24

alsa-project/alsa-tools issue #25 was edited from kostadinsh: Some of the programs in alsa-tools fail to build with upcoming GCC 15 which uses `-std=gnu23` by default. This can be reproduced on older GCC and Clang versions by adding `-std=gnu23` to CFLAGS. Downstream Gentoo bug report: https://bugs.gentoo.org/943946 hdajackretask: ``` apply-changes.c:358:10: error: conflicting types for ‘reset_changes_boot’; have ‘gboolean(GError **)’ {aka ‘int(struct _GError **)’} 358 | gboolean reset_changes_boot(GError** err) | ^~~~~~~~~~~~~~~~~~ In file included from apply-changes.c:12: apply-changes.h:12:10: note: previous declaration of ‘reset_changes_boot’ with type ‘gboolean(void)’ {aka ‘int(void)’} 12 | gboolean reset_changes_boot(); | ^~~~~~~~~~~~~~~~~~ main-gtk.c: In function ‘reset_boot_clicked’: main-gtk.c:375:5: error: too many arguments to function ‘reset_changes_boot’ 375 | reset_changes_boot(&err); | ^~~~~~~~~~~~~~~~~~ In file included from main-gtk.c:11: apply-changes.h:12:10: note: declared here 12 | gboolean reset_changes_boot(); | ^~~~~~~~~~~~~~~~~~ ``` envy24control: ``` new_process.c: In function ‘new_process’: new_process.c:67:18: error: assignment to ‘void (*)(void)’ from incompatible pointer type ‘__sighandler_t’ {aka ‘void (*)(int)’} [-Wincompatible-pointer-types] 67 | int_stat = signal(SIGINT, SIG_IGN); | ^ new_process.c:68:19: error: assignment to ‘void (*)(void)’ from incompatible pointer type ‘__sighandler_t’ {aka ‘void (*)(int)’} [-Wincompatible-pointer-types] 68 | quit_stat = signal(SIGQUIT, SIG_IGN); | ^ new_process.c:69:19: error: assignment to ‘void (*)(void)’ from incompatible pointer type ‘__sighandler_t’ {aka ‘void (*)(int)’} [-Wincompatible-pointer-types] 69 | usr2_stat = signal(SIGUSR2, SIG_IGN); | ^ new_process.c:81:24: error: passing argument 2 of ‘signal’ from incompatible pointer type [-Wincompatible-pointer-types] 81 | signal(SIGINT, int_stat); | ^~~~~~~~ | | | void (*)(void) In file included from envy24control.h:4: /usr/include/signal.h:88:57: note: expected ‘__sighandler_t’ {aka ‘void (*)(int)’} but argument is of type ‘void (*)(void)’ 88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler) | ~~~~~~~~~~~~~~~^~~~~~~~~ new_process.c:82:25: error: passing argument 2 of ‘signal’ from incompatible pointer type [-Wincompatible-pointer-types] 82 | signal(SIGQUIT, quit_stat); | ^~~~~~~~~ | | | void (*)(void) /usr/include/signal.h:88:57: note: expected ‘__sighandler_t’ {aka ‘void (*)(int)’} but argument is of type ‘void (*)(void)’ 88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler) | ~~~~~~~~~~~~~~~^~~~~~~~~ new_process.c:83:25: error: passing argument 2 of ‘signal’ from incompatible pointer type [-Wincompatible-pointer-types] 83 | signal(SIGUSR2, usr2_stat); | ^~~~~~~~~ | | | void (*)(void) /usr/include/signal.h:88:57: note: expected ‘__sighandler_t’ {aka ‘void (*)(int)’} but argument is of type ‘void (*)(void)’ 88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler) | ~~~~~~~~~~~~~~~^~~~~~~~~ ``` Issue URL : https://github.com/alsa-project/alsa-tools/issues/25 Repository URL: https://github.com/alsa-project/alsa-tools

1 0

Build failures with GCC 15 (-std=gnu23)
by GitHub issues - opened 26 Nov '24

26 Nov '24

alsa-project/alsa-tools issue #25 was opened from kostadinsh: Some of the programs in alsa-tools fail to build with upcoming GCC 15 which uses `-std=gnu23` by default. This can be reproduced on older GCC and Clang versions by adding `-std=gnu23` to CFLAGS. Downstream Gentoo bug report: https://bugs.gentoo.org/943946 hdajackretask: ``` main-gtk.c: In function ‘reset_boot_clicked’: main-gtk.c:375:5: error: too many arguments to function ‘reset_changes_boot’ 375 | reset_changes_boot(&err); | ^~~~~~~~~~~~~~~~~~ In file included from main-gtk.c:11: apply-changes.h:12:10: note: declared here 12 | gboolean reset_changes_boot(); | ^~~~~~~~~~~~~~~~~~ ``` envy24control: ``` new_process.c: In function ‘new_process’: new_process.c:67:18: error: assignment to ‘void (*)(void)’ from incompatible pointer type ‘__sighandler_t’ {aka ‘void (*)(int)’} [-Wincompatible-pointer-types] 67 | int_stat = signal(SIGINT, SIG_IGN); | ^ new_process.c:68:19: error: assignment to ‘void (*)(void)’ from incompatible pointer type ‘__sighandler_t’ {aka ‘void (*)(int)’} [-Wincompatible-pointer-types] 68 | quit_stat = signal(SIGQUIT, SIG_IGN); | ^ new_process.c:69:19: error: assignment to ‘void (*)(void)’ from incompatible pointer type ‘__sighandler_t’ {aka ‘void (*)(int)’} [-Wincompatible-pointer-types] 69 | usr2_stat = signal(SIGUSR2, SIG_IGN); | ^ new_process.c:81:24: error: passing argument 2 of ‘signal’ from incompatible pointer type [-Wincompatible-pointer-types] 81 | signal(SIGINT, int_stat); | ^~~~~~~~ | | | void (*)(void) In file included from envy24control.h:4: /usr/include/signal.h:88:57: note: expected ‘__sighandler_t’ {aka ‘void (*)(int)’} but argument is of type ‘void (*)(void)’ 88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler) | ~~~~~~~~~~~~~~~^~~~~~~~~ new_process.c:82:25: error: passing argument 2 of ‘signal’ from incompatible pointer type [-Wincompatible-pointer-types] 82 | signal(SIGQUIT, quit_stat); | ^~~~~~~~~ | | | void (*)(void) /usr/include/signal.h:88:57: note: expected ‘__sighandler_t’ {aka ‘void (*)(int)’} but argument is of type ‘void (*)(void)’ 88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler) | ~~~~~~~~~~~~~~~^~~~~~~~~ new_process.c:83:25: error: passing argument 2 of ‘signal’ from incompatible pointer type [-Wincompatible-pointer-types] 83 | signal(SIGUSR2, usr2_stat); | ^~~~~~~~~ | | | void (*)(void) /usr/include/signal.h:88:57: note: expected ‘__sighandler_t’ {aka ‘void (*)(int)’} but argument is of type ‘void (*)(void)’ 88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler) | ~~~~~~~~~~~~~~~^~~~~~~~~ ``` Issue URL : https://github.com/alsa-project/alsa-tools/issues/25 Repository URL: https://github.com/alsa-project/alsa-tools

1 0

No built-in microphone in Thinkpad X1 Carbon (Gen 12) after update to v1.2.13
by GitHub issues - opened 26 Nov '24

26 Nov '24

alsa-project/alsa-ucm-conf issue #476 was opened from iyanmv: I think the title is self-explanatory. After updating from v1.2.12 to v1.2.13 in Arch Linux, the built-in microphone on my laptop is not working. Downgrading to previous versions fixes the issue. In addition, I also noticed that when attached to an external monitor using a docking station, the speakers of the monitor are not listed as before, and only the laptop's built-in speaker appears. I'm running linux 6.12.1 and KDE Plasma 6.2.3. Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/476 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

how do I create configure a ucm2 conf file for my card just like an acp file
by GitHub issues - opened 26 Nov '24

26 Nov '24

alsa-project/alsa-ucm-conf issue #475 was opened from beh-10257: 1_ how do I know if my card is using acp or ucm profile 2_ can ucm config file be availble in user directories 3_ how do i test a ucm profile 4_ if my card is using ucm is there a way to cooverride that file 5_ for more context https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/4421 6_ as a tldr I want to take advanatage of indep_hp=yes (IDK why this is not enabled by default its a great feature compared to other platforms after all) either way I want to make hw:0,0 as speaker and hw:0,2 as headphones can a ucm profile replace the indep_hp hint and udev rule and just porceed to seperate them directly also indep_hp seperates speaker and headphones output is there a way to seperate internal mic and headphone speaker also is there a way to put priority for headphones when the jack port is actually put or even disable it entirely and just default back to speaker automatically thats all thanks thats all and thanks further editing will be filled once I have more questions and thanks Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/475 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

ALC225 update depop procedure
by Kailang 26 Nov '24

26 Nov '24

Hi Takashi, ALC225 update depop procedure. Many Thanks. BR, Kailang

2 1

Enable speaker pins for Medion E15443 platform
by Kailang 26 Nov '24

26 Nov '24

Hi Takashi, Attach was fixed speaker no sound issue. BR, Kailang

2 1

Device selection regression in 1.2.13 for LNL
by GitHub issues - edited 26 Nov '24

26 Nov '24

alsa-project/alsa-ucm-conf issue #474 was edited from CarelessCaution: On Intel Lunar Lake, there seems to be a regression in alsa-ucm-conf that affects device selection in KDE Plasma and probably in other software. In 1.2.12, there are the options Play HiFi Quality Music and Pro Audio for both input and output. However, when upgrading to 1.2.13, there is only the option for Pro Audio. This problem is immediately remedied by downgrading just the alsa-ucm-conf package on Arch Linux. According to `aplay -l`, the audio card is sofhdadsp. Before (1.2.12): ![before](https://github.com/user-attachments/assets/c7fa81e0-97f1-45ae-a14e-8549f85cdd27) After (1.2.13): ![after](https://github.com/user-attachments/assets/5867886b-6686-4265-ad68-50c7f53e1a47) Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/474 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

Device selection regression in 1.2.13 for LNL
by GitHub issues - edited 26 Nov '24

26 Nov '24

alsa-project/alsa-ucm-conf issue #474 was edited from CarelessCaution: On Intel Lunar Lake, there seems to be a regression in alsa-ucm-conf that affects device selection in KDE Plasma and probably in other software. In 1.2.12, there are the options Play HiFi Quality Music and Pro Audio for both input and output. However, when upgrading to 1.2.13, there is only the option for Pro Audio. This problem is immediately remedied by downgrading just the alsa-ucm-conf package on Arch Linux. According to `aplay -l`, the audio card is sofhdadsp . Before (1.2.12): ![before](https://github.com/user-attachments/assets/c7fa81e0-97f1-45ae-a14e-8549f85cdd27) After (1.2.13): ![after](https://github.com/user-attachments/assets/5867886b-6686-4265-ad68-50c7f53e1a47) Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/474 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

Device selection regression in 1.2.13 for LNL
by GitHub issues - opened 26 Nov '24

26 Nov '24

alsa-project/alsa-ucm-conf issue #474 was opened from CarelessCaution: On Intel Lunar Lake, there seems to be a regression in alsa-ucm-conf that affects device selection in KDE Plasma and probably in other software. In 1.2.12, there are the options Play HiFi Quality Music and Pro Audio for both input and output. However, when upgrading to 1.2.13, there is only the option for Pro Audio. This problem is immediately remedied by downgrading just the alsa-ucm-conf package on Arch Linux. Before (1.2.12): ![before](https://github.com/user-attachments/assets/c7fa81e0-97f1-45ae-a14e-8549f85cdd27) After (1.2.13): ![after](https://github.com/user-attachments/assets/5867886b-6686-4265-ad68-50c7f53e1a47) Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/474 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0