- AlmaLinux Users - AlmaLinux List Archives

Re: XFCE Missing Volume Control Plugin on AlmaLinux 9
by John Thompson 25 Jun '25

25 Jun '25

On 6/24/25 07:26, David Eric via AlmaLinux Users wrote: > Hi everyone, > I’ve installed AlmaLinux 9 with XFCE on my notebook, but I noticed the xfce4-pulseaudio-plugin is missing. As a result, I can’t control the system volume directly—only through individual apps like Audacious or Firefox. > I checked EPEL and even enabled epel-testing, but couldn’t find the package. Should I file a request for the plugin in EPEL, or is there a better solution considering AlmaLinux 9 uses PipeWire? > As a temporary fix, I’m considering using pavucontrol, but I’d love to hear how others are handling this. > Thanks in advance! I downloaded the source code for xfce4-pulseaudio-plugin_0.4.8 and built the plugin from that. Not sure why it wasn't included by default. -- -John (JohnDThompson(a)gmail.com) Appleton, WI USA

1 0

XFCE Missing Volume Control Plugin on AlmaLinux 9
by nguyenthuu30031999＠gmail.com 23 Jun '25

23 Jun '25

Hi everyone, I’ve installed AlmaLinux 9 with XFCE on my notebook, but I noticed the xfce4-pulseaudio-plugin is missing. As a result, I can’t control the system volume directly—only through individual apps like Audacious or Firefox. I checked EPEL and even enabled epel-testing, but couldn’t find the package. Should I file a request for the plugin in EPEL, or is there a better solution considering AlmaLinux 9 uses PipeWire? As a temporary fix, I’m considering using pavucontrol, but I’d love to hear how others are handling this. Thanks in advance!

1 0

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

23 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 30 May '25

30 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

Re: tftp not working on almalinux 9
by Gerald Vogt 30 May '25

30 May '25

On 20.05.25 15:31, Jerry Geis via AlmaLinux Users wrote: > Hi - > > I followed these steps: > https://computingforgeeks.com/setup-tftp-server-on-centos-rhel-rocky- > linux/ <https://computingforgeeks.com/setup-tftp-server-on-centos-rhel- > rocky-linux/> Don't do that. Those instructions are often from people who really don't understand what they are doing. Step 2 messes everything totally up. Someone doesn't understand how systemd works and how to overwrite unit files... > now I get this: > systemctl status tftp-server.service > × tftp-server.service - Tftp Server > Loaded: loaded (/etc/systemd/system/tftp-server.service; enabled; > preset: disabled) > Active: failed (Result: resources) > TriggeredBy: ○ tftp-server.socket > Docs: man:in.tftpd > CPU: 0 > > May 20 08:27:27 VMWare.lsi.com <http://VMWare.lsi.com> systemd[1]: tftp- > server.service: Cannot add dependency job, ignoring: Unit tftp- > server.socket has a bad unit file setting. As the error says: your tftp-server.socket is broken. Which probably comes because of step 2 above. # systemctl cat tftp-server.socket will show the content of the active configuration. > May 20 08:27:28 VMWare.lsi.com <http://VMWare.lsi.com> systemd[1]: tftp- > server.service: Got no socket. > May 20 08:27:28 VMWare.lsi.com <http://VMWare.lsi.com> systemd[1]: tftp- > server.service: Failed to run 'start' task: Invalid argument > May 20 08:27:28 VMWare.lsi.com <http://VMWare.lsi.com> systemd[1]: tftp- > server.service: Failed with result 'resources'. > May 20 08:27:28 VMWare.lsi.com <http://VMWare.lsi.com> systemd[1]: > Failed to start Tftp Server. > > > this is my file after removing start arguments: > more tftp-server.service > [Unit] > Description=Tftp Server > Requires=tftp-server.socket > Documentation=man:in.tftpd > > [Service] > ExecStart=/usr/sbin/in.tftpd /tftpboot > StandardInput=socket > > [Install] > WantedBy=multi-user.target > Also=tftp-server.socket > > STill does not start. Yes. Changing that file doesn't make sense either. The tftp-server.socket unit is broken. > What are the correct steps for setting up TFTP . The correct steps are fairly simple: # dnf -y install tftp-server # systemctl enable --now tftp.socket That's all what is necessary to get it running. After it's running, make necessary changes if you need something different. But that's done via the standard systemd overrides and not by putting different files with different names into /etc/systemd/system... I would recommend in your current setup to remove those copied files # /bin/rm /etc/systemd/system/tftp-server.service # /bin/rm /etc/systemd/system/tftp-server.socket # systemctl daemon-reload # systemctl enable --now tftp.socket And then check if you can access it... -Gerald

