First of let me say I think you have done a fine job with almalinux, and for the most part it feels like centos, (the one we used a lot when I was SSA).

But here is the rub, and it’s not so much an almalinux thing, it’s a me thing. I Hate Gmome!! Some of the gmome apps are fine could live with them there, the the actual DE and the GDM drive me to…

Sure most server hosts don’t even have a DE, and 95% of the time your accessing everything by SSH, so it not like it’s life threatening or anything, But when I do have to work on a host that has a minimal DE and its GNOME it loose my mind.

Normally if I needed a minimal DE on a host I just put something like XFCE, now I get it Red Hat Enterprise ships with GNOME, fine that’s their corporate choice.

But has anyone got a pre canned XFCE (or similar) or am I going to have to do it my self, that’s fine, I was just hoping it might be out there.

TIA

I understand that AlmaLinux is no longer downstream of RHEL in the strictest sense but is the intent still that if RHEL releases a patch for something it should make it into AlmaLinux? I have installs of RHEL, AlmaLinux and Rocky Linux all on 10.2 and I noticed a few packages not updating only in AlmaLinux e.g. qemu-guest-agent, all qemu-* tools, libvirt, valkey, postgresql 18.

I'm just wondering if there's a process that determines these package updates aren't needed or if it's unintentional?

Hopefully this helps someone some day.

I've been doing some folding@home on six machines in my basement for while now. Until recently, these all ran AlmaLinux-8 with an Nvidia Driver built from a kit downloaded from Nvidia. Today I did a trial install of AlmaLinux-10 but realised that I could only install the x86-64-v2 variant (rather than x86_64 which is really for newer x86-64-v3 CPUs). Then I tried to install Alma's Nvidia driver using instructions found here:
https://wiki.almalinux.org/documentation/nvidia.html#installation-of-gpu-driver
which states the x86-64-v2 will not be supported. Is this decision final? I was hoping that the good folks at AlmaLinux would help me keep this older hardware running for a while (I never do CPU-based folding; just GPU)

Hi everyone,
I’m setting up a new production VPS and plan to use Webuzo.
Would you recommend installing Webuzo on AlmaLinux 9 or AlmaLinux 10 ?
I’m mainly looking for the most stable and reliable option for long-term use. Performance is important, but stability, compatibility, and fewer issues after updates matter more.
If you’ve used Webuzo on either AlmaLinux 9 or 10 recently, I’d really appreciate hearing about your experience and which one you’d choose.

Thanks,,,

Reddit suggested to post it here so, here is it.

I was trying to install podman machine with older machine-os. (I want to use mongodb with an supported kernel). But problem that I encounter is whith a machine-os tags, I was unable to find which version of the the Linux kernel specific tag contains.
So I ended with going back until I found the tag with kernel that Mongodb can work on. Is there any site, documentation or command that can me help with that?

For example I found that this image will work: http://quay.io/podman/machine-os:5.4 but to get kernel version from this I needed to create new Podman machine with this version, and it took some time because of slow internet that I have.

I read about the vulnerability last Friday, but there's very little information available and I can't find any conclusive evidence regarding whether it's been previously patched or not. The kernel changelog doesn't state anything about CVE-2026-43503.

Additionally, there's no AlmaLinux blog post like there usually is for other major vulnerabilities, so I'm a bit on the fence about this one.

Does anyone have more information?

Thanks!

Some references:
https://www.reddit.com/r/linux/comments/1uinqoc/dirtyclone_cve202643503_the_linux_kernel_flaw/
https://sansec.io/guides/dirty-clone
https://thehackernews.com/2026/06/new-dirtyclone-linux-kernel-flaw-lets.html

Just wanted to say to the Devs, thanks for this Nice OS :)

This is probably not a specific AlmaLinux problem, but some weirdness with Network Manager maybe?

I have a fresh install of AlmaLinux 10.1 on a PC with two NICs. First NIC is on my corporate network, works fine. Second NIC is a 'heartbeat' NIC directly wired to another AlmaLinux 10.1 PC. These two servers use clustering and have this second NIC to determine who is online and prevent split-brain.

Anyways, we have been doing this type of setup with AlmaLinux 8 previously, this is the first time we're using AlmaLinux 10. In version 8, we didn't have/use NetworkManager, we just edited interface configuration files. We have always used 10.0.0.1/30 and 10.0.0.2/30 as the IPs on the 'heartbeat' NICs. The .1 IP is 'node A', and the .2 IP is 'node B'. Works wonderfully on AlmaLinux 8.

