October 2024 - AlmaLinux Users - AlmaLinux List Archives

AlmaLinux 9 and XFCE sound problem
by Alessandro Baggi 24 Jun '25

24 Jun '25

Hey there, I installed Almalinux OS 9 on my notebook. I installed XFCE but I'm getting problem with audio because xfce4-pulseaudio plugin is missing and I can't change sound volume except on the specific program that play the music (In my case audacious and firefox). Currently I don't know if I must open a "please build xfce4-pulseaudio-plugin" on epel or if I should use something due to pipewire. I enabled also epel-testing to check if the package was in testing but seems missing. Someone has the same problem? Thank you in advance.

6 6

Autofs: too many open files issue
by Carles Acosta Silva 31 May '25

31 May '25

Hi, We are running AlmaLinux 9.3 on several nodes that normally use autofs to mount different kinds of remote directories. Since the last week, we are seeing these errors: automount[2150866]: open_pipe:161: failed to open pipe: Too many open files And automount stops working. It does not seem that any user has arrived at the maximum number of open files. Do you have any idea where we can look to find a solution? Thank you in advance. Best regards, Carles

5 5

AlmaLinux 9.3 and libvirtd problem
by Alessandro Baggi 23 Oct '24

23 Oct '24

Hi list, I'm running AlmaLinux 9.3 and I'm running several virtual machines using qemu-kvm and libvirtd ( and virt-manager). 3 VMs starts during system boot (configured with "virsh autostart VMNAME"). All works as expected until I loaded a old vm config file. When I tried to run "systemctl reload libvirtd" I got: "libvirtd.service is not active, cannot reload." It is enable on boot and running "systemctl status libvirtd" I get: Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; preset: disabled) Active: inactive (dead) since Thu 2024-01-25 16:32:40 CET; 4min 55s ago Duration: 5min 14.530s It reports that it is inactive (really dead) because I can't find it inside process table. Rebooting the system, I found libvirtd process with argument "--timeout=120" and after 120 seconds it dies. Reading libvirtd systemd unit I found Environment=LIBVIRTD_ARGS="--timeout 120" and from the man page I get: "t, --timeout *SECONDS* Exit after timeout period (in seconds), provided there are neither any client connections nor any running domains." Here I found something strange. On boot I have 3 running domains but libvirtd dies after 120 seconds. To load new configuration I need to run restart and virt-manager works without problem also if libvirtd is not running. This is a misconfiguration or it is a bug? Thank you in advance. Alessandro.

2 4

Cannot login to user account
by Angel Campoverde 22 Oct '24

22 Oct '24

Hi, I am seeing some problems with my alma9 installation. 1. I locked the machine with superkey + l, then I came back and unlocked it. 2. I saw that the upper case keys were on by default and I had to turn on caps-lock to turn back on the lower case keys. 3. The number pad did not show numbers, but the signs you get when you press shift, i.e. !@#$... 4. The arrow keys did not do the arrow thing, but they showed upper case letters, A, F, I do not remember the others. So I restarted. Then I tried to log in but: 1. When I put the right password, It looks like it will log in, because the screen goes black, however it comes back to the login screen without telling me anything else. 2. I know this is not a password issue, because when I put a wrong password, it tells me that the password is wrong. 3. I can log in as root. 4. I can do su - username and log in from there with my normal password. I do not recall doing anything special with the computer. Do you know what might be happening? Cheers.

2 1