2 1

Re: Virtualbox fail with new almalinux kernel
by John Thompson 22 May '25

22 May '25

On 5/22/25 11:45, John Thompson via AlmaLinux Users wrote: > My almalinux-9.6 just updated to kernel 5.14.0-570.12.1.el9_6.x86_64 #1 > and Virtualbox can no longer load my virtual machines, failing with this > error: > > VirtualBox can't operate in VMX root mode. Please disable the KVM kernel > extension, recompile your kernel and reboot > > Anybody else seeing this? Following up on this, using rmmod to unload the kvm and kvm_intel kernel modules allows VirtualBox to load my virtual machines, but that still begs the question "why did this happen?" Looking at the .config files for the current and older kernels I have on my almalinux machine (5.14.0-503.38.1.el9_5.x86_64, 5.14.0-503.40.1.el9_5.x86_64, and 5.14.0-570.12.1.el9_6.x86_64), I see that CONFIG_X86_VMX_FEATURE_NAMES=y and CONFIG_VMXNET3=m are set in all of them, so why does it fail with VirtualBox only in the latest kernel? And does almalinux support a module blacklist in /etc/modprobe.d to prevent the kvm modules from loading in future reboots? -- -John (JohnDThompson(a)gmail.com) Appleton, WI USA

1 0

Virtualbox fail with new almalinux kernel
by John Thompson 22 May '25

22 May '25

My almalinux-9.6 just updated to kernel 5.14.0-570.12.1.el9_6.x86_64 #1 and Virtualbox can no longer load my virtual machines, failing with this error: VirtualBox can't operate in VMX root mode. Please disable the KVM kernel extension, recompile your kernel and reboot Anybody else seeing this? -- -John Thompson (johndthompson(a)gmail.com) Appleton WI USA

1 0

Re: Install sox in 9.6
by Stephen John Smoogen 21 May '25

21 May '25

On Wed, 21 May 2025 at 08:39, Jerry Geis via AlmaLinux Users < users(a)lists.almalinux.org> wrote: > > > On Wed, May 21, 2025 at 8:15 AM Jerry Geis <jerry.geis(a)gmail.com> wrote: > >> I do the following command to install sox and get an error: >> >> yum install sox >> Last metadata expiration check: 0:13:27 ago on Wed May 21 08:00:40 2025. >> No match for argument: sox >> Error: Unable to find a match: sox >> >> what? how do I install sox ? I tried dnf also >> >> Jerry >> >> > I did this: > yum install epel-release > yum install sox > > > my apologies for the email saying to do the above.. I didn't get this email until after I sent my reply. > that seemed to work > > Jerry > > _______________________________________________ > AlmaLinux Users mailing list -- users(a)lists.almalinux.org > To unsubscribe send an email to users-leave(a)lists.almalinux.org > -- Stephen J Smoogen. Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren

1 0

Re: Install sox in 9.6
by Stephen John Smoogen 21 May '25

21 May '25

On Wed, 21 May 2025 at 08:15, Jerry Geis via AlmaLinux Users < users(a)lists.almalinux.org> wrote: > I do the following command to install sox and get an error: > > yum install sox > Last metadata expiration check: 0:13:27 ago on Wed May 21 08:00:40 2025. > No match for argument: sox > Error: Unable to find a match: sox > > what? how do I install sox ? I tried dnf also > > The package sox has not been built for the base EL operating systems but is available in the EPEL repository. Please try the following: dnf config-manager --set-enabled crb dnf install epel-release dnf install sox > Jerry > > _______________________________________________ > AlmaLinux Users mailing list -- users(a)lists.almalinux.org > To unsubscribe send an email to users-leave(a)lists.almalinux.org > -- Stephen J Smoogen. Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren

1 0

Install sox in 9.6
by Jerry Geis 21 May '25

21 May '25

I do the following command to install sox and get an error: yum install sox Last metadata expiration check: 0:13:27 ago on Wed May 21 08:00:40 2025. No match for argument: sox Error: Unable to find a match: sox what? how do I install sox ? I tried dnf also Jerry

1 1

tftp not working on almalinux 9
by Jerry Geis 20 May '25

20 May '25

Hi - I followed these steps: https://computingforgeeks.com/setup-tftp-server-on-centos-rhel-rocky-linux/ now I get this: systemctl status tftp-server.service × tftp-server.service - Tftp Server Loaded: loaded (/etc/systemd/system/tftp-server.service; enabled; preset: disabled) Active: failed (Result: resources) TriggeredBy: ○ tftp-server.socket Docs: man:in.tftpd CPU: 0 May 20 08:27:27 VMWare.lsi.com systemd[1]: tftp-server.service: Cannot add dependency job, ignoring: Unit tftp-server.socket has a bad unit file setting. May 20 08:27:28 VMWare.lsi.com systemd[1]: tftp-server.service: Got no socket. May 20 08:27:28 VMWare.lsi.com systemd[1]: tftp-server.service: Failed to run 'start' task: Invalid argument May 20 08:27:28 VMWare.lsi.com systemd[1]: tftp-server.service: Failed with result 'resources'. May 20 08:27:28 VMWare.lsi.com systemd[1]: Failed to start Tftp Server. this is my file after removing start arguments: more tftp-server.service [Unit] Description=Tftp Server Requires=tftp-server.socket Documentation=man:in.tftpd [Service] ExecStart=/usr/sbin/in.tftpd /tftpboot StandardInput=socket [Install] WantedBy=multi-user.target Also=tftp-server.socket STill does not start. What are the correct steps for setting up TFTP . Thank you. Jerry

1 0

Re: New to Almalinux libnghttp2 needed
by Jerry Geis 19 May '25

19 May '25

On Mon, May 19, 2025 at 10:37 AM Jonathan Wright via AlmaLinux Users < users(a)lists.almalinux.org> wrote: > You probably need to enable the `CRB` repo as that's where the package > exists. > > You can do this with `sudo dnf config-manager --enable crb` > > [jonathan@jon-home ~]$ dnf info libnghttp2-devel > Last metadata expiration check: 0:00:06 ago on Mon 19 May 2025 09:34:07 AM > CDT. > Available Packages > Name : libnghttp2-devel > Version : 1.43.0 > Release : 6.el9 > Architecture : i686 > Size : 52 k > Source : nghttp2-1.43.0-6.el9.src.rpm > Repository : crb > Summary : Files needed for building applications with libnghttp2 > URL : https://nghttp2.org/ > License : MIT > Description : The libnghttp2-devel package includes libraries and header > files needed > : for building applications with libnghttp2. > > Name : libnghttp2-devel > Version : 1.43.0 > Release : 6.el9 > Architecture : x86_64 > Size : 52 k > Source : nghttp2-1.43.0-6.el9.src.rpm > Repository : crb > Summary : Files needed for building applications with libnghttp2 > URL : https://nghttp2.org/ > License : MIT > Description : The libnghttp2-devel package includes libraries and header > files needed > : for building applications with libnghttp2. > _______________________________________________ > AlmaLinux Users mailing list -- users(a)lists.almalinux.org > To unsubscribe send an email to users-leave(a)lists.almalinux.org dnf config-manager --enable crb Updating Subscription Management repositories. Unable to read consumer identity This system is not registered with an entitlement server. You can use subscription-manager to register. The above is what I get.... Jerry

2 4

New to Almalinux libnghttp2 needed
by Jerry Geis 19 May '25

19 May '25

I was moving along pretty good... I did: yum install libnghttp2 then I tried yum install libnghttp2-devel and got "not found" What command do I use to instal the -devel for nghttp2 ? Thanks Jerry

2 1

Setup of default route on multi-homed host
by James Fait 15 May '25

