| Summary: | alsa addon service status always shows "stopped" | ||
|---|---|---|---|
| Product: | IPFire | Reporter: | Arno Jonker <admin> |
| Component: | --- | Assignee: | Adolf Belka <adolf.belka> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | Aesthetic Issue | ||
| Priority: | - Unknown - | CC: | adolf.belka, peter.mueller |
| Version: | 2 | ||
| Hardware: | x86_64 | ||
| OS: | All | ||
| Attachments: | Screenshot Add-On - Services Page | ||
I have looked through the initscript and done a lot of reading on the alsa package. I now understand that alsa is not running as a typical daemon service. It is provided by kernel modules. The initscript does not start and stop alsa in the traditional approach. The start loads two alsa modules which then triggers other dependent alsa modules to be loaded. Then alsactl restore is run which restores andy configuration previously saved. The stop runs alsactl store which stores the current configuration. So alsa is not a service in the intention of the addon services table. Therefore I will raise a patch to remove the service label from it as @Arno originally suggested in the forum where the problem was first flagged. I have also noted that when the alsa addon is first installed the initscript links are created but the initscript is not run so the required modules would not be loaded unless IPFire was rebooted. Once the modules are loaded, then if alsa is uninstalled those modules stay in place until IPFire is rebooted. I confirmed this on my IPFire system. The modules stayed in place after alsa was uninstalled and a reboot was needed to remove all the alsa related modules. So I will also raise a patch that adds the start option from the initscript to the install.sh pak file and unload the modules in the uninstall.sh pak file. patch set submitted to dev mailing list and to patchwork. https://lists.ipfire.org/pipermail/development/2023-April/015800.html https://patchwork.ipfire.org/project/ipfire/list/?series=3593 V2 version of patch set submitted based on feedback from Arne Fitzenreiter. https://lists.ipfire.org/pipermail/development/2023-May/015856.html https://patchwork.ipfire.org/project/ipfire/list/?series=3622 https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=d83b6fc6df76b9feefdb53ebd7c7516820004e92 https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=908f3783ec544ea0da998c5840a47d5f138882b2 https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=238a0468da6a6d1fdfa236969e5dd43029dcb85a https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=4e28814b6f9378ec1dad7bf62243bf4ccf214397 Core Update 175 Testing has been released https://blog.ipfire.org/post/ipfire-2-27-core-update-175-is-available-for-testing Confirmed that when alsa is installed that it no longer shows up in the addon services list. Also confirmed that when alsa is uninstalled the sound modules are then unloaded. |
Created attachment 1148 [details] Screenshot Add-On - Services Page The alsa addon always shows status stopped. The initscript does not have a status command option (only start|stop). The services page uses the status command to show what the status of the service is.