Requests for current-next (15.0-->15.1)

gbschenkel · 07-27-2023, 02:51 PM

Quote:

Originally Posted by metalforever

The slackware installation defaults to the nvidia card in pulse audio and mutes the sound card, resulting in no sound by default. This is easily fixed by going in and unmuting the sound card and setting it as default .

I use a Creative Sound Blaster AE-5, my onboard sound is disabled, I use Radeon Graphics, Pipewire, Wireplumber and I have this issue. I only can unmute using alsamixer because when Plasma session load the KMixer don't show up all Sound Card devices. I know the problem is on session, because I can unmute, logout, login and is muted again. I have set the config for rc.alsa to load, all what I have saved are still in there, only Front every time get muted.

Already have posted last year about this issue on Pipewire thread.

prejudices_mars · 07-27-2023, 07:11 PM

Fixed.

metalforever · 07-27-2023, 11:55 PM

Quote:

Originally Posted by gbschenkel

I use a Creative Sound Blaster AE-5, my onboard sound is disabled, I use Radeon Graphics, Pipewire, Wireplumber and I have this issue. I only can unmute using alsamixer because when Plasma session load the KMixer don't show up all Sound Card devices. I know the problem is on session, because I can unmute, logout, login and is muted again. I have set the config for rc.alsa to load, all what I have saved are still in there, only Front every time get muted.

Already have posted last year about this issue on Pipewire thread.

Yeah for me its Xonar SE sound card and Nvidia . Must be / must have been an actual bug. ok.

teoberi · 07-28-2023, 02:00 AM

I'm back with the previous post:
https://www.linuxquestions.org/quest...ml#post6443189
Or maybe we are waiting for the Python version to be updated?
https://www.python.org/downloads/source/

alex14641 · 07-28-2023, 01:56 PM

Pipewire 0.3.76

One salient fix:
pipewire: add missing stdbool.h include to version.h.in

marav · 07-29-2023, 08:58 AM

Mesa 23.2.0

https://gitlab.freedesktop.org/mesa/...gs/mesa-23.2.0

dchmelik · 07-30-2023, 04:04 AM

Slackware 15 and current should have a way--as in UNIX tradition which all this still works on FreeBSD--to override PAM on all password checks and allow palindromes ('obscure' setting?) and minimum length zero ('minlen' setting) even for root even for rsh & ssh (like on a private local area network (LAN))... it's not up to PAM to decide what users cannot do with their computers, when even some computers having nothing but the OS (no personal information) and only connect to the Internet to update that (not web browsing, etc.). I wouldn't say PAM 'does one thing and does it well' nor respects users nor UNIX tradition.
        Another thing, if necessary: /etc/pam.d/{rexec,rlogin,rsh} ... rsh/rlogin is better than ssh for our far out rural home's LAN no one would care to drill into an internal wall into a cable to snoop rather than try something worse, but when I use rsh/rlogin on Slackware-current (despite uncommented in /etc/inetd.conf and inetd running) it's always connection refused/closed (is there a log?). It does sometimes/usually work on Slackware 15 (occasionally same errors as Slackware-current) which is what I use for most computers (laptop, server, classic/p3/686) except main desktop (Slackware-current). For users' Ubuntu-based PC I administer, rsh/rlogin came with aforementioned configuration and always works, but on Slackware maybe something else is/went wrong/missing or these network programs are so old they're not so stable? I don't know if the configuration is necessary on Slackware, but it's just a suggestion in case PAM is making it necessary... if it usually/always works for other people without it, then just ignore this, and I'll try to figure out what happened...

henca · 07-30-2023, 04:44 AM

Quote:

Originally Posted by dchmelik

rsh/rlogin is better than ssh for our far out rural home's LAN

I haven't used telnet/rlogin/rexec/rcp/rsh for decades. For me ssh has been more than a good enough replacement. With good old rsh you could have hosts.equiv files allowing you to login without password, but that can be acomplished also with ssh using public/private key pairs. The commands ssh-keygen and ssh-copy-id might be really useful if the different machines are not sharing the same home directories by something line NFS.

Unfortunately ssh has been less backwards compatible with old machines since abandoning the ssh v1 protocol, but having access to semi old "proxy" machines in the network solves that problem.

Using X tunneling through ssh is also convenient, but if you don't want to waste resources on encrypting X traffic you are still free to use DISPLAY and xhost the good old way. The good old way might require some extra configuration of your X server to allow tcp connections.

regards Henrik

0XBF · 07-30-2023, 11:08 AM

Quote:

Originally Posted by dchmelik