15 May '25

I have a system that is using Almalinux 8.10 that has several active networks for the segregation of traffic according to purpose. Whenever this machine is rebooted, it is random on which interface is selected to be the default route, with two interfaces being selected for default route, only one of which actually connects to the outside network. How can I force that the true default route is always chosen? I have attached the output of the route command before and after deleting the erroneous route. Thanks in advance for your assistance. ## Routing tables after power cycle -- no outside internet access $ route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 10.57.30.1 0.0.0.0 UG 100 0 0 eno2 default pancho208 0.0.0.0 UG 101 0 0 eno4 10.57.0.0 0.0.0.0 255.255.0.0 U 100 0 0 eno2 ###.54.208.0 0.0.0.0 255.255.255.0 U 101 0 0 eno4 192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0 $ sudo route del default # delete the first route ## Routing tables with working outside internet $ route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default pancho208 0.0.0.0 UG 101 0 0 eno4 10.57.0.0 0.0.0.0 255.255.0.0 U 100 0 0 eno2 ###.54.208.0 0.0.0.0 255.255.255.0 U 101 0 0 eno4 192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0

1 0

AlmaLinux Bug fixing process
by Alessandro Baggi 13 May '25

13 May '25

Hi list, I would like to know how works bugfixes on AlmaLinux when a user report a moderate/critical bug. For example, some times ago I found a bug in Debian stable kernel relative to MD devices. I contacted the developer, helped the team with testing to reproduce the issue, testing patches. After some day patch applied on testing and unstable and after ~15 days patch was released on debian stable kernel (wit a backport) and on backports kernel. How works this on AlmaLinux? I know that I can open bugs and help but what about timing on patchs release? I can contact the "kernel team" directly like in Debian? Patch will be released during minor release update or when ready and tested? Thank you in advance. Best regards, Alessandro

1 0

Fwd: Training SIG
by Bryson 01 Apr '25

01 Apr '25

Hello everyone! I am currently gauging interest in a training SIG. Please let me know if this is something you'd want to assist with. The focus areas would be; - Beginner to advanced training courses on system administration, security, and more. - Recording and editing trainings. - Standing up an AlmaLinux OS course certifications. - Interactive labs and virtual machines to practice AlmaLinux commands and tasks. - Certification study guides and hands-on practice exams for certifications. - Community mentorship programs to help new users learn from experienced administrators. If any of these sound like something you would be interested in helping with, or you feel you would like to see this happen, please reply to this email! Feel free to suggest anything you would like to see added to the scope of this SIG.

2 1

About rdma service in Almalinux9
by Patrick Bégou 28 Mar '25

28 Mar '25

Hi, I'm deploying a small cluster based on Almalinux9 using a dedicated cluster environment. When deploying infiniband support, the provided Ansible scripts try to launch the rdma service and it fails. In my old CentOS8 cluster, rdma-core provides the rdma service startup file /usr/lib/systemd/system/rdma.service in rdma-core-26.0-8.el8 to launch the rdma service In my new Almalinux9 cluster this file is no more provided by rdma-core-51.0-1.el9 And I'm unable to understand if it is no more necessary ("automagically" activated) or if I need an other package by looking at various documentations and https://github.com/linux-rdma/rdma-core. But I'm not very familiar with this stack as usually it works out of the box (so I never delved deeply into the documentation before) Could someone help me to clarify this ? Thanks Patrick

1 0

Cannot install drivers for NVIDIA
by Angel Campoverde 25 Feb '25

25 Feb '25

