SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I posted this was released almost a week ago, but no update, so feel free to parse the changelog and if any of it affects you, d/l and build apache yourselves, especially if your a mod_md user or the CVE affects you.
edited:
CVE-2021-31618 mod_http2: Fix a potential NULL pointer dereference
PS Pat, if youve ignored this because you're awaiting the official announce email, there has been a problem with the process that sends the emails out (it is being resolved at present)
I posted this was released almost a week ago, but no update, so feel free to parse the changelog and if any of it affects you, d/l and build apache yourselves, especially if your a mod_md user or the CVE affects you.
edited:
CVE-2021-31618 mod_http2: Fix a potential NULL pointer dereference
PS Pat, if youve ignored this because you're awaiting the official announce email, there has been a problem with the process that sends the emails out (it is being resolved at present)
The 2.4.48 was formally released only yesterday 1st of June, not last week, see: https://httpd.apache.org/
Last time we upgraded Apache httpd (to 2.4.47) without waiting for the formal release announcement I ended up with a broken web service.
The 2.4.48 was formally released only yesterday 1st of June, not last week, see: https://httpd.apache.org/
Last time we upgraded Apache httpd (to 2.4.47) without waiting for the formal release announcement I ended up with a broken web service.
Im one of the apache testers, I KNOW when it was released and it was before then, I could tell you teh exact time/date but cant be arsed, as I said, there was a problem with process which changes templates, and sends emails
2.4.47 was a very rare event, so rare it wasnt picked up by automated testing, nor manual testing. I can understand Pat waiting, and if he just wants to wait for them, no problem, I wont waste my time announcing releases here any more.
I propose to rollback to the previous ALSA packages, because the one from the series 1.2.5 does not work at all on my mini-PC MinisForum Z83-F which relies on UCM for the audio support.
I got no audio devices and no sound at all. I tested this both with PulseAudio and PipeWire. Not tested at all on pure ALSA, because my mini-PC have around 200 controls on the alsamixer.
And not only that they does not work, but with all respect, looks like at least alsa-lib is not so well packaged, as the topologies and the UCM folders are put now in folders with names like /usr/share/alsa/alsa-topology-conf-1.2.4.2.g15998 and /usr/share/alsa/alsa-ucm-conf-1.2.4.81.g4884e instead of being put on /usr/share/alsa as usual.
So, I believe that their place is better on /testing until further testing and packaging tuning is done.
Last edited by ZhaoLin1457; 06-02-2021 at 12:12 PM.
as the topologies and the UCM folders are put now in folders with names like /usr/share/alsa/alsa-topology-conf-1.2.4.2.g15998 and /usr/share/alsa/alsa-ucm-conf-1.2.4.81.g4884e instead of being put on /usr/share/alsa as usual.
Code:
root:alsa/ # alsactl store
root:alsa/ # alsactl restore
alsa-lib parser.c:2372:(load_toplevel_config) Unable to find the top-level configuration file '/usr/share/alsa/ucm2/ucm.conf'.
alsa-lib main.c:1402:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2
alsa-lib parser.c:2372:(load_toplevel_config) Unable to find the top-level configuration file '/usr/share/alsa/ucm2/ucm.conf'.
alsa-lib main.c:1402:(snd_use_case_mgr_open) error: failed to import hw:1 use case configuration -2
alsa-lib parser.c:2372:(load_toplevel_config) Unable to find the top-level configuration file '/usr/share/alsa/ucm2/ucm.conf'.
alsa-lib main.c:1402:(snd_use_case_mgr_open) error: failed to import hw:29 use case configuration -2
root:alsa/ # pwd
/usr/share/alsa
root:alsa/ # ls -l
total 48
drwxr-xr-x 3 root root 4096 mai 31 21:14 alsa-topology-conf-1.2.4.2.g15998
drwxr-xr-x 4 root root 4096 mai 31 21:14 alsa-ucm-conf-1.2.4.81.g4884e
drwxr-xr-x 2 root root 4096 mai 31 21:15 alsa.conf.d
drwxr-xr-x 2 root root 4096 mai 31 21:14 cards
drwxr-xr-x 2 root root 4096 mai 31 21:14 ctl
drwxr-xr-x 2 root root 4096 mai 31 21:16 init
drwxr-xr-x 2 root root 4096 mai 31 21:14 pcm
drwxr-xr-x 2 root root 4096 mai 31 21:16 speaker-test
-rw-r--r-- 1 root root 10119 mai 31 21:14 alsa.conf
-rw-r--r-- 1 root root 155 mai 31 21:14 smixer.conf
I propose to rollback to the previous ALSA packages, because the one from the series 1.2.5 does not work at all on my mini-PC MinisForum Z83-F which relies on UCM for the audio support.
I got no audio devices and no sound at all. I tested this both with PulseAudio and PipeWire. Not tested at all on pure ALSA, because my mini-PC have around 200 controls on the alsamixer.
And not only that they does not work, but with all respect, looks like at least alsa-lib is not so well packaged, as the topologies and the UCM folders are put now in folders with names like /usr/share/alsa/alsa-topology-conf-1.2.4.2.g15998 and /usr/share/alsa/alsa-ucm-conf-1.2.4.81.g4884e instead of being put on /usr/share/alsa as usual.
So, I believe that their place is better on /testing until further testing and packaging tuning is done.
Code:
Jaroslav Kysela (perexg)
I'll release 1.2.5.1 soon (will try to fix alsa-project/alsa-lib#142 anyway).
sorry, I already asked this before. I saw your TexLive 2021 candidate at your website and I wanted to test it but I couldn't find SlackBuilds for texlive-docs and texlive-extra. Do you plan to add these as well?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.