Slackware 15 and current should have a way--as in UNIX tradition which all this still works on FreeBSD--to override PAM on all password checks and allow palindromes ('obscure' setting?) and minimum length zero ('minlen' setting) even for root even for rsh & ssh (like on a private local area network (LAN))... it's not up to PAM to decide what users cannot do with their computers, when even some computers having nothing but the OS (no personal information) and only connect to the Internet to update that (not web browsing, etc.). I wouldn't say PAM 'does one thing and does it well' nor respects users nor UNIX tradition.

Personally I don't mind having the security checks on my passwords that PAM provides.

Also AFAIK choosing a palindrome or a password like '123456', '111', etc will just warn you about your terrible choice of password, but still allow you to set it to that. If you don't like the warnings, there is an optional config in the system-auth PAM stack that is commented on how to disable the pam_pwquality checks.

The only password that PAM prevents you from setting in my testing is a blank password. You can get around this by setting a password for a new user, then using "passwd --delete <user>" to remove the password. The system-auth PAM stack allows you to log in still with a blank password due to the 'nullok' in the 'auth' section so once the password is deleted you should be able to do a passwordless login with that account. Note that for ssh you will also have to edit /etc/ssh/sshd_config to allow blank passwords (hmm, blank passwords are discouraged everywhere...)

I dont recommend any of the above so if you choose to leave your system wide open thats up to you and the consequences are yours to deal with.

Windu · 07-30-2023, 02:00 PM

Quote:

Originally Posted by dchmelik

Slackware 15 and current should have a way--as in UNIX tradition which all this still works on FreeBSD--to override PAM on all password checks and allow palindromes ('obscure' setting?) and minimum length zero ('minlen' setting) even for root even for rsh & ssh (like on a private local area network (LAN))

For ssh, this is not prevented by PAM but by a default in the ssh daemon.
See /etc/ssh/sshd_config where you will find:

Code:

#PermitEmptyPasswords no

Un-comment this line and change 'no to 'yes'.

Windu · 07-30-2023, 02:05 PM

Quote:

Originally Posted by dchmelik

Slackware 15 and current should have a way--as in UNIX tradition which all this still works on FreeBSD--to override PAM on all password checks and allow palindromes ('obscure' setting?) and minimum length zero ('minlen' setting) even for root even for rsh & ssh (like on a private local area network (LAN))... it's not up to PAM to decide what users cannot do with their computers, when even some computers having nothing but the OS (no personal information) and only connect to the Internet to update that (not web browsing, etc.). I wouldn't say PAM 'does one thing and does it well' nor respects users nor UNIX tradition.

You can change the way PAM thinks about password validity. In /etc/pam.d/system-auth there's this section. Read the comments and follow the advice.

Code:

#############################
# Password quality checking #
#############################
#
# Please note that unless cracklib and libpwquality are installed, setting
# passwords will not work unless the lines for the pam_pwquality module are
# commented out and the line for the traditional no-quality-check password
# changing is uncommented.
#
# The pam_pwquality module will check the quality of a user-supplied password
# against the dictionary installed for cracklib. Other tests are (or may be)
# done as well - see: man pam_pwquality
#
# Default password quality checking with pam_pwquality. If you don't want
# password quality checking, comment out these two lines and uncomment the
# traditional password handling line below.
password    requisite     pam_pwquality.so minlen=6 retry=3
password    sufficient    pam_unix.so nullok sha512 shadow minlen=6 try_first_pass use_authtok

# Traditional password handling without pam_pwquality password checking.
# Commented out by default to use the two pam_pwquality lines above.
#password    sufficient    pam_unix.so nullok sha512 shadow minlen=6

alex14641 · 07-30-2023, 03:19 PM

Binutils 2.41:

Changelog and source links: https://lists.gnu.org/archive/html/i.../msg00009.html

Jeebizz · 07-30-2023, 06:46 PM

I'm still going to throw this in at least for further consideration - with regards to the installer / options:

The option to choose between Lilo and GRUB / ELILO and GRUB for UEFI
Removing redundant options - "Menu" , since we already have expert anyways - plus changing the output of Expert to a terse output would be nice

volkerdi · 07-30-2023, 07:49 PM

Quote:

Originally Posted by Jeebizz

[*]The option to choose between Lilo and GRUB / ELILO and GRUB for UEFI

We'll let you pick whatever bootloader you like, as long as it's GRUB.

reddog83 · 07-30-2023, 07:53 PM

@volkerdi I was wondering if the gtkmm, glibmm etc would be upgraded and added for the GTK4 port that is being merged in Gnome 43/44/45?