Hi, I am trying to install NVIDIA drivers following https://wiki.almalinux.org/series/system/SystemSeriesA03R9.html#%F0%9F%8C%9… but I see: Last metadata expiration check: 0:00:04 ago on Tue 25 Feb 2025 05:34:12 PM CST. Error: Problem 1: package nvidia-kmod-common-3:570.86.15-1.el9.noarch from cuda-rhel9-x86_64 requires nvidia-kmod = 3:570.86.15, but none of the providers can be installed - cannot install the best candidate for the job - package kmod-nvidia-latest-dkms-3:570.86.15-1.el9.x86_64 from cuda-rhel9-x86_64 is filtered out by modular filtering - package kmod-nvidia-open-dkms-3:570.86.15-1.el9.noarch from cuda-rhel9-x86_64 is filtered out by modular filtering Problem 2: package nvidia-driver-3:570.86.15-1.el9.x86_64 from cuda-rhel9-x86_64 requires nvidia-kmod-common = 3:570.86.15, but none of the providers can be installed - package nvidia-kmod-common-3:570.86.15-1.el9.noarch from cuda-rhel9-x86_64 requires nvidia-kmod = 3:570.86.15, but none of the providers can be installed - cannot install the best candidate for the job - package kmod-nvidia-latest-dkms-3:570.86.15-1.el9.x86_64 from cuda-rhel9-x86_64 is filtered out by modular filtering - package kmod-nvidia-open-dkms-3:570.86.15-1.el9.noarch from cuda-rhel9-x86_64 is filtered out by modular filtering Problem 3: package nvidia-driver-cuda-3:570.86.15-1.el9.x86_64 from cuda-rhel9-x86_64 requires nvidia-kmod-common = 3:570.86.15, but none of the providers can be installed - package nvidia-kmod-common-3:570.86.15-1.el9.noarch from cuda-rhel9-x86_64 requires nvidia-kmod = 3:570.86.15, but none of the providers can be installed - cannot install the best candidate for the job - package kmod-nvidia-latest-dkms-3:570.86.15-1.el9.x86_64 from cuda-rhel9-x86_64 is filtered out by modular filtering - package kmod-nvidia-open-dkms-3:570.86.15-1.el9.noarch from cuda-rhel9-x86_64 is filtered out by modular filtering Problem 4: package nvidia-driver-3:570.86.15-1.el9.x86_64 from cuda-rhel9-x86_64 requires nvidia-kmod-common = 3:570.86.15, but none of the providers can be installed - package nvidia-settings-3:570.86.15-1.el9.x86_64 from cuda-rhel9-x86_64 requires nvidia-driver(x86-64) = 3:570.86.15, but none of the providers can be installed - package nvidia-kmod-common-3:570.86.15-1.el9.noarch from cuda-rhel9-x86_64 requires nvidia-kmod = 3:570.86.15, but none of the providers can be installed - cannot install the best candidate for the job - package kmod-nvidia-latest-dkms-3:570.86.15-1.el9.x86_64 from cuda-rhel9-x86_64 is filtered out by modular filtering - package kmod-nvidia-open-dkms-3:570.86.15-1.el9.noarch from cuda-rhel9-x86_64 is filtered out by modular filtering Problem 5: package xorg-x11-nvidia-3:570.86.15-1.el9.x86_64 from cuda-rhel9-x86_64 requires nvidia-driver(x86-64) = 3:570.86.15, but none of the providers can be installed - package nvidia-driver-3:570.86.15-1.el9.x86_64 from cuda-rhel9-x86_64 requires nvidia-kmod-common = 3:570.86.15, but none of the providers can be installed - package nvidia-xconfig-3:570.86.15-1.el9.x86_64 from cuda-rhel9-x86_64 requires xorg-x11-nvidia(x86-64) >= 3:570.86.15, but none of the providers can be installed - package nvidia-kmod-common-3:570.86.15-1.el9.noarch from cuda-rhel9-x86_64 requires nvidia-kmod = 3:570.86.15, but none of the providers can be installed - cannot install the best candidate for the job - package kmod-nvidia-latest-dkms-3:570.86.15-1.el9.x86_64 from cuda-rhel9-x86_64 is filtered out by modular filtering - package kmod-nvidia-open-dkms-3:570.86.15-1.el9.noarch from cuda-rhel9-x86_64 is filtered out by modular filtering (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) What should I do about it? Cheers.

2 3

Libvirt SEV support in Kitten
by Teodor Pripoae 24 Feb '25

24 Feb '25