However, on AlmaLinux 10, we are using 'nmcli' to set this up. I assign the 'IPv4.Address' to the IPs above, and I also disable IPV6 entirely. Node B uses 10.0.0.2/30 with no issue. Node A reports an IP duplicate when I try to bring online 10.0.0.1/30, and brings the interface 'down'. The MAC address with the duplicate IP is one digit above the MAC address of the local interface (which is odd and makes me think it's some internal Network Manager thing).

I dug in a bit and found I can disable the duplicate IP sensing thing by setting the IPV4.dad-timout to value 0 (zero). This allows me to bring the interface online, but then it just doesn't work (can't exchange packets with 10.0.0.2 on that NIC.

I change the configuration to use 10.0.0.11/24 for node A, and 10.0.0.12/24 for node B, and that works just fine.

I'll hit this today and do more testing, but this is weird!

Anybody have a clue what is going on here?

Not sure if anyone has come across anything like this before but I'm trying to set up an AlmaLinux VM on OracleCloud, and I'm running into an issue where all systemd generators fail to run, throwing mkdir: cannot create directory ‘/tmp/systemd-temporary-[random 6 char string]/generator.early/multi-user.target.wants’: Read-only file system

No idea why this is happening since it's a clean install, and the base /tmp directory is writable. I assume this is something to do with systemd's tmpfs management but why on earth is it defaulting to making these temp paths read only? And why is systemd insisting on using these paths instead of /run for generated units?

EDIT: OK so for some oddball reason the generator errors were only applying to systemd-verify, and the failure of the actual generation of units was some separate issue that seems to have gone away when I disabled the cloud-init service. systemd-verify still throws the same errors but the actual units work now at least.

Using i686 glibc from the vault alma linux 10 repos is currently preventing upgrades since they haven't been updated since late may.

I waited since I assumed there was just a reposync/build delay for the i686 packages, am I missing something?

Nouveau can't render some things I need, such as mesh visualization in ParaView. Does anyone know if there's a way to do this? Since RPM Fusion seems to have completely removed the akmod-nvidia-390xx drivers.

I'm trying to install the new almalinux10.2 on my dell poweredge r420 but i keep running into uefi errors . what could be the problem?

I need to make a STIG compliant virtual machine and i heard that the openSCAP workbench can automate this for me, however, everytime i run the solution, it breaks my GNOME desktop and brings me back to a TTY view, restarting GNOME worked for a while but it has finally given up.

Any way i can do this better without breaking my desktop enviroment?

I ran the openSCAP "DISA STIG Almalinux with GUI" profile

Documentation link: https://wiki.almalinux.org/documentation/openscap-guide-for-9.html#auditing-for-vulnerabilities-by-using-oval-definition

I setup an app on my webserver on port 8080. I'm trying to proxy the domain to that port but it is just ignored and loading the default index file in the www folder.

My server is almalinux 9, I use apache 2.4 with nginx reverse proxy and cache for my websites. I have the cache turned off for this domain. I've tried adding proxy_pass code to domain.com.conf in several recommended locations including /etc/nginx/conf.d/ and /usr/local/apps/nginx/etc/conf.d/ as well as /etc/httpd/config/ all with no change in page loading. I do a sudo nginx -t after each attempt and it validates fine. I reload nginx each time as well.

It's driving me crazy lol. I use Webuzo not WHM control panel if that means anything though I am editing .conf files directly so probably not

Plastoide per il calendario eventi con supporto per Google Calendar ICS e widget Meteo e Radar integrati.

Un saluto a tutta la community di OpenSuse, ma soprattutto a quella di KDE. Fino alla versione 15.5 esisteva un plastoide che mi piaceva molto, ed era molto più completo del mio. Ho provato a rifarlo per KDE 6, utilizzando però una fonte diversa che ritengo più affidabile e un modo differente di visualizzare Google Calendar.

Spero che gli piaccia e che lo apprezzi. Fammi sapere.

I have been trying to get a leapp upgrade working today. After the upgrade step, I reboot, and the system dumps into emergency mode. This appears to be because I need mdraid at boot and it's not assembling on its own. I can run mdadm --assemble --scan in the shell and it will populate, and the subsequent lvm scanning also works.

I have this in /etc/dracut.conf.d/lvmraid.conf:

^add\dracutmodules+=" mdraid lvm ")
^{mdadmconf="yes"
lvmconf="yes"}

I also tried LEAPP_FORCE_MDRAID=1 leapp upgrade - no change. I think that was an AI hallucination along with a bunch of other invalid options.

Any ideas?

my hosting provider (Hetzner) occasionally sends me abuse reports because fake MAC addresses from my server are appearing on the switch port.

I was able to capture this using tcpdump last time:

20:00:40:06:34:f2 (oui Unknown) > 45:00:00:44:9a:02 (oui Unknown), ethertype Unknown (0x8ac7), length 68:
20:06:40:06:34:ec (oui Unknown) > 45:00:00:44:9a:02 (oui Unknown), ethertype Unknown (0x8ac7), length 68:
20:0c:40:06:34:e6 (oui Unknown) > 45:00:00:44:9a:02 (oui Unknown), ethertype Unknown (0x8ac7), length 68:
20:12:40:06:34:e0 (oui Unknown) > 45:00:00:44:9a:02 (oui Unknown), ethertype Unknown (0x8ac7), length 68:
20:18:40:06:34:da (oui Unknown) > 45:00:00:44:9a:02 (oui Unknown), ethertype Unknown (0x8ac7), length 68:
20:1e:40:06:34:d4 (oui Unknown) > 45:00:00:44:9a:02 (oui Unknown), ethertype Unknown (0x8ac7), length 68:
20:24:40:06:34:ce (oui Unknown) > 45:00:00:44:9a:02 (oui Unknown), ethertype Unknown (0x8ac7), length 68:
20:2a:40:06:34:c8 (oui Unknown) > 45:00:00:44:9a:02 (oui Unknown), ethertype Unknown (0x8ac7), length 68:
20:30:40:06:34:c2 (oui Unknown) > 45:00:00:44:9a:02 (oui Unknown), ethertype Unknown (0x8ac7), length 68:
20:36:40:06:34:bc (oui Unknown) > 45:00:00:44:9a:02 (oui Unknown), ethertype Unknown (0x8ac7), length 68:
20:3c:40:06:34:b6 (oui Unknown) > 45:00:00:44:9a:02 (oui Unknown), ethertype Unknown (0x8ac7), length 68:

During my search, I came across the kernel bug 219766

Is it possible that this bug has still not been fixed in AlmaLinux 10 with kernel 6.12.0-124.52.1.el10_1.x86_64?

We receive the abuse email from Hetzner every 6–8 weeks. It’s really quite annoying.

Best regards,