Hello, I have been testing Alma Linux Kitten and libvirt is not properly detecting SEV capabilities. Is Libvirt/QEMU compiled without SEV support ? $ dmesg | grep -i sev [ 1.821468] ccp 0000:45:00.1: sev enabled [ 53.414679] kvm_amd: SEV enabled (ASIDs 250 - 509) [ 53.414701] kvm_amd: SEV-ES enabled (ASIDs 1 - 249) [ 53.414720] kvm_amd: SEV-SNP disabled (ASIDs 1 - 249) $ virsh domcapabilities | grep -i sev <sev supported='no'/> $ virt-host-validate QEMU: Checking for hardware virtualization : PASS QEMU: Checking if device '/dev/kvm' exists : PASS QEMU: Checking if device '/dev/kvm' is accessible : PASS QEMU: Checking if device '/dev/vhost-net' exists : PASS QEMU: Checking if device '/dev/net/tun' exists : PASS QEMU: Checking for cgroup 'cpu' controller support : PASS QEMU: Checking for cgroup 'cpuacct' controller support : PASS QEMU: Checking for cgroup 'cpuset' controller support : PASS QEMU: Checking for cgroup 'memory' controller support : PASS QEMU: Checking for cgroup 'devices' controller support : PASS QEMU: Checking for cgroup 'blkio' controller support : PASS QEMU: Checking for device assignment IOMMU support : PASS QEMU: Checking if IOMMU is enabled by kernel : PASS QEMU: Checking for secure guest support : PASS QEMU: Checking for AMD Secure Encrypted Virtualization-Encrypted State (SEV-ES): PASS QEMU: Checking for AMD Secure Encrypted Virtualization-Secure Nested Paging (SEV-SNP): PASS

2 2

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

22 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

Kickstart installs with isolinux (insecure boot) fails, same Kickstart works with EFI(secureboot)
by fait＠uga.edu 10 Sep '24

10 Sep '24

I have been working with AlmaLinux 8 for a couple of years using various iterations AlmaLinux 8, with my systems(5 of them) currently using 8.10. I am now in the process of validating install media to move to version 9.4, using kickstart to manage the initial configuration of these hosts. The kickstart file sets up the network,decides the host name, and sets up a complex partitioning scenario. Initially I tested this using secure boot, without any issue. I repeated the same install, on the same hardware, using the same kickstart file, only this time using the legacy boot (insecure). I have verified that this is an issue with insecure boot, as I then did a manual install of a server+graphics, along with development tools, and then took the resulting kickstart file, made the required changes so that the partitioning would work, and then attempted to do a kickstart install using this minimal kickstart, with the same results of success for the EFI boot, and failure with the isolinux boot. I did check, and the two commands to the kernel appear to be identical, but the insecure boot is not able to find the kickstart file. Has anyone else seen this behavior? Anyone found a work-around?

1 0

Almalinux 9.4 import LVM VG bug?
by Alessandro Baggi 08 Sep '24

08 Sep '24

Hi list, on my Almalinux 9.4 I tried to import LVM Volume Group from another system. When I attached disks on my workstation, pvscan or vgimport does not found any lvm devices. Reading here: https://discussion.fedoraproject.org/t/lvm-operations-might-fail-on-a-fedor… seems that renaming /etc/lvm/devices/system.devices permits the system to read lvm devices and able to import an existing volume. This is a bug or a wanted behaviour? File system.devices is required? I should restore it? Thank you in advance Alessandro.

2 2

Where are the archives for: users@lists.almalinux.org ?
by Mike Schleif 29 Aug '24

29 Aug '24

I just signed up and I want to see if my questions are already answered. TY

2 1

RPM creation problem
by Alessandro Baggi 25 Jul '24

25 Jul '24

Hi list, I'm creating an RPM package for gocryptfs on AlmaLinux 9.3 I'm using the source with deps (vendoring) because deps are too much. During the process rpmbuild returns: gocryptfs-debugsource-2.4.0-1.el9.x86_64 error: Empty %files file /root/rpmbuild/BUILD/gocryptfs_v2.4.0_src-deps/debugsourcefiles.list To avoid this I can add: %global debug_package %{nil} and the problem is solved also if the build-id links are generated. But, here there is a problem. I read that for $arch packages a debug package will be created and if some error is reported there is something wrong on the SPEC file. Why debugsourcefiles.list is empty? What is causing this? Thank you in advance. Alessandro.